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
simbajigege/book2skills/skills/creating-superfans-hodak/SKILL.md
Apply Brittany Hodak's SUPER Model for customer loyalty, referrals, word of mouth, personalization, service recovery, and scalable customer experience.
Decision brief
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.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/simbajigege/book2skills --skill "skills/creating-superfans-hodak"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
Review the “Workflow Inventory” section in the pinned source before continuing.
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…
Use this skill when the user asks how to:
Review the “Routing Rules” section in the pinned source before continuing.
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…
Permission review
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
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 146 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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
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 | User question pattern | Inputs | Output | Subskill |
|---|---|---|---|---|
| Superfan diagnosis | "Why are customers not coming back or referring?" | Customer segment, current journey, retention/referral symptoms | Ladder stage, apathy diagnosis, weak SUPER pillar | M1 |
| Story positioning | "How do we differentiate without lowering price?" | Brand origin, values, market, customer promise | Story intersection and category-of-one positioning | M2 |
| Customer understanding | "Who are our customers and what do they really want?" | Customer type, conversations, reviews, support notes | Customer STORY map and voice-of-customer questions | M3 |
| Personalization | "How do we make customers feel seen?" | Customer signals, CRM fields, journey stage, boundaries | Personalization actions and triggers | M4 |
| Exceed expectations | "How do we create word of mouth or memorable experiences?" | Journey touchpoints, expectations, emotional moments | Repeatable experience moments and advocacy triggers | M5 |
| Service recovery | "A customer had a bad experience. What should we do?" | Failure details, customer impact, relationship context | 5 As recovery plan and prevention fix | M6 |
| Repeatable supergroups | "How do we scale CX across teams?" | Team structure, processes, feedback loops, employee experience | System, ownership, metrics, and cross-functional rollout | M7 |
Use this skill when the user asks how to:
| User question type | Must run | Optional run |
|---|---|---|
| "How do I improve retention or repeat purchase?" | M1 -> M3 -> M5 -> M7 | M4 |
| "How do I get more referrals or word of mouth?" | M1 -> M2 -> M5 -> M7 | M4 |
| "How do I differentiate without lowering price?" | M2 -> M3 -> M5 | M7 |
| "How do I understand my customers better?" | M3 | M1 |
| "How do I personalize this journey/message/gift?" | M3 -> M4 | M7 |
| "How do I wow customers?" | M5 | M3, M4, M7 |
| "A customer had a bad experience. What should I do?" | M6 -> M7 | M3 |
| "How do I scale customer experience as we grow?" | M1 -> M7 | M2 through M6 as needed |
| "How should marketing/sales/support/social apply SUPER?" | M7 | M2, M3, M5, M6 |
references/case_library.md.Each module owns its own citation library:
main-framework-quotes.md copied into their module reference libraries.customer-understanding-quotes.md.personalization-quotes.md.exceeding-expectations-quotes.md.apology-recovery-quotes.md.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.
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 | Path | Status |
|---|---|---|
| M1 Superfan Diagnosis | subskills/m1_superfan_diagnosis/ | Available |
| M2 Story Positioning | subskills/m2_story_positioning/ | Available |
| M3 Customer Understanding | subskills/m3_customer_understanding/ | Available |
| M4 Personalization | subskills/m4_personalization/ | Available |
| M5 Exceed Expectations | subskills/m5_exceed_expectations/ | Available |
| M6 Service Recovery | subskills/m6_service_recovery/ | Available |
| M7 Repeatable Supergroups | subskills/m7_repeatable_supergroups/ | Available |
Frequently asked questions
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.
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
garrytan/gbrain
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.
alirezarezvani/claude-skills
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
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
prowler-cloud/prowler
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