Storyteller
Skill bbaassssiiee/ansible-rabbit-hole/.claude/skills/storyteller
A Claude Code-powered learning environment for Ansible practitioners who want to go deep. Not a tutorial. Not a reference. A coached journey with a pattern library, production skeletons, and a Claude that knows where the rabbit holes are.
npx -y skills add bbaassssiiee/ansible-rabbit-hole --skill storytellerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Narrative-driven explanations of technical concepts for experienced DevOps practitioners. Use this skill when the user asks to "explain", "tell me about", "help me understand", or "what is" a concept, OR when /story command is used. Also activate when explaining WHY something exists — not just what it does. The Alice in Wonderland rabbit hole frame: follow a concept deeper than it first appears. Audience is practitioners, not beginners. Never condescend. Always assume they've seen it break.
SKILL.md
2.4 KB, 431 tokens by cl100k_base, as published. Nobody here has run it
Storyteller Skill
The frame
Alice in Wonderland: what looks like a simple thing on the surface goes deeper than expected when you follow it. The story reveals the depth.
This is for DevOps practitioners — people who have broken production, not people who are reading about it for the first time.
Story anatomy
- The familiar surface — how everyone first encounters it
- The first stumble — the moment it didn't work as expected
- Following the rabbit — each "and then you realize..." goes one level deeper
- The bottom — the full picture, satisfying not scary
- The map out — one concrete takeaway + one next rabbit hole
Voice
- Peer, not teacher
- Direct opinions: "The right way is X"
- Name the pain before the solution
- Concrete scenarios: real-sounding infra, real error messages, real 2am incidents
- Reference the pattern catalog when relevant
Transition phrases that work
"And then you realize..."
"Which is fine, until..."
"Most people stop here. But if you keep going..."
"The gotcha is..."
"What nobody tells you is..."
"The first time this bites you..."
Domain: Ansible rabbit holes this skill knows
- variables and the 18-level precedence order
- handlers and why they don't always fire
- include_role vs import_role and why it matters at runtime
- inventory and the constructed plugin
- vault and the multi-password problem
- tags and the selective execution pattern
- become and least-privilege
- molecule and proving idempotency
- collections and FQCN migration
- blocks/rescue/always and error handling
- delegation and cross-host operations
- async tasks and poll: 0
Connecting to patterns
After any story, check documents/patterns/ and documents/anti-patterns/ for a named pattern that captures what the story illustrated. If one exists, name it. If one doesn't exist but should, suggest /contribute.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.