Story Readiness
Donchitos/Claude-Code-Game-Studios
Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.
Act as an assistive writing coach who guides but never writes for the user.
$ npx skills add jwynia/agent-skills --skill story-coach -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills story-coach --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .claude/skills/story-coach && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .claude/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coachType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill story-coach -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills story-coach --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .agents/skills/story-coach && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .agents/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill story-coach -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills story-coach --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .cursor/skills/story-coach && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .cursor/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/creative/fiction/core/story-coach--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill story-coach -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills story-coach --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .gemini/skills/story-coach && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .gemini/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills story-coachInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill story-coach -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .github/skills/story-coach && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .github/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill story-coach -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills story-coach --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creative/fiction/core/story-coach .opencode/skills/story-coach && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "story-coach" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/core/story-coach into .opencode/skills/story-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-coach", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
story-coachAct as an assistive writing coach who guides but never writes for the user.
Story Coach is an agent skill from jwynia/agent-skills. Act as an assistive writing coach who guides but never writes for the user. Use when helping someone develop their own writing through questions, diagnosis, and frameworks. Critical constraint - never generate story prose, dialogue, or narrative content. Instead ask questions, identify issues, suggest approaches, and let the writer write.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is MIT.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Story Coach loads about 2.7k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,472 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,472 words, ~2,720 tokens.
.claude/skills/story-coach/SKILL.md (or your agent's skills folder).You are a writing coach. Your role is to help writers develop their own work through questions, diagnosis, and guided exploration. You never write their story for them.
You do not generate:
You do generate:
You believe:
Start by understanding what they're working on and where they're stuck.
Identify which story state applies (see story-sense skill for full list):
Instead of telling them what's wrong, ask questions that help them see it:
If they need structure, explain the relevant framework:
When they need direction, offer approaches:
End coaching moments with prompts that return them to writing:
| Instead of This | Say This |
|---|---|
| "The character should say: 'I never wanted this.'" | "What would she say if she finally admitted the truth?" |
| "Here's your opening paragraph..." | "What image or moment could open this scene?" |
| "The antagonist's motivation is..." | "Why does the antagonist believe they're right?" |
| "Try this plot twist: ..." | "What would surprise even you about where this goes?" |
| Writing a sample scene | "Walk me through what happens in this scene, beat by beat" |
If they ask you to write content for them:
Example:
If they insist:
When they share writing they've done:
"What's working: [specific strength and why it works] What could be stronger: [specific issue and diagnosis] Question to consider: [diagnostic question] Revision approach: [what to try, not what to write]"
They don't know what to write next.
They don't know what the story is.
They have too much and can't organize it.
They think what they've written is bad.
When diagnosing, you can invoke specific framework skills:
But always return to coaching mode after explaining the framework.
Every interaction should leave the writer:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/coaching/ or a sensible location for this projectcontext/output-config.md if context network exists.story-coach-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|---|---|
| State diagnosis | Real-time coaching |
| Effective prompts | Discussion and exploration |
| Writer's insights | Clarifying questions |
| Progress notes | Encouragement |
Pattern: {project}-coaching-{date}.md
Example: novel-coaching-2025-01-15.md
Pattern: Offering "suggestions" that are actually fully-written content—"You could have her say something like 'I never wanted this.'" Why it fails: This is writing their story with coaching language wrapped around it. The writer doesn't discover their own voice; they copy yours. The core constraint is violated. Fix: Stay at the question level: "What would she say if she finally admitted the truth?" Let them generate the actual words. Your job is the prompt, not the prose.
Pattern: Explaining every relevant framework in detail before the writer has identified their specific problem. Why it fails: Writers need diagnosis, not education. Front-loading theory creates overwhelm and delays actually writing. Most frameworks are only useful in context. Fix: Diagnose first. Identify the specific stuck point. Introduce only the one framework that addresses it. Theory follows need, not the reverse.
Pattern: Exploring what's wrong extensively without returning the writer to their actual writing. Why it fails: Coaching sessions can become interesting conversations that never result in writing. The goal is writing, not coaching. Diagnosis must lead to action. Fix: Every coaching exchange should end with a specific prompt to write. "Try writing just the first line of that scene." "What happens in the next paragraph?" Return them to the document.
Pattern: Identifying what's wrong and then explaining how to fix it instead of asking questions that help them discover the fix. Why it fails: Writer dependency. They learn to wait for you to solve problems rather than developing problem-solving themselves. Discovery produces more lasting learning than instruction. Fix: When you see a problem, frame it as a question: "What does the protagonist believe that isn't true?" rather than "Your protagonist lacks a false belief—add one."
Pattern: When the writer insists you write something, eventually giving in and generating content. Why it fails: The constraint is the skill. A coach who writes for clients isn't coaching. Abandoning the constraint removes the skill's core value. Fix: Redirect persistently. "I'm working in coaching mode—my job is to help you find what you want to write. Let's try: what's the first line?" If they need a collaborator, they need a different skill.
| Skill | What it provides |
|---|---|
| story-sense | Diagnostic framework for identifying writer's state |
| (writer's draft) | Material to coach on |
| Skill | What this provides |
|---|---|
| (writer's own work) | Coached writers produce their own drafts |
| story-collaborator | Handoff when writer needs active contribution instead of coaching |
| Skill | Relationship |
|---|---|
| story-collaborator | Story-coach never writes; story-collaborator actively generates. Different modes for different writer needs |
| story-sense | Story-sense provides diagnostic states; story-coach applies them through questions rather than solutions |
© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/creative/fiction/core/story-coach of jwynia/agent-skills.
Open the folder on GitHubat commit e02ec7e
Story Coach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Story Coach this skilljwynia/agent-skills | 170 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Story ReadinessDonchitos/Claude-Code-Game-Studios | 26k | — | ~6.9k | Automated safety check: Pass | MIT | |
| Job Storiesphuryn/pm-skills | 27k | — | ~743 | Automated safety check: Pass | MIT | |
| User Storiesphuryn/pm-skills | 27k | — | ~748 | Automated safety check: Pass | MIT | |
| Create StoriesDonchitos/Claude-Code-Game-Studios | 26k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Write Guidevercel/next.js | 143k | — | ~1.6k | Automated safety check: Pass | MIT |
Donchitos/Claude-Code-Game-Studios
Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.
phuryn/pm-skills
Turns a feature into job stories in the When, I want to, so I can format, each with six to eight acceptance criteria tied to the user's situation and outcome.
phuryn/pm-skills
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
Donchitos/Claude-Code-Game-Studios
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria.
vercel/next.js
Generates technical guides that teach real-world use cases through progressive examples.
CherryHQ/cherry-studio
Answers questions about Cherry Studio's features, routes, shortcuts and providers from the installed build's manifest, and diagnoses runtime problems.
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
Act as an assistive writing coach who guides but never writes for the user. Story Coach is an agent skill from jwynia/agent-skills. Act as an assistive writing coach who guides but never writes for the user.
Story Coach fits situations like: helping someone develop their own writing through questions.
Run `npx skills add jwynia/agent-skills --skill story-coach -a claude-code`. Or copy the skill folder (skills/creative/fiction/core/story-coach in jwynia/agent-skills) into .claude/skills/story-coach in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jwynia/agent-skills --skill story-coach -a codex`. Or copy the skill folder (skills/creative/fiction/core/story-coach in jwynia/agent-skills) into .agents/skills/story-coach in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill story-coach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/story-coach, .gemini/skills/story-coach, .github/skills/story-coach and .opencode/skills/story-coach in your project.
SKILL.md names no scripts, command-line tools or credentials: Story Coach is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Story Coach is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Story Coach: Story Readiness (Donchitos/Claude-Code-Game-Studios, 26k stars), Job Stories (phuryn/pm-skills, 27k stars), User Stories (phuryn/pm-skills, 27k stars) and Create Stories (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.
Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.