writing-stickiness
Applies the Heath brothers' SUCCESs model (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make messages memorable and persuasive, with systematic analysis, targeted improvements, and scoring (0-18 stickiness scorecard). Use when making messages more memorable or compelling, preparing presentations, crafting pitches or campaigns, or when user mentions stickiness, making ideas stick, persuasion, SUCCESs framework, or Heath brothers.
What this skill does
# Writing Stickiness Enhancement
## Table of Contents
- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [SUCCESs Framework Overview](#success-framework-overview)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
**Related skills:** Use `writing-structure-planner` for planning structure, `writing-revision` for prose revision, `writing-pre-publish-checklist` for final quality checks.
## Core Principles
1. **Six dimensions of stickiness**: Simple, Unexpected, Concrete, Credible, Emotional, Stories
2. **Diagnose before treating**: Score current stickiness first, then improve weakest areas
3. **Not all principles are equal**: Some matter more for certain contexts - prioritize accordingly
4. **Concrete beats abstract**: Brains think in images, not abstractions
5. **Individuals beat statistics**: One person's story moves people more than millions in data
## Workflow
Copy this checklist and track your progress:
```
Stickiness Enhancement:
- [ ] Step 1: Analyze against SUCCESs framework
- [ ] Step 2: Improve weak principles
- [ ] Step 3: Score and refine
```
**Before starting:** Review [resources/success-model.md](resources/success-model.md) for the complete SUCCESs framework with all 6 principles, stickiness scorecard, and before/after examples.
Analyze the entire document first and output findings to an analysis file in the current directory, then read that file to make improvements. This ensures complete coverage.
**Step 1: Analyze against SUCCESs framework**
Step 1.1: Read entire draft. Create analysis file `writer-stickiness-analysis.md` assessing the document against all 6 SUCCESs principles:
- **Simple** (0-3): Identify core message in 12 words or fewer. List competing messages. Rate clarity and focus.
- **Unexpected** (0-3): Identify surprise elements or curiosity gaps. Note where expectations could be violated. Rate attention-getting power.
- **Concrete** (0-3): List visualizable details. Identify abstract sections needing examples. Rate sensory specificity.
- **Credible** (0-3): Identify credibility sources (statistics, testability, authority, vivid details). Note unsupported claims. Rate believability.
- **Emotional** (0-3): Identify emotional connections and personal benefits. Note where motivation could be strengthened. Rate "care factor."
- **Stories** (0-3): Identify story or human elements. Note opportunities to add narrative. Rate mental simulation potential.
Step 1.2: Calculate total current stickiness score out of 18. Present findings to user.
See each principle's section in [resources/success-model.md](resources/success-model.md) for detailed scoring guidance.
**Step 2: Improve weak principles**
Step 2.1: Read analysis file. Identify the 2-3 weakest principles (scored 0-1).
Step 2.2: Work through entire draft making targeted improvements for each weak principle:
- **Simple**: Refine core message to 12 words or fewer. Strip competing ideas.
- **Unexpected**: Add surprise or curiosity gaps. Violate reader expectations.
- **Concrete**: Add visualizable details and specific examples. Replace abstractions.
- **Credible**: Add statistics (human-scale), testability ("try it yourself"), authority, or vivid details.
- **Emotional**: Strengthen personal benefits and emotional connections. Focus on individuals, not masses.
- **Stories**: Add narrative or human elements. Use challenge, connection, or creativity plots.
Step 2.3: Present improved version to user with changes highlighted.
See [resources/success-model.md](resources/success-model.md) for specific techniques and examples for each principle.
**Step 3: Score and refine**
Step 3.1: Score the revised message using the [Stickiness Scorecard](resources/success-model.md#stickiness-scorecard).
Step 3.2: Aim for 12+/18 for good stickiness, 15+/18 for excellent. If score is below 12, identify the weakest 2 principles and do another improvement pass focusing on those.
Step 3.3: Present final scored version with before/after comparison.
See [resources/success-model.md - Complete Example](resources/success-model.md#complete-example) for transformation patterns.
Validate using [resources/evaluators/rubric_stickiness.json](resources/evaluators/rubric_stickiness.json). **Minimum standard**: Average score >= 3.5.
## SUCCESs Framework Overview
| Principle | Key Question | Technique |
|-----------|-------------|-----------|
| **S**imple | What's the ONE core idea? | Commander's intent in 12 words |
| **U**nexpected | What will surprise readers? | Schema violation + curiosity gaps |
| **C**oncrete | Can readers visualize it? | Sensory details, specific examples |
| **C**redible | Why should readers believe it? | Human-scale stats, testability |
| **E**motional | Why should readers care? | Individual focus, identity appeal |
| **S**tories | Can readers simulate the experience? | Challenge/connection/creativity plots |
**Scoring:** Each principle rated 0-3. Total out of 18. Target 12+ for good, 15+ for excellent.
## Guardrails
**Requirements:**
1. **Score before improving**: Always analyze and score the current state before making changes
2. **Target weakest first**: Focus improvements on the lowest-scoring principles
3. **Preserve accuracy**: Never sacrifice truthfulness for stickiness - credibility matters
4. **Context-appropriate**: Not every piece needs maximum stickiness - match to purpose
5. **Re-score after improving**: Always score the revised version to measure improvement
**Common pitfalls:**
- Improving already-strong principles while ignoring weak ones
- Adding surprise that's random rather than relevant to the core message
- Using statistics that are too large to grasp (billions, trillions)
- Focusing on masses instead of individuals for emotional appeal
- Telling instead of showing when adding stories
## Quick Reference
**Key resources:**
- **[resources/success-model.md](resources/success-model.md)**: Complete SUCCESs framework, all 6 principles, scorecard, examples
- **[resources/evaluators/rubric_stickiness.json](resources/evaluators/rubric_stickiness.json)**: Quality scoring criteria
**Inputs required:**
- Draft text or message to enhance
- Target audience (if known)
- Context (presentation, article, email, pitch, etc.)
**Outputs produced:**
- Stickiness analysis with per-principle scores
- Improved version targeting weak principles
- Before/after comparison with score improvement
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.