skills/writing-stickiness/SKILL.md
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.
npx skillsauth add lyndonkl/claude writing-stickinessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Related skills: Use writing-structure-planner for planning structure, writing-revision for prose revision, writing-pre-publish-checklist for final quality checks.
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 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:
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 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:
Step 2.3: Present improved version to user with changes highlighted.
See 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.
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 for transformation patterns.
Validate using resources/evaluators/rubric_stickiness.json. Minimum standard: Average score >= 3.5.
| Principle | Key Question | Technique | |-----------|-------------|-----------| | Simple | What's the ONE core idea? | Commander's intent in 12 words | | Unexpected | What will surprise readers? | Schema violation + curiosity gaps | | Concrete | Can readers visualize it? | Sensory details, specific examples | | Credible | Why should readers believe it? | Human-scale stats, testability | | Emotional | Why should readers care? | Individual focus, identity appeal | | Stories | 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.
Requirements:
Common pitfalls:
Key resources:
Inputs required:
Outputs produced:
development
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
development
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
testing
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
development
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.