MCP HubMCP Hub
SKILL·FBB757

made-to-stick

wondelai
Actualizado 21 days ago
7 vistas
2,069
213
2,069
Ver en GitHub
Comunicaciónpowerpointai

Acerca de

Esta habilidad ayuda a los desarrolladores a crear mensajes memorables e impactantes utilizando el marco SUCCESs (Simple, Inesperado, Concreto, Creíble, Emocional, Historias). Se activa cuando los usuarios necesitan mejorar presentaciones, simplificar explicaciones complejas o hacer que sus exposiciones sean más convincentes. La herramienta aborda específicamente la "maldición del conocimiento" para crear mensajes que sean comprendidos, recordados y que impulsen a la acción.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add wondelai/skills -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/wondelai/skills
Git CloneAlternativo
git clone https://github.com/wondelai/skills.git ~/.claude/skills/made-to-stick

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Made to Stick Framework

A framework for crafting ideas and messages that are understood, remembered, and drive lasting action. Based on decades of research into why some ideas survive and others die.

Core Principle

The Curse of Knowledge is the single greatest barrier to effective communication. Once we know something, we can't imagine not knowing it—which makes us bad at explaining our ideas to others. Sticky ideas aren't born, they're made: the SUCCESs framework provides six principles that make any idea more memorable and impactful.

Scoring

