lyndonkl/writing-stickiness
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.
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude writing-stickinessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:27 AM137.5s3 files scanned
SKILL.md
- name:
- writing-stickiness
- description:
- 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.
Writing Stickiness Enhancement
Table of Contents
- Core Principles
- Workflow
- SUCCESs Framework Overview
- Guardrails
- 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
- Six dimensions of stickiness: Simple, Unexpected, Concrete, Credible, Emotional, Stories
- Diagnose before treating: Score current stickiness first, then improve weakest areas
- Not all principles are equal: Some matter more for certain contexts - prioritize accordingly
- Concrete beats abstract: Brains think in images, not abstractions
- 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 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 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 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.
SUCCESs Framework Overview
| 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.
Guardrails
Requirements:
- Score before improving: Always analyze and score the current state before making changes
- Target weakest first: Focus improvements on the lowest-scoring principles
- Preserve accuracy: Never sacrifice truthfulness for stickiness - credibility matters
- Context-appropriate: Not every piece needs maximum stickiness - match to purpose
- 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: Complete SUCCESs framework, all 6 principles, scorecard, examples
- 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 Skills
lyndonkl/conf-theme-clustering
testing
VerifiedTrustedCommunity
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-schedule-optimization
development
VerifiedTrustedCommunity
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-program-extraction
development
VerifiedTrustedCommunity
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-preference-elicitation
development
VerifiedTrustedCommunity
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.
127SKILL.mdUpdated Jun 28, 2026