agentleFS
tonysinatonysina/claude-skills/skills/start-with-why/SKILL.md

start-with-why

Skill2 starsChanged 6 months agoMITView on GitHub

Creates inspiring content using Simon Sinek's Golden Circle (WHY to HOW to WHAT). Use for thought leadership, speeches, brand messaging, keynotes, mission statements, or company narratives that inspire rather than manipulate. Triggers: "start with why", "golden circle", "find my WHY", "purpose-driven", "inspire not manipulate", "inside-out messaging", "celery test", or requests for content that leads with belief/purpose. Also use when user wants to diagnose why their messaging feels flat or commodity-like. Do NOT use for: product or feature copy, SEO content, or technical writing. Also not for: slides or decks, sharpening a line that already exists such as a tagline or a closing sentence (use farnsworth-rhetoric), or a high-stakes message aimed at one named individual in a live decision (use strategic-persuasion-writing, and read its scope gate first).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 18 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈18

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not every user needs full WHY discovery.

    line 42
  2. Distinctive:

    Path A -- WHY already clear: If the user provides a purpose, cause, or belief that passes the validation checklist below, skip to Step 3.

    line 44
  3. Distinctive:

    Path B -- WHY needs discovery: If the user leads with products, features, market position, or goals (money, growth, being #1), they need …

    line 46
  4. Distinctive:

    If user cannot articulate a clear WHY (purpose, cause, or belief), guide discovery:

    line 52
  5. Distinctive:

    Ask "Why does this matter?" then dig deeper with each answer

    line 61
  6. Distinctive:

    If stated WHY sounds like a WHAT in disguise, challenge it:

    line 72
  7. Distinctive:

    Should be specific enough to guide decisions

    line 83
  8. Distinctive:

    Use the Celery Test as a writing filter, not just a decision filter:

    line 92
  9. Distinctive:

    Write the WHY statement at the top of the page.

    line 95
  10. Distinctive:

    If content fails the Celery Test, flag it to the user.

    line 109
  11. Distinctive:

    Tone: Default to inspirational and authentic unless user requests otherwise.

    line 128
  12. Distinctive:

    Length: Ask user about intended use and optimize:

    line 130
  13. Distinctive:

    If user requests manipulative content, explain: "This approach may work short-term but won't build loyalty.

    line 149
  14. Distinctive:

    Read these as needed during the workflow:

    line 161
  15. Distinctive:

    Never include explicit "WHY/HOW/WHAT" labels in deliverables.

    line 203
  16. Distinctive:

    Use book examples internally to shape approach.

    line 205
  17. Distinctive:

    Ask about length requirements in context of intended platform.

    line 206
  18. Distinctive:

    Default audience: business professionals with tacit subject knowledge.

    line 207
  19. Very specific:

    Run humanizer on the draft before delivering it.

    line 215

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Start with Why Writing Skill

Create inspiring thought leadership content using the Golden Circle framework. Sourced from two Sinek books: the Golden Circle itself, the Law of Diffusion, and the "WHY Goes Fuzzy" pattern are from Start with Why (2009); the Contribution/Impact WHY-statement template in Step 2a is from the follow-up, Find Your Why (Sinek, Mead & Docker, 2017).

Core Principle

People don't buy WHAT you do, they buy WHY you do it. Inspiring content communicates from the inside out: WHY -> HOW -> WHAT. This works because the limbic brain (where decisions and loyalty originate) responds to belief and belonging, not to features and facts. The neocortex handles rational analysis, but the limbic brain drives behavior.

Workflow

1. Gather Context

Collect from user:

  • Content type (article, speech, presentation, post, etc.)
  • Intended outlet/platform and desired length
  • Target audience (default: business professionals)
  • Topic or subject matter

2. Assess Starting Point

Not every user needs full WHY discovery. Branch based on where they are:

Path A -- WHY already clear: If the user provides a purpose, cause, or belief that passes the validation checklist below, skip to Step 3. Don't force discovery on someone who's already there.

Path B -- WHY needs discovery: If the user leads with products, features, market position, or goals (money, growth, being #1), they need discovery. Go to Step 2a.

Path C -- Diagnosing flat messaging: If the user says their content "feels generic," "sounds like everyone else," or "isn't landing," check for WHY fuzziness. Signs: leading with features, competing on specs/price, messaging that could belong to any competitor. The book calls this pattern "When WHY Goes Fuzzy" -- it happens when organizations succeed and gradually lose sight of their original purpose. Ask about the founder's origin story, what the company believed before it got big, what changed. Then proceed through discovery.

2a. Discover the WHY

If user cannot articulate a clear WHY (purpose, cause, or belief), guide discovery:

Use the Contribution/Impact Formula (from Find Your Why): Help users draft their WHY using this structure: "To [contribution] so that [impact]"

  • First blank: the action taken (contribution to others)
  • Second blank: the change desired in others' lives (impact)
  • Example: "To inspire people to do the things that inspire them so that, together, we can change our world"

Apply the 5 Whys Technique (Toyoda's, not Sinek's, but it does the excavation work):

  • Ask "Why does this matter?" then dig deeper with each answer
  • Continue until reaching a fundamental belief about people, the world, or how things should be
  • The WHY comes from looking back (origins, experiences, formative moments), not forward. This is a process of discovery, not invention.

WHY Validation Checklist:

  • Is it a purpose, cause, or belief (not a result like money/success)?
  • Does it explain why the organization/person exists beyond products/services?
  • Would it remain true even if the products/services changed completely?
  • Does it speak to something bigger than the individual?

Push Back If Needed: If stated WHY sounds like a WHAT in disguise, challenge it:

  • "We make the best software" -> Ask: "WHY do you make software at all? What do you believe about the world?"
  • "We want to be number one" -> Ask: "WHY does being number one matter? What would that enable?"
  • "We help customers succeed" -> Ask: "WHY do you care about their success? What belief drives that?"
  • "We want to help people" -> Too generic. Ask: "Help people do what, specifically? What experience made you care about this?"

3. Define HOW and WHAT

HOW (Values/Guiding Principles):

  • Express as verbs, not nouns ("always do the right thing" not "integrity"). Verbs are actionable and guide real decisions; nouns become wall art that nobody follows.
  • These are actions taken to realize the belief
  • Should be specific enough to guide decisions

WHAT (Tangible Proof):

  • Products, services, actions, results
  • Everything said and done that proves the WHY
  • Apply Celery Test: Does this WHAT align with the WHY?

4. Apply the Celery Test to Your Draft

Use the Celery Test as a writing filter, not just a decision filter:

Before Drafting: Write the WHY statement at the top of the page. This becomes the filter for every subsequent choice.

Audit the Draft: Review every claim, feature, story, or recommendation. Ask:

  • Does it fit with the stated WHY?
  • Would someone who knows the WHY predict this choice?
  • Does it serve as tangible proof of the belief?

The "Good Advice" Trap: Content may be valid, popular, or recommended by others, but if it doesn't align with THIS specific WHY, it's clutter. Remove it even if it's "good."

The Glance Test: Run this yourself, in writing, before delivering. Re-read only what survived the audit above -- nothing else -- and state in one sentence the belief a first-time reader would infer from it. If that sentence isn't the WHY statement from the top of the page, cut more and run it again. Report the inferred sentence to the user alongside the draft; the gap between it and the stated WHY is the most useful thing you can show them. If they have a peer to ask, offer that as a second pass -- but don't make it the only check.

If content fails the Celery Test, flag it to the user.

5. Draft Content

Structure: Weave Golden Circle naturally (see Output Guidelines below for the label rule).

  • Open with belief or cause (the WHY)
  • Show how values bring it to life (the HOW)
  • Present tangible proof (the WHAT)

Create belonging, not just agreement. The goal of inside-out content is not just to communicate a belief, but to give readers something to belong to. The book shows that 250,000 people came to hear MLK speak not for him, but for themselves -- his belief aligned with theirs. Ask: does this content make like-minded people feel seen?

Write for believers first. Per the Law of Diffusion, your content must resonate with the ~16% who already share the belief (innovators and early adopters) before it can reach the majority. Content that tries to appeal to everyone appeals to no one. Speak to those who already feel what you feel; they will spread the message to the rest. See references/diffusion-and-tipping-points.md for more detail.

Adapt to audience:

  • Executives and entrepreneurs respond to WHY-heavy content (they think in terms of purpose and vision)
  • Technical audiences need more HOW (they want to see how the belief translates to practice)
  • General consumers need the WHY to be implicit, woven into story rather than stated directly
  • Mixed audiences: lead with WHY, quickly move to HOW, let WHAT serve as proof

Tone: Default to inspirational and authentic unless user requests otherwise. Authenticity here means the Golden Circle is in balance: what you say and do aligns with what you believe. The limbic brain detects this alignment as "trust."

Length: Ask user about intended use and optimize:

  • LinkedIn posts: ~150-300 words. Three hashtags maximum, and only if the user asks for them -- hashtag stuffing reads as promotional and undercuts the belief. This skill doesn't do SEO; see the description.
  • Articles: Ask target word count (typically 800-2000 words)
  • Speeches: Ask duration target (150 words ~ 1 minute spoken)
  • Other formats: Clarify expectations before drafting

6. Avoid Manipulation Tactics

Flag and discourage these approaches (get user approval before including):

ManipulationWhat It Looks LikeWhy It Fails
PriceLeading with cost savings, discountsCreates commodity, no loyalty
FearWarning of consequences if they don't actMotivates avoidance, not belief
AspirationPromising dreams without substanceCreates short-term action only
Peer Pressure"Everyone else is doing it"Appeals to insecurity
NoveltyLeading with new features/innovationGenerates interest, not loyalty
PromotionFree stuff, limited time offersTransactions, not relationships

If user requests manipulative content, explain: "This approach may work short-term but won't build loyalty. The book shows manipulation creates stress for both buyer and seller. Would you like to find an inspiring angle instead?"

7. Review and Feedback

Re-run the Celery Test audit from Step 4 -- don't repeat it from scratch, just confirm it still holds after drafting. Then check the two things Step 4 doesn't cover:

  • Does the opening establish WHY before WHAT (ordering, not just content)?
  • Does it create a sense of belonging, or just deliver information?

Offer to revise based on feedback, but wait for user input before making changes.

Reference Files

Read these as needed during the workflow:

  • references/golden-circle-framework.md -- Read before Step 2a (Discover the WHY) if you need deeper understanding of the three circles, the biology behind them, or the Clarity/Discipline/Consistency triad.
  • references/book-examples.md -- Read before Step 5 (Draft Content) for internal examples of how Apple, Southwest, MLK, Wal-Mart, TiVo, and others communicate inside-out (or fail to). Do not cite these in outputs.
  • references/manipulation-vs-inspiration.md -- Read before Step 6 (Avoid Manipulation) when evaluating whether draft content uses manipulation tactics. Also read when the user explicitly requests persuasive or sales-oriented content.
  • references/diffusion-and-tipping-points.md -- Read when writing content intended for broad audiences, product launches, or movement-building. Covers why you must win believers before reaching the mainstream.

Use Case Examples

Use Case 1: LinkedIn Thought Leadership Post

Trigger: "Write a LinkedIn post about why our consulting firm exists" Discovery: WHY = "To help organizations see what they can't see about themselves" Output: ~250-word post opening with the belief ("Most organizations already have the answers they need -- they just can't see them from the inside"), showing HOW (asking uncomfortable questions, challenging assumptions, holding up mirrors), then WHAT (consulting engagements, strategy workshops). Closes with an invitation to belong: a question or statement that like-minded readers will identify with.

Use Case 2: Keynote Opening

Trigger: "Help me open my conference keynote about AI in healthcare" Discovery: WHY = "To give every patient the care they'd want for their own family" Output: 2-minute opening (~300 words) that starts with the belief, not with AI features. Might open with a personal story about a family member's care experience, then connect it to a broader belief about what healthcare should be. AI enters the narrative as a HOW, not as the headline.

Use Case 3: Diagnosing Flat Messaging

Trigger: "Our website copy feels generic, help me fix it" Discovery: Current copy leads with WHAT (features, pricing, "industry-leading solutions"). Help user uncover their WHY through origin-story questions. Restructure the messaging to lead with belief, moving features into supporting proof.

Troubleshooting

User can't articulate a WHY

This is the most common challenge. Don't accept vague answers like "we want to help people" or "we want to be the best" -- these are HOWs or WHATs disguised as WHYs. Use the 5 Whys technique more aggressively. If still stuck, ask about the founder's origin story: "What experience made you start this? What were you frustrated by? What did you believe the world needed?"

WHY sounds like a mission statement

Mission statements are often aspirational and forward-looking. The WHY comes from looking backward at origins and formative experiences. Redirect: "That sounds like where you want to go. Tell me about where you came from -- what made you care about this in the first place?"

User insists on manipulation tactics

Explain the short-term vs. long-term tradeoff. If they still want it, comply but flag it clearly: "This will drive transactions but not loyalty. Here's the version you asked for, and here's an alternative that leads with belief instead."

Content feels formulaic

If the output reads like a template (belief statement, then values, then products), the structure is showing through. Rewrite with the Golden Circle as invisible scaffolding: vary sentence length, use stories instead of declarations, let the WHY emerge rather than stating it upfront. The reader should feel the belief without being told "here is our belief."

User's organization has lost its WHY

This is the "WHY Goes Fuzzy" pattern from the book. Common in mature companies. Help the user trace back to the founder's original purpose. Ask: "What did this company believe before it got big? What would the founder say if they walked in today?" The WHY doesn't change -- it gets buried. The job is excavation, not invention.

Output Guidelines

  • Never include explicit "WHY/HOW/WHAT" labels in deliverables. The structure should feel like a natural narrative; labeling it makes the content feel like a textbook exercise rather than genuine communication.
  • Inform user of Golden Circle structure outside the output (in conversation). This helps them understand the method without it bleeding into the actual content.
  • Use book examples internally to shape approach; do not cite them in outputs. The user's content should stand on its own belief, not lean on Apple or Southwest as crutches.
  • Ask about length requirements in context of intended platform.
  • Default audience: business professionals with tacit subject knowledge.

Workflow Position

This skill generates prose, and generated prose carries AI tells:

start-with-why -> humanizer -> farnsworth-rhetoric

Run humanizer on the draft before delivering it. When one line carries the piece -- a keynote's last sentence, a tagline, a post's closing invitation -- run farnsworth-rhetoric last, at its 1-figure budget. Never run farnsworth first: figures applied before humanizer get stripped by it.

At Step 2a, if the user has no WHY and the first candidate passes the validation checklist, consider chaining beyond-obvious for 3-5 distinct candidates before committing -- the first statement that passes validation is rarely the truest one.

Examples of Inside-Out vs Outside-In

Outside-In (typical, uninspiring):

We make great computers. They're beautifully designed, simple to use and user-friendly. Want to buy one?

Inside-Out (inspiring):

Everything we do, we believe in challenging the status quo. We believe in thinking differently. The way we challenge the status quo is by making our products beautifully designed, simple to use and user-friendly. And we happen to make great computers. Want to buy one?

The difference: The second version leads with belief. It gives people something to belong to. The products become proof of the belief, not the reason for the conversation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.