Goal: 10/10. Score any messaging (copy, presentations, campaigns, onboarding) by running the Quick Diagnostic: rate each of the six traits 1-10, then map the 6-60 total to a band (50-60 = 9-10, extremely sticky; 35-49 = 7-8, strong; 20-34 = 4-6, forgettable; below 20 = ≤3, won't stick). Always state the current score, which traits scored lowest, and the specific fix from the diagnostic's Fix column.

The SUCCESs Framework

Simple · Unexpected · Concrete · Credible · Emotional · Stories

Not a checklist—a toolkit. Not every sticky idea uses all six, but the stickiest ideas tend to use most of them—don't force all six onto a message that only needs two.

1. Simple

Core concept: Find the core of the idea and share it compactly. Simple ≠ dumbed down—it means ruthless prioritization: "if you say three things, you say nothing."

The Commander's Intent: if everything else goes wrong, what ONE thing must we accomplish? For messaging: if people remember ONE thing about your product, what should it be? The inverted pyramid: lead with the most important thing; readers who stop anywhere still got the core.

Techniques for simplicity:

TechniqueHow It WorksExample
Core messageStrip to the essentialSouthwest: "THE low-fare airline"
AnalogyExplain new via known"It's like Uber for dog walking"
GenerativeCore idea that generates behavior"Names, names, names" (local newspaper motto)

Application to product messaging:

Before (Complex)After (Simple)
"AI-powered, cloud-native customer engagement platform with omnichannel capabilities""Talk to all your customers in one place"
"We leverage machine learning algorithms to optimize conversion funnels""We find why visitors don't buy and fix it"
"Enterprise-grade project management with Gantt charts, resource allocation...""The simplest way to manage projects"

The test: Can you explain it to a smart 12-year-old? Warning: don't simplify into emptiness—"we make the world better" is simple but meaningless.

See references/simple.md when you can't reduce a message to one core idea—it has the Commander's Intent exercise, the inverted-pyramid pattern, and five "find the core" drills.

2. Unexpected

Core concept: Get attention by breaking patterns (surprise); hold attention by creating curiosity gaps (interest). The surprise must connect to the core message—identify the counterintuitive implication and communicate that.

Example surprises:

CategoryExpectedUnexpected (Sticky)
Product launch"Introducing our new feature""We removed your favorite feature. Here's why."
Statistics"Obesity is growing""A bag of movie popcorn has more fat than a bacon-and-eggs breakfast, Big Mac and fries, and steak dinner — combined"
Value prop"Save money on insurance""15 minutes could save you 15%" (specific, unexpected)

Creating curiosity gaps — open a gap in knowledge, create the desire to fill it:

TechniqueHow It WorksExample
QuestionAsk what they don't know"What's the #1 reason startups fail?"
PredictionAsk them to predict"How many X do you think...?"
MysteryPresent a puzzle, delay the resolution"Nordstrom once refunded a set of tires. They don't sell tires."
ChallengeViolate assumptions"Everything you know about X is wrong"

Anti-pattern: Gimmicky surprise without substance.

See references/unexpected.md when a message reads as predictable—it has techniques for finding the counterintuitive angle and engineering curiosity gaps.

3. Concrete

Core concept: Use sensory language and specific details instead of abstract concepts. Abstraction kills memorability; the more concrete and specific the idea, the stickier it becomes.

Abstract vs. Concrete:

AbstractConcrete
"Improve customer experience""Customers get their order in 30 minutes, still hot"
"Increase engagement""Users open the app 8 times a day"
"Optimize efficiency""Reduce report generation from 4 hours to 10 minutes"
"World-class support""Call us and a human answers in under 60 seconds"
"Scalable solution""Handle 10,000 users on day one without code changes"

The Velcro theory of memory: concrete ideas have more "hooks"—"bicycle" is easier to remember than "vehicle" because you can picture it.

Techniques for concreteness:

TechniqueHow It WorksExample
Specific numbersReplace "a lot" with exact figures"2,347 customers" not "thousands"
Sensory languageEngage senses"Crispy, not crunchy"
Concrete exampleReplace category with instance"Like John, a 35-year-old teacher in Denver"
Before/afterTangible transformation"Before: 4 hours. After: 10 minutes."

Application: features → outcomes; percentages → real numbers ("saves 40%" → "saves 16 hours/month"); categories → specific examples ("restaurants" → "pizza shops in Brooklyn"); demos > feature lists.

See references/concrete.md when a message stays abstract—it has sensory-language drills and the abstract-to-concrete conversion process.

4. Credible

Core concept: Help people believe your idea using external credibility (authorities, credentials) and internal credibility (vivid details, human-scale statistics, testable claims)—internal is more powerful.

External credibility:

SourceHow It WorksExample
AuthoritiesExpert endorsement"Recommended by Harvard Business Review"
Anti-authoritiesReal people with experience"Here's what a customer with the same problem found"
CredentialsVerifiable achievements"10 years experience, SOC 2 certified"

Internal credibility:

TechniqueHow It WorksExample
Vivid detailsSpecificity implies truth"On Tuesday at 3pm, in the conference room on the 4th floor..."
Human-scale statisticsRelate numbers to experienceNot "10TB of data" but "every book ever written, 100 times"
The Sinatra TestOne example so good it proves everything"If I can make it there, I can make it anywhere"
Testable credentialLet them verify"Try it free for 14 days"

The Sinatra Test: one reference so impressive it handles all objections—"We secured the White House" (security), "We handle Super Bowl traffic" (scalability), "Used by Apple, Google, and Microsoft" (quality).

Making statistics stick: put them in a context people understand—not "37 grams of saturated fat" but "more saturated fat than a Big Mac, fries, and milkshake combined."

See references/credible.md when a claim sounds unbelievable—it has authority types, the Sinatra Test, and methods for making statistics human-scale.

5. Emotional

Core concept: Make people feel something—people act on emotion, not analysis. Statistics numb; stories about individuals inspire action. Mother Teresa principle: "If I look at the mass, I will never act. If I look at the one, I will."

Emotional appeals:

ApproachHow It WorksExample
Individual focusOne person's story > statistics"Meet Sarah, who..." > "10,000 people affected"
Self-interest"What's in it for me?"WIIFM: features → personal benefits
Identity"What would someone like me do?""Texans don't litter" (Don't Mess with Texas)
Maslow's hierarchyAppeal to the right levelSecurity, belonging, esteem, self-actualization

The identity approach: people decide based on identity, not calculation—frame your product as consistent with who they want to be:

Identity FrameProductMessage
"I'm an innovative leader"SaaS tool"For teams that move fast"
"I care about my health"Food product"Made with ingredients you can pronounce"
"I'm a serious professional"B2B service"The tool Fortune 500 CTOs rely on"

Avoid the "semantic stretch": don't over-abstract the emotion—"Support the troops" beats "Support our national defense infrastructure."

See references/emotional.md when a message is all logic and no feeling—it has the individual-focus, identity, and self-interest appeal frameworks.

6. Stories

Core concept: Stories are flight simulators for the brain: they simulate experience, inspire action, stay memorable through narrative structure, and bypass resistance (people don't argue with stories).

Three story plots that work:

PlotStructureWhen to UseExample
ChallengeProtagonist overcomes obstacleInspire courage, perseverance"We started in a garage..."
ConnectionPeople bridging a gapInspire tolerance, teamwork"A customer helped another customer..."
CreativityNovel solution to problemInspire innovation, thinking"We tried X, Y, Z... then discovered..."

Story structure for product messaging: character (relatable customer) → problem (emotional) → journey (what they tried, concrete) → solution (how your product helped, specific) → outcome (measurable + emotional).

Example:

"Sarah ran a 10-person design agency. Her team spent 4 hours every Friday compiling client reports from 5 different tools. She'd tried hiring an intern, building spreadsheets, even a custom tool. Nothing worked. Then she found [Product]. Now reports generate in 10 minutes. Last Friday, her team left at 3pm for the first time in years."

Spotting stories in the wild: support tickets (problems + resolutions), sales calls (objections + breakthroughs), user interviews (before/after moments), internal Slack (team wins).

See references/stories.md when you need to build a narrative—it has the three story plots, the product-story structure, and methods for collecting real stories.

The Curse of Knowledge

How it manifests: jargon your audience doesn't know; skipping context that seems "obvious"; assuming your audience sees what you see; over-abstracting because you know the specifics.

Solutions: test messaging with outsiders (not your team); use concrete language, not abstractions; tell stories, not bullet points; ask "would my mom understand this?"

See references/curse-of-knowledge.md when your own message reads clearly but lands flat on others—it has diagnosis and remedies for shared-context blind spots.

Applying SUCCESs to Product

Landing Pages

  • Simple: one clear value proposition above the fold
  • Unexpected: counterintuitive claim or statistic
  • Concrete: specific outcome ("save 4 hours/week" not "save time")
  • Credible: customer logos, specific testimonials
  • Emotional + Stories: customer pain point and transformation narrative

Product Demos

  • Simple: show ONE core workflow, not every feature
  • Unexpected: start with the "aha moment", not a tour
  • Concrete: use real data, not "Lorem ipsum"
  • Credible: show how [specific company] uses it
  • Emotional + Stories: "Let me show you what happens when [customer] has this problem..."

Onboarding

  • Simple: one action per screen
  • Unexpected: delight with a quick win early
  • Concrete: show real results, not abstract promises
  • Credible: "Join 5,000 teams already using..."
  • Emotional + Stories: celebrate first success; "here's how [user] got started..."

See references/applications.md when applying SUCCESs to a specific format—it has element-by-element tables, fill-in templates, and before/after examples for landing pages, demos, onboarding, presentations, email campaigns, internal comms, and documentation. See references/case-studies.md for full worked teardowns (JFK's moonshot, the Subway diet, Don't Mess with Texas) when you want to see all six traits operating together in a famous message.

Common Mistakes

MistakeWhy It FailsFix
Burying the leadCore message lost in detailsCommander's Intent: what's the ONE thing?
Too abstractNothing to rememberReplace every abstraction with a concrete example
Feature listingNo emotional connectionTell customer stories, show transformations
JargonCurse of KnowledgeTest with outsiders
Statistics without contextNumbers don't stickMake stats human-scale and relatable

Quick Diagnostic

The single scoring instrument. Score each trait 1-10, fix the lowest, then re-score:

TraitQuestionIf weakFix
SimpleCan I state the core in one sentence?Too complexFind the Commander's Intent
UnexpectedWould this surprise someone?Predictable = forgettableFind the counterintuitive angle
ConcreteCan I picture it happening?Too abstractAdd specific, sensory details
CredibleWhy should someone believe this?No credibilityAdd proof, examples, Sinatra Test
EmotionalDoes it make me feel something?Purely logicalFocus on one person, not statistics
StoriesIs there a story?List of factsWrap in character + problem + resolution

Sum the six scores and band per Scoring above.

Further Reading

For the complete framework and research:

  • "Made to Stick" by Chip Heath & Dan Heath
  • "Switch" by Chip Heath & Dan Heath (companion: how to make change stick)

About the Authors

Chip Heath is a professor at Stanford Graduate School of Business, and Dan Heath is a senior fellow at Duke University's CASE center. Together they have written four New York Times bestsellers; Made to Stick spent over two years on the list, and its SUCCESs framework is used by educators, marketers, nonprofits, and product teams worldwide.

Repositorio GitHub

wondelai/skills
Ruta: plugins/sales-influence/skills/made-to-stick
0
agent-skillsai-skillsbusinessclaude-codeclaude-code-marketplaceclaude-code-plugin
FAQ

Preguntas frecuentes

¿Qué es el Skill made-to-stick?

made-to-stick es un Skill de Claude creado por wondelai. Los Skills agrupan instrucciones y recursos que Claude carga cuando los necesita para realizar tareas relacionadas con made-to-stick sin indicaciones adicionales.

¿Cómo instalo made-to-stick?

Usa los comandos de instalación de esta página: añade made-to-stick a Claude Code como plugin o clona su repositorio en tu directorio de skills y reinicia Claude para cargarlo.

¿A qué categoría pertenece made-to-stick?

made-to-stick pertenece a la categoría Comunicación.

¿Se puede usar made-to-stick gratis?

Sí. made-to-stick aparece en AIMCP y se puede instalar gratis.

Habilidades relacionadas

himalaya-email-manager
Comunicación

Esta habilidad de Claude permite gestionar correos electrónicos a través de la herramienta CLI de Himalaya utilizando IMAP. Permite a los desarrolladores buscar, resumir y eliminar correos de una cuenta IMAP mediante consultas en lenguaje natural. Úsala para flujos de trabajo automatizados de correo, como obtener resúmenes diarios o realizar operaciones por lotes directamente desde Claude.

Ver habilidad
imsg
Comunicación

imsg es una herramienta CLI para macOS que te permite interactuar programáticamente con iMessage/SMS a través de la aplicación Mensajes. Permite a los desarrolladores listar chats, ver el historial de mensajes, observar conversaciones en tiempo real y enviar mensajes o archivos adjuntos. Usa esta habilidad para automatizar tareas de mensajería o integrar funcionalidades de iMessage/SMS en tus flujos de trabajo de desarrollo.

Ver habilidad
internationalization-i18n
Comunicación

Esta habilidad de Claude proporciona orientación integral para implementar internacionalización (i18n) y localización en aplicaciones. Cubre tareas clave como extracción de mensajes, gestión de traducciones, formato específico por localización y soporte para idiomas de derecha a izquierda (RTL) utilizando bibliotecas como i18next y gettext. Úsela al construir aplicaciones multilingües o al agregar funciones de localización para usuarios internacionales.

Ver habilidad
wacli
Comunicación

wacli es una herramienta de línea de comandos que permite el envío de mensajes, la búsqueda y la sincronización a través del protocolo WhatsApp Web. Se utiliza principalmente dentro de flujos de trabajo de Clawdis para manejo automatizado, pero puede invocarse directamente para enviar mensajes, sincronizar chats o consultar el historial. Sus características clave incluyen autenticación mediante código QR, sincronización continua en segundo plano y la capacidad de enviar tanto texto como archivos.

Ver habilidad