Source profileQuality 92/100

simbajigege/book2skills/skills/creating-superfans-hodak/SKILL.md

creating-superfans-hodak

Apply Brittany Hodak's SUPER Model for customer loyalty, referrals, word of mouth, personalization, service recovery, and scalable customer experience.

Source repository stars
146
Declared platforms
0
Static risk flags
0
Last source update
2026-08-20
Source checked
2026-08-25

Decision brief

What it does: where it fits

Knowledge source: Creating Superfans: Turning Everyday Customers into Enthusiastic Advocates by Brittany Hodak, 2023. Architecture: Orchestrator + 7 subskills. This file routes the user query; subskills execute the actual workflows.

Best for

  • Increase retention, repeat purchase, referrals, reviews, advocacy, or word of mouth
  • Diagnose why customers are satisfied but quiet
  • Differentiate a brand when products, prices, or features look similar

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/simbajigege/book2skills --skill "skills/creating-superfans-hodak"
Safe inspection promptEditorial

Inspect the Agent Skill "creating-superfans-hodak" from https://github.com/simbajigege/book2skills/blob/f90fa7a78e4c78c92312d06fd70f7d24282c937f/skills/creating-superfans-hodak/SKILL.md at commit f90fa7a78e4c78c92312d06fd70f7d24282c937f. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow Inventory

    Review the “Workflow Inventory” section in the pinned source before continuing.

    Review and apply the “Workflow Inventory” source section.
  2. 02

    Skill Purpose

    Help founders, marketers, sales teams, customer success leaders, support teams, and operators turn ordinary customers into enthusiastic advocates. Hodak's core idea is that superfans are created where the brand's story intersects with the customer's story, then reinforced throug…

    Help founders, marketers, sales teams, customer success leaders, support teams, and operators turn ordinary customers into enthusiastic advocates. Hodak's core idea is that superfans are created where the brand's story…This is not a paid ads, SEO, pricing, funnel analytics, or generic growth-hacking playbook. Use it when the question involves customer experience, loyalty, retention, referrals, reviews, advocacy, service recovery, or c…
  3. 03

    When to Use This Skill

    Use this skill when the user asks how to:

    Increase retention, repeat purchase, referrals, reviews, advocacy, or word of mouthDiagnose why customers are satisfied but quietDifferentiate a brand when products, prices, or features look similar
  4. 04

    Routing Rules

    Review the “Routing Rules” section in the pinned source before continuing.

    Review and apply the “Routing Rules” source section.
  5. 05

    Execution Rules

    1. Read only the modules required by the routing table. 2. If a module depends on upstream context, run the upstream module first. 3. Pass each module's output into the next module when routed as a sequence. 4. If context is thin, ask for the customer type, product or service, c…

    Read only the modules required by the routing table.If a module depends on upstream context, run the upstream module first.Pass each module's output into the next module when routed as a sequence.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars146SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
simbajigege/book2skills
Skill path
skills/creating-superfans-hodak/SKILL.md
Commit
f90fa7a78e4c78c92312d06fd70f7d24282c937f
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

Creating Superfans - Skill (Brittany Hodak)

Knowledge source: Creating Superfans: Turning Everyday Customers into Enthusiastic Advocates by Brittany Hodak, 2023. Architecture: Orchestrator + 7 subskills. This file routes the user query; subskills execute the actual workflows.

creating-superfans-hodak/
├── SKILL.md
└── subskills/
    ├── m1_superfan_diagnosis/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m2_story_positioning/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m3_customer_understanding/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m4_personalization/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m5_exceed_expectations/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m6_service_recovery/
    │   ├── module.md
    │   └── references/case_library.md
    └── m7_repeatable_supergroups/
        ├── module.md
        └── references/case_library.md

Skill Purpose

Help founders, marketers, sales teams, customer success leaders, support teams, and operators turn ordinary customers into enthusiastic advocates. Hodak's core idea is that superfans are created where the brand's story intersects with the customer's story, then reinforced through understanding, personalization, expectation-exceeding experiences, recovery, and repeatable systems.

This is not a paid ads, SEO, pricing, funnel analytics, or generic growth-hacking playbook. Use it when the question involves customer experience, loyalty, retention, referrals, reviews, advocacy, service recovery, or cross-functional customer centricity.

Workflow Inventory

WorkflowUser question patternInputsOutputSubskill
Superfan diagnosis"Why are customers not coming back or referring?"Customer segment, current journey, retention/referral symptomsLadder stage, apathy diagnosis, weak SUPER pillarM1
Story positioning"How do we differentiate without lowering price?"Brand origin, values, market, customer promiseStory intersection and category-of-one positioningM2
Customer understanding"Who are our customers and what do they really want?"Customer type, conversations, reviews, support notesCustomer STORY map and voice-of-customer questionsM3
Personalization"How do we make customers feel seen?"Customer signals, CRM fields, journey stage, boundariesPersonalization actions and triggersM4
Exceed expectations"How do we create word of mouth or memorable experiences?"Journey touchpoints, expectations, emotional momentsRepeatable experience moments and advocacy triggersM5
Service recovery"A customer had a bad experience. What should we do?"Failure details, customer impact, relationship context5 As recovery plan and prevention fixM6
Repeatable supergroups"How do we scale CX across teams?"Team structure, processes, feedback loops, employee experienceSystem, ownership, metrics, and cross-functional rolloutM7

