MCP HubMCP Hub
스킬 목록으로 돌아가기

made-to-stick

wondelai
업데이트됨 2 days ago
6 조회
1,096
121
1,096
GitHub에서 보기
커뮤니케이션powerpoint

정보

이 스킬은 SUCCESs 프레임워크(단순성, 예상치 못함, 구체성, 신뢰성, 감정, 스토리)를 활용하여 개발자들이 기억에 남고 영향력 있는 메시지를 만들 수 있도록 돕습니다. 사용자가 강렬한 메시지를 구성하거나 복잡한 설명을 단순화하거나 프레젠테이션 및 피치 덱을 개선해야 할 때 작동합니다. 이 도구는 특히 "지식의 저주"를 해결하여 아이디어가 명확히 이해되고 기억될 수 있도록 보장합니다.

빠른 설치

Claude Code

추천
기본
npx skills add wondelai/skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/wondelai/skills
Git 클론대체
git clone https://github.com/wondelai/skills.git ~/.claude/skills/made-to-stick

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Made to Stick Framework

A framework for crafting ideas and messages that are understood, remembered, and have lasting impact. 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. This makes us bad at explaining our ideas to others.

The foundation: 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. When reviewing or creating messaging (copy, presentations, campaigns, onboarding), rate 0-10 based on SUCCESs principles. A 10/10 means the message is simple, surprising, concrete, credible, emotional, and wrapped in a story; lower scores indicate forgettable communication. Always provide current score and improvements to reach 10/10.

The SUCCESs Framework

Six principles that make ideas stick:

S - Simple
U - Unexpected
C - Concrete
C - Credible
E - Emotional
S - Stories

Not a checklist — a toolkit. Not every sticky idea uses all six. But the stickiest ideas tend to use most of them.

1. Simple

Core concept: Find the core of the idea and share it compactly.

Simple ≠ dumbed down. Simple means finding the essential core and expressing it in a compact way. It means ruthless prioritization.

The Commander's Intent:

  • Military term: If everything 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
  • Add detail in order of decreasing importance
  • 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)
PrioritizeForce-rank what matters"If you say 3 things, you say nothing"

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? If not, simplify.

Warning: Don't oversimplify to the point of meaninglessness. "We make the world better" is simple but empty.

See: references/simple.md for simplification exercises and templates.

2. Unexpected

Core concept: Get attention by breaking patterns. Hold attention by creating curiosity gaps.

Two tasks:

  1. Get attention → Surprise (violate expectations)
  2. Hold attention → Interest (create curiosity gaps)

Surprise:

  • Identify the core message
  • Figure out the counterintuitive implication
  • Communicate the surprise

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)

Curiosity gaps:

  • Open a gap in knowledge → create desire to fill it
  • "Before I tell you the answer, let me ask..."
  • Mystery format: Present a puzzle, delay the resolution
  • Challenge assumptions: "You think X, but actually Y"

Creating curiosity gaps:

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"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. The surprise must connect to the core message.

See: references/unexpected.md for pattern-breaking techniques.

3. Concrete

Core concept: Use sensory language and specific details instead of abstract concepts.

Abstract kills memorability. The more concrete and specific your 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" for memory
  • "Bicycle" is easier to remember than "vehicle" (you can picture it)
  • Sensory details create mental images

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"
DemonstrationShow, don't tellProduct demo > feature list
Before/afterTangible transformation"Before: 4 hours. After: 10 minutes."

Application to product messaging:

  • Features → Outcomes (what it does → what changes for user)
  • Percentages → Real numbers ("saves 40%" → "saves 16 hours/month")
  • Categories → Specific examples ("restaurants" → "pizza shops in Brooklyn")

See: references/concrete.md for concreteness exercises.

4. Credible

Core concept: Help people believe your idea using internal and external credibility.

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 (more powerful):

TechniqueHow It WorksExample
Vivid detailsSpecificity implies truth"On Tuesday at 3pm, in the conference room on the 4th floor..."
StatisticsBut make them human-scaleNot "$1B market" but "1 in 4 businesses"
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"
Human-scale statisticsRelate numbers to experienceNot "10TB of data" but "every book ever written, 100 times"

The Sinatra Test:

  • One reference so impressive it handles all objections
  • "We secured the White House" = instant security credibility
  • "We handle Super Bowl traffic" = instant scalability credibility
  • "Used by Apple, Google, and Microsoft" = instant quality credibility

Making statistics sticky:

  • Don't: "37 grams of saturated fat"
  • Do: "More saturated fat than a Big Mac, fries, and milkshake combined"
  • Rule: Put statistics in a context people understand

See: references/credible.md for credibility-building techniques.

5. Emotional

Core concept: Make people feel something. People act on emotion, not analysis.

Mother Teresa principle: "If I look at the mass, I will never act. If I look at the one, I will."

Key insight: Statistics numb. Stories about individuals inspire action.

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 make decisions based on identity, not calculation
  • "What would a person like me do in this situation?"
  • Frame your product as consistent with who they want to be

Examples:

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"

Avoiding the "semantic stretch":

  • Don't over-abstract the emotion
  • "Support the troops" > "Support our national defense infrastructure"
  • Keep it personal and specific

