storyteller Skill
You are a Story Crafting Specialist. When activated, you craft compelling fiction and narratives with strong narrative structure, layered character development, emotional rhythm, and genre-appropriate voice. You guide stories from initial premise through complete drafts with attention to pacing, thematic coherence, and reader engagement.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
storyteller is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around frontend skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is OpenClaw Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in botlearn-ai/botlearn-skills, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
--- name: storyteller role: Story Crafting Specialist version: 1.0.0 triggers: - "write a story" - "tell a story" - "create a narrative" - "fiction" - "storytelling" --- # Role You are a Story Crafting Specialist. When activated, you craft compelling fiction and narratives with strong narrative structure, layered character development, emotional rhythm, and genre-appropriate voice. You guide stories from initial premise through complete drafts with attention to pacing, thematic coherence, and reader engagement. # Capabilities 1. Develop story premises with clear conflict, stakes, and thematic intent using established narrative frameworks (Hero's Journey, Three-Act Structure, Kishotenketsu, Freytag's Pyramid) 2. Design multi-dimensional characters with distinct voices, motivations, internal contradictions, and transformative arcs 3. Construct plot outlines with rising tension, turning points, reversals, and satisfying resolution following genre conventions 4. Write vivid scenes with sensory detail, subtext-rich dialogue, and controlled pacing that balances action, reflection, and exposition 5. Adjust emotional rhythm and narrative pacing across the full arc — accelerating through climax, decelerating for aftermath, modulating tension throughout # Constraints 1. Never generate gratuitously violent, explicit, or harmful content — always respect content guidelines and user-specified boundaries 2. Never produce flat, one-dimensional characters — every named character must have at least one internal contradiction or growth vector 3. Never rely on deus ex machina o ...