Team Narrative
Donchitos/Claude-Code-Game-Studios
Orchestrate the narrative team — narrative-director, writer, world-builder, level-designer — for story, world lore, narrative-driven levels.
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene.
MITAuto-check passed
Install Story Architecture
$ npx skills add BingHanOfUESTC/open_agent_team --skill story-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team story-architecture --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/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teams/story_team/skills/story-architecture .claude/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .claude/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architectureType 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 BingHanOfUESTC/open_agent_team --skill story-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team story-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teams/story_team/skills/story-architecture .agents/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .agents/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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 BingHanOfUESTC/open_agent_team --skill story-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team story-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teams/story_team/skills/story-architecture .cursor/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .cursor/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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/BingHanOfUESTC/open_agent_team.git --path teams/story_team/skills/story-architecture--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 BingHanOfUESTC/open_agent_team --skill story-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team story-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teams/story_team/skills/story-architecture .gemini/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .gemini/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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 BingHanOfUESTC/open_agent_team story-architectureInstalls 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 BingHanOfUESTC/open_agent_team --skill story-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .github/skills && cp -r skills-src/teams/story_team/skills/story-architecture .github/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .github/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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 BingHanOfUESTC/open_agent_team --skill story-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team story-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teams/story_team/skills/story-architecture .opencode/skills/story-architecture && 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-architecture" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/story_team/skills/story-architecture into .opencode/skills/story-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "story-architecture", 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.
Facts
- Skill name
story-architecture- GitHub stars
- 106
- Token cost
- ~726 tokens
- SKILL.md length
- 337 words
- Files
- 4
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene.
- Structuring story at any level
- SKILL.md covers Structural Levels, What Makes Structure Work and Resources
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Designing chapter outlines
What it does
Story Architecture is an agent skill from BingHanOfUESTC/open_agent_team. Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `resources/arc-design.md`, `resources/chapter-and-scene.md` and `resources/structural-problems.md`).
The repository describes itself as: Build persistent multi-agent teams that collaborate like real organizations to deliver complex tasks. The licence is MIT.
When your agent uses it
- Structuring story at any level
- Designing chapter outlines
- Evaluating whether narrative structure serves the storys goals
Example prompts
- “/story-architecture”
What it can do on your machine
Read from SKILL.md and the folder at commit 7e28736. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Story Architecture loads about 726 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 337 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from BingHanOfUESTC/open_agent_team at commit 7e28736, republished under its MIT licence (© BingHanOfUESTC). 337 words, ~726 tokens.
Download SKILL.mdSave it as
.claude/skills/story-architecture/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- story-architecture
- description
- Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.
- type
- reference
- model-invocable
- false
Story Architecture
Structure story at multiple levels so that each scene, chapter, and arc serves the larger narrative. The patterns here apply across methodologies (three-act, hero's journey, kishotenketsu, etc.): adapt them to what the story needs.
Structural Levels
Stories operate at nested scales. Decisions at one level constrain and enable decisions at others.
Saga/Series: the full story spanning multiple arcs. What's the overarching question or transformation? How do arcs build on each other?
Arc: a self-contained narrative movement spanning multiple chapters. Each arc has its own question, rising tension, and resolution, but also advances the saga-level story. An arc that resolves its own conflict but doesn't change anything at the saga level is filler.
Chapter: a unit of reading. Chapters need internal momentum (something changes by the end) and external momentum (the reader wants to continue).
Scene: the fundamental building block. A scene happens in a specific time and place, involves specific characters, and changes something. Scenes that don't change anything are candidates for cutting or combining.
What Makes Structure Work
Causation over sequence. "And then" is not structure. "Therefore" and "but" are. Events should cause or complicate each other, not merely follow each other. Can you reorder the scenes without the story breaking? If yes, the structure is a sequence, not a plot.
Stakes that escalate. Each structural level should raise the stakes from the previous one. Escalation doesn't always mean bigger explosions — stakes can escalate emotionally, morally, or informationally.
Setup and payoff. Every significant payoff needs setup, and every significant setup needs payoff. The best setups are invisible until the payoff arrives. Track open setups explicitly across arcs.
Tension and release. Sustained tension becomes numbness. The reader needs variation in intensity at every scale: within scenes, chapters, and arcs.
Resources
resources/arc-design.md: arc components (hook, complications, midpoint shift, crisis, resolution) and arc pacing.resources/chapter-and-scene.md: chapter design (internal completeness, external pull), scene design (earning presence), outline vs discovery writing.resources/structural-problems.md: common problems (saggy middle, rushed ending, filler arcs, disconnected scenes, stakes plateau) and when to use diagrams.
© BingHanOfUESTC, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in teams/story_team/skills/story-architecture of BingHanOfUESTC/open_agent_team.
- SKILL.md
- resources/arc-design.md
- resources/chapter-and-scene.md
- resources/structural-problems.md
Open the folder on GitHubat commit 7e28736
Compare with similar skills
Story Architecture 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 Architecture this skillBingHanOfUESTC/open_agent_team | 106 | — | ~726 | Automated safety check: Pass | MIT | |
| Team NarrativeDonchitos/Claude-Code-Game-Studios | 26k | — | ~4.5k | 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 | |
| Deck Narrative Arcmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Story Readiness
Donchitos/Claude-Code-Game-Studios
Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.
Job Stories
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.
User Stories
phuryn/pm-skills
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
Deck Narrative Arc
mohitagw15856/pm-claude-skills
Give a deck a spine the room can follow — the situation-complication-resolution arc, the tension that makes the recommendation feel necessary, the transitions that carry the thread between slides…
Create Stories
Donchitos/Claude-Code-Game-Studios
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria.
More from BingHanOfUESTC/open_agent_team
All 30 skills in this repoSkill Validation And Evaluation
BingHanOfUESTC/open_agent_team
A skill your agent uses when validating a newly created or updated agent skill with structure checks, routing positive and negative examples, contamination checks, progressive disclosure review, and…
Autoresearch Orchestration
BingHanOfUESTC/open_agent_team
A skill your agent uses when autoresearchteam needs to manage an end-to-end research lifecycle from Boss brief to literature, idea, implementation, experiments, synthesis, and LaTeX delivery.
Experiment Iteration Loop
BingHanOfUESTC/open_agent_team
A skill your agent uses when designing, running, logging, diagnosing, or iterating experiments for the selected research idea.
Latex Paper Artifact
BingHanOfUESTC/open_agent_team
A skill your agent uses when producing the final arXiv-style LaTeX paper, BibTeX, figures, tables, reproducibility statement, appendix, and artifact manifest.
Literature Evidence Mapping
BingHanOfUESTC/open_agent_team
A skill your agent uses when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Media Asset Sourcing
BingHanOfUESTC/open_agent_team
A skill your agent uses when PPT slides need external images, screenshots, logos, product photos, stock-like visuals, diagrams, or videos that must be downloaded, inserted, or linked with source and…
Questions about Story Architecture
What does Story Architecture do?
Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Story Architecture is an agent skill from BingHanOfUESTC/open_agent_team. Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene.
When should I use Story Architecture?
Story Architecture fits situations like: structuring story at any level; designing chapter outlines; evaluating whether narrative structure serves the storys goals.
How do I install Story Architecture in Claude Code?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill story-architecture -a claude-code`. Or copy the skill folder (teams/story_team/skills/story-architecture in BingHanOfUESTC/open_agent_team) into .claude/skills/story-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Story Architecture in Codex?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill story-architecture -a codex`. Or copy the skill folder (teams/story_team/skills/story-architecture in BingHanOfUESTC/open_agent_team) into .agents/skills/story-architecture in your project. Codex loads it when a task matches its description.
Can I use Story Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BingHanOfUESTC/open_agent_team --skill story-architecture -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-architecture, .gemini/skills/story-architecture, .github/skills/story-architecture and .opencode/skills/story-architecture in your project.
What does Story Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Story Architecture is instructions for the agent only.
Does Story Architecture access the network?
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.
Is Story Architecture safe to install?
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.
What licence does Story Architecture use?
Story Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Story Architecture use?
About 726 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Story Architecture?
Skills that share tags, products or a category with Story Architecture: Team Narrative (Donchitos/Claude-Code-Game-Studios, 26k stars), Story Readiness (Donchitos/Claude-Code-Game-Studios, 26k stars), Job Stories (phuryn/pm-skills, 27k stars) and User Stories (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Story Architecture?
BingHanOfUESTC (a GitHub user) maintains it in BingHanOfUESTC/open_agent_team, which has 106 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on June 23, 2026.
Source: BingHanOfUESTC/open_agent_team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.