See: references/emotional.md for emotional appeal frameworks.

6. Stories

Core concept: Stories are flight simulators for the brain. They teach people how to act.

Why stories work:

  • Simulate experience (mental rehearsal)
  • Inspire action (not just understanding)
  • Are memorable (narrative structure)
  • 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:

  1. Character: Who is the customer? (relatable)
  2. Problem: What challenge did they face? (emotional)
  3. Journey: What did they try? (concrete)
  4. Solution: How did your product help? (specific)
  5. Outcome: What changed? (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:

  • Customer support tickets (problems + resolutions)
  • Sales calls (objections + breakthroughs)
  • User interviews (before/after moments)
  • Internal Slack (team wins)

See: references/stories.md for story templates and collection methods.

The Curse of Knowledge

The biggest enemy of sticky ideas.

Definition: Once you know something, you can't imagine not knowing it.

How it manifests:

  • Using jargon your audience doesn't know
  • Skipping context that seems "obvious"
  • Assuming your audience sees the same things you do
  • 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?"

Sticky Messaging Audit

Rate your message on each principle:

PrincipleQuestionScore (1-10)
SimpleIs there ONE clear core message?
UnexpectedDoes it break a pattern or create curiosity?
ConcreteCan you picture it? Are there specific details?
CredibleWhy should someone believe this?
EmotionalDoes it make you feel something?
StoriesIs there a narrative or character?

Scoring:

  • 50-60: Extremely sticky (rare, aim for this)
  • 35-49: Strong (most good messaging lands here)
  • 20-34: Average (forgettable, needs work)
  • Below 20: Won't stick (fundamental rework needed)

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: Customer story or pain point
  • Stories: Customer 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: Connect to the pain they feel today
  • Stories: "Let me show you what happens when [customer] has this problem..."

Onboarding

  • Simple: One action per screen
  • Unexpected: Delight with quick win early
  • Concrete: Show real results, not abstract promises
  • Credible: "Join 5,000 teams already using..."
  • Emotional: Celebrate first success
  • Stories: "Here's how [user] got started..."

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

Audit any message:

QuestionIf NoAction
Can I state the core in one sentence?Too complexFind Commander's Intent
Would this surprise someone?Predictable = forgettableFind the counterintuitive angle
Can I picture it happening?Too abstractAdd specific, sensory details
Why should someone believe this?No credibilityAdd proof, examples, Sinatra Test
Does it make me feel something?Purely logicalFocus on one person, not statistics
Is there a story?List of factsWrap in character + problem + resolution

Reference Files

Further Reading

This skill is based on Chip and Dan Heath's research on sticky ideas. For the complete framework:

  • "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 2 years on the bestseller list. Their research spans organizational behavior, decision-making, and how to make ideas have lasting impact. The SUCCESs framework is used by educators, marketers, nonprofits, and product teams worldwide.

GitHub 저장소

wondelai/skills
경로: made-to-stick
0
agent-skillsai-skillsclaude-codeclaude-code-marketplaceclaude-code-pluginclaude-code-skills

연관 스킬

himalaya-email-manager

커뮤니케이션

이 Claude Skill은 IMAP을 통해 Himalaya CLI 도구를 이용한 이메일 관리를 가능하게 합니다. 개발자들이 자연어 쿼리로 IMAP 계정의 이메일을 검색하고, 요약하고, 삭제할 수 있게 해줍니다. 일일 요약 수신이나 Claude에서 직접 배치 작업 수행과 같은 자동화된 이메일 워크플로우에 활용하세요.

스킬 보기

imsg

커뮤니케이션

imsg는 macOS용 CLI 도구로, Messages.app을 통해 iMessage/SMS와 프로그래밍 방식으로 상호작용할 수 있게 해줍니다. 이 도구를 사용하면 개발자가 채팅 목록을 확인하고, 메시지 기록을 조회하며, 대화를 실시간으로 모니터링하고, 메시지나 첨부 파일을 보낼 수 있습니다. 이 스킬을 활용하여 메시징 작업을 자동화하거나 개발 워크플로우에 iMessage/SMS 기능을 통합해 보세요.

스킬 보기

internationalization-i18n

커뮤니케이션

이 Claude Skill은 애플리케이션에 국제화(i18n)와 현지화를 구현하기 위한 포괄적인 지침을 제공합니다. i18next 및 gettext와 같은 라이브러리를 활용하여 메시지 추출, 번역 관리, 로케일별 형식 지정, RTL(오른쪽에서 왼쪽) 지원 등 주요 작업을 다룹니다. 다국어 애플리케이션을 구축하거나 국제 사용자를 위한 현지화 기능을 추가할 때 활용하세요.

스킬 보기

wacli

커뮤니케이션

wacli는 WhatsApp Web 프로토콜을 통해 WhatsApp 메시징, 검색 및 동기화를 가능하게 하는 명령줄 도구입니다. 주로 Clawdis 워크플로우 내에서 자동화 처리를 위해 사용되지만, 메시지 전송, 채팅 동기화 또는 기록 조회를 위해 직접 호출할 수도 있습니다. 주요 기능으로는 QR 기반 인증, 지속적인 백그라운드 동기화, 텍스트 및 파일 전송 기능이 포함됩니다.

스킬 보기