When to Use This Skill

Use this skill when the user asks how to:

  • Increase retention, repeat purchase, referrals, reviews, advocacy, or word of mouth
  • Diagnose why customers are satisfied but quiet
  • Differentiate a brand when products, prices, or features look similar
  • Improve customer experience across marketing, sales, onboarding, service, community, or social media
  • Personalize customer touchpoints without becoming intrusive
  • Recover from a bad customer experience
  • Scale excellent service through systems rather than founder heroics
  • Build a more customer-centric team culture

Routing Rules

User question typeMust runOptional run
"How do I improve retention or repeat purchase?"M1 -> M3 -> M5 -> M7M4
"How do I get more referrals or word of mouth?"M1 -> M2 -> M5 -> M7M4
"How do I differentiate without lowering price?"M2 -> M3 -> M5M7
"How do I understand my customers better?"M3M1
"How do I personalize this journey/message/gift?"M3 -> M4M7
"How do I wow customers?"M5M3, M4, M7
"A customer had a bad experience. What should I do?"M6 -> M7M3
"How do I scale customer experience as we grow?"M1 -> M7M2 through M6 as needed
"How should marketing/sales/support/social apply SUPER?"M7M2, M3, M5, M6

Execution Rules

  1. Read only the modules required by the routing table.
  2. If a module depends on upstream context, run the upstream module first.
  3. Pass each module's output into the next module when routed as a sequence.
  4. If context is thin, ask for the customer type, product or service, current touchpoints, retention/referral symptoms, and one recent customer interaction.
  5. Do not run every module for a narrow question.
  6. Every substantive recommendation should cite the relevant module's references/case_library.md.
  7. Keep direct quotes short and use them as evidence, not as the answer.

Citation Rules

Each module owns its own citation library:

  • M1 and M2 use main-framework-quotes.md copied into their module reference libraries.
  • M3 uses customer-understanding-quotes.md.
  • M4 uses personalization-quotes.md.
  • M5 uses exceeding-expectations-quotes.md.
  • M6 uses apology-recovery-quotes.md.
  • M7 uses repeatability, experience measurement, and organization-wide customer centricity references.

When a routed module contains a "Citation instruction," read that module's references/case_library.md, select the closest anchor, and include a short citation in the answer.

Multi-Module Output Format

For substantial answers, use this structure:

Creating Superfans diagnosis - [Business / Situation]

1. Current superfan stage
   - Ladder stage:
   - Apathy risk:
   - Weakest SUPER pillar:

2. Hodak principle being applied
   - [Short principle with citation]

3. Action plan
   - [2-5 specific touchpoint or system changes]

4. Artifact
   - [Script, checklist, journey map, CRM trigger, service recovery draft, or team routine when useful]

5. Measurement
   - Behavior metric:
   - Customer-story signal:

6. Watch-outs
   - [The mistake most likely to weaken the plan]

For quick answers, provide the diagnosis, the next action, and one citation.

Subskill Status

SubskillPathStatus
M1 Superfan Diagnosissubskills/m1_superfan_diagnosis/Available
M2 Story Positioningsubskills/m2_story_positioning/Available
M3 Customer Understandingsubskills/m3_customer_understanding/Available
M4 Personalizationsubskills/m4_personalization/Available
M5 Exceed Expectationssubskills/m5_exceed_expectations/Available
M6 Service Recoverysubskills/m6_service_recovery/Available
M7 Repeatable Supergroupssubskills/m7_repeatable_supergroups/Available

Do Not

  • Do not confuse awareness with caring; many growth problems are apathy problems.
  • Do not treat satisfied customers as superfans unless they advocate voluntarily.
  • Do not prescribe tactics before connecting the brand's story to the customer's story.
  • Do not recommend personalization that is intrusive, creepy, or primarily brand-centered.
  • Do not suggest grand gestures before fixing basic consistency.
  • Do not treat service recovery as only compensation; require emotional repair and system repair.
  • Do not tolerate abusive or wrong-fit customers in the name of customer centricity.
  • Do not let customer experience depend on a single heroic employee.

Frequently asked questions

What to verify before installation and use

What does the creating-superfans-hodak source document cover?

Knowledge source: Creating Superfans: Turning Everyday Customers into Enthusiastic Advocates by Brittany Hodak, 2023. Architecture: Orchestrator + 7 subskills. This file routes the user query; subskills execute the actual workflows.

How do I install creating-superfans-hodak?

The source record exposes this install command: npx skills add https://github.com/simbajigege/book2skills --skill "skills/creating-superfans-hodak". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,034

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,122

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance