Agent skills for writers: prompts, skill packs, plugins, MCP
Oh Story · Updated 2026-10-15
An agent skill is a folder of instructions and reference files that a compatible agent host such as Claude Code or Codex can load for a matching task. You do not write code to use one. For a novelist the tasks include turning an idea into an outline, importing a manuscript or revising a chapter against project notes. Oh Story is a pack of 13 fiction skills that use the model configured in the host. A prompt expresses a request and can be saved as a template; a skill packages a reusable process and its resources. A plugin distributes capabilities, while an MCP server exposes tools through a protocol. Pick the writing job first, then the host. The example below compares two investigation openings in chat before any planning files are created.
Method fromstory5 method files
Before you start
- One concrete writing task and material you own or are authorized to use. A premise, a chapter needing revision or an unfinished manuscript is enough to choose a starting point.
- For Oh Story, a configured supported agent host and a writing-project folder. The writing tasks below involve no coding: you open the right folder, follow the installation instructions and review requested file/tool access. If you prefer not to manage that setup, see the separate ZenStory Workbench.
Steps
- Decide whether a prompt is enough For “suggest five titles” or a one-off paragraph edit, a clear prompt is usually enough. Prompts can also be reusable templates. Consider a skill when you repeatedly paste the same process, refer to the same resources or need a consistent handoff between research, outlining and revision. Packaging gives you a repeatable process; you still judge each answer on its merits.
- Distinguish the instruction from the package A skill has a SKILL.md entry with metadata and instructions, and may include references, templates or scripts. A compatible host discovers it and loads relevant instructions when needed. “Skill pack” is an informal name for a collection of related skills; the Agent Skills standard defines the format of a single skill. Oh Story groups writing, import, analysis and revision tasks this way.
- Separate the model, host, plugin and MCP connection The model generates responses; the host runs the session and manages tools and permissions. In Claude Code, a plugin is a distribution container that can include skills, agents, hooks and MCP servers. MCP is a protocol for connecting AI applications to external data and tools; a skill sits in a separate layer. These layers can work together. Installing a skill gives the host instructions to load, and the model itself stays unchanged.
- Choose the entry by what you already have Only an idea: use story-long-write to plan a long-form project, or story-short-write for a short story. Existing manuscript: follow the import and continuation guide to rebuild the project first, then ask for chapter 21. A draft needing editorial feedback: use story-review; a passage needing less formulaic wording: use story-deslop and the annotated prose revision example. Unsure which to pick? Ask the story router to choose. Oh Story specializes in Chinese web-fiction workflows, and its review rubrics are set for web fiction. If the premise is still loose, the first-reply example below asks for two concrete starts and their open choices without launching a project.
- Install one matching route, then work in your book folder The Oh Story project page shows the npx skills installation path. In Claude Code, that path uses /story-setup, followed by a fresh session and /story. The Claude Code marketplace plugin has namespaced commands such as /oh-story:story-setup instead. Use the commands of the path you actually installed. Other hosts differ in command syntax and in their support for hooks and specialist agents.
- Can I plan the novel without having AI write it? Yes: a new-book request such as /story-long-write 帮我开书 defaults to planning and stops before prose unless you also ask for a chapter or daily writing. Planning writes the requested settings and outlines. Tracking is initialized when you explicitly move a new book into chapter drafting. If you only want to compare ideas, ask in ordinary chat: “Discuss two possible structures in this reply only; do not start the new-book workflow or create or change files.” That sentence is a boundary you set in the request; file access itself stays under the host's permission settings. A bare /story-long-write diagnoses the project and offers next steps; the full plan comes from a new-book request.
- Ask for the whole-book structure, then chapter outlines in batches Name the deliverables: the whole-book volume overview, volume outlines and the first batch of up to ten chapter outlines. The volume overview maps the larger direction; chapter outlines specify what characters do in the next stretch. Later chapter outlines follow in rolling batches, one plot unit at a time. A request to “plan the whole book” delivers the requested book or volume structure; ask explicitly for chapter outlines when you want them. An explicit chapter range can be delivered in successive batches. For an existing book, name the unfinished range and skip the new-book workflow, which is for starting a project; use the scoped revision example in outline to chapter to protect already agreed material.
- Resolve author decisions without approving every small detail In the coastal-mystery brief below, repairing old radios, family avoidance, close-third-person viewpoint and observable-clue rule are agreed constraints. The central mystery and the family’s role are still open. Ask for one or two alternatives and how each changes clues, character choices and the eventual reveal; do not let a proposed culprit become an established fact. The documented workflow allows incidental invention and records reusable additions within the agreed framework. Whole-book truths, mainline changes or conflicts with earlier decisions need the author’s ruling; affected material waits while independent planning can continue. Once you choose, have the decision saved in the relevant settings and finish the affected outlines before explicitly requesting prose. If the character card is detailed but the story still will not move, use character motivation to connect a goal, personal reason and habitual tactic to a concrete choice.
- Continue from the same project folder On the next session, return to the same writing folder and ask what is already established and what comes next. Point to the exact chapter or passage when requesting revisions. Keep author preferences separate from facts about this book, and ask the agent to write each correction into the relevant project records, since the next session works from those records. For DeepSeek Harness, use the separate DSH writing guide.
Example
Example
In Claude Code, after the npx skills installation and /story-setup, open a fresh session in your writing folder. The requests below are suggestions to adapt.
With only a premise, ask for one reply that helps you choose You can discuss the idea before you have a complete character dossier, a final chapter count or any software vocabulary. Separate what you have decided, what remains open and what this reply should deliver. Start with an ordinary-chat comparison, and save “help me start a book” for when you want planning files.
A brief you can adapt: “So far I have decided: a coastal setting, a protagonist who repairs old radios and avoids family conflict, close third person and observable clues without a supernatural solution. Length and the central mystery remain open. In this reply only, compare two investigation openings: what she does first, what resists her and what each option still needs me to decide. Do not start new-book planning or any other skill, scan rankings, research external sources, create or change files, or draft chapter prose. Label added people, objects and clues as proposals.” This states the work boundary for the reply; on tool-enabled hosts, file access is still governed by the host's own permission settings.
An original illustration of a first reply These openings are alternatives: two different ways the same story could begin. The collection slip, customers and repair marks are new material proposed for this comparison and stay proposals until you adopt them.
Direction one: trace an object's history from a collection slip. One proposed opening has a customer bring an old radio with a collection slip bearing a family member's name. She wants to establish whether the slip really belongs with this machine but avoids asking her family directly. She could begin by questioning the person who delivered it and checking a visible identifier. The obstacle is that the same name does not yet explain what the family member did. The author still chooses whether the slip leads toward earlier safekeeping, repair or a transfer, and how the family was involved. Treat the name as a lead; falsification would need evidence of its own. This direction brings private relationship pressure into the investigation early.
Direction two: begin with two customers' conflicting accounts. One proposed opening has two people claim the same old radio, each giving a detail related to a visible repair mark. The protagonist selects one checkable claim to question and vouches for neither speaker, however certain they sound. The obstacle: the two accounts differ, yet both may be true, because the radio may have changed hands between them. The author still chooses which account she pursues first, what observable evidence exists and whether her family participated in a transfer. This direction first puts her in a face-to-face disagreement. Its family connection still has to be built into the plot, beyond a line in her character description.
This is enough for the first discussion: would you rather begin with a private relationship complicating an inquiry, or with the protagonist handling two people's disagreement? Each option supplies a first action. The whole-book truth, the family’s role and the final reveal stay open for your later rulings, and chapter outlines come with the planning request. After you choose a direction, each proposed person, object and clue can still be kept, rejected or left open; the first exchange can leave some of them unsettled.
Next: ask for something more specific than “continue” If undecided, name one comparison to develop: “Keep direction two's face-to-face disagreement and explain how it can press on her avoidance of family conflict. Still proposals only; do not make a new relationship an established fact.” The next reply then develops that one point and leaves the genre, character dossier and opening as they are. When ready to create a writing project, put your chosen direction into the new-book request below and list the central truth and family role that remain undecided. That request leaves both open for author decisions; if you have already decided, replace those two lines with your rulings so each item is marked either fixed or pending. Choosing an investigation opening settles one direction; the required settings and affected chapter outlines still come before an explicit prose request.
When ready to create planning files: /story-long-write 帮我开书 Plan an original Chinese-language coastal mystery serial. The protagonist repairs old radios and avoids confronting her family. Use close third person. Clues must be observable; no supernatural solution. Deliver the premise, character constraints, whole-book volume overview, volume outlines and the first ten chapter outlines. Stop before prose. Do not decide the central mystery or the family's role for me: list one or two options and the affected outlines; pause affected material until I choose, and continue independent planning. At the stopping point, list files created or changed, the completed outline range and pending author decisions. Say whether initial tracking has been created; do not claim it is initialized if the outline stage is still incomplete.
If choices remain, resolve them first and explicitly ask to save the chosen settings and complete the remaining planning—still no prose. After reviewing and revising the completed plan: /story-long-write 写第1章 Follow the agreed outline. Let the conflict emerge through dialogue and action. Write only chapter 1, then summarize the changed project records.
Expected files
- For the optional chat-only first request: two proposed openings, their first actions, obstacles and author choices. The comparison lives in the chat reply; project files and whole-book planning come with the later new-book request.
- Setup creates the host-specific skill/configuration files for the chosen installation. Those files make up the working environment around your book.
- Planning files include settings, 大纲/大纲.md (the whole-book volume overview), 大纲/卷纲_第X卷.md (volume outlines) and separate 大纲/细纲_第XXX章.md chapter outlines. Report the range actually completed and the unresolved decisions; call the whole book planned only after the sections that depend on those decisions are done.
- When you explicitly request the new book’s first chapter, the writing workflow initializes its tracking state before drafting: a chapter-zero checkpoint, a continuation context card and empty clue/timeline views. Planning alone does not create these records. Planned reveals stay in the outlines until prose establishes them. For an imported book, inspect its reconstructed project before requesting continuation.
- Chapter continuity comes from project records such as tracking state, so preserve the writing folder and back up material you want to keep.
- Once a chapter plan exists, use outline to chapter to turn abstract plot labels into visible evidence, choices and consequences, without forcing a twist into every chapter.
Check the result
- Before accepting a chapter, read it yourself: check that the intended scene works, the character choices are believable and the facts stay consistent.
- Review installation trust and model/service configuration separately. The skills are open source; model usage, including any quota or cost, comes from the model service configured in your host, and that service decides where inference runs, even when the skill files sit on your own computer.
Sources
- Agent Skills: format and progressive disclosure
- Claude Code: skills and host-specific extensions
- Claude Code: plugin packaging and namespaces
- MCP: connecting AI applications to external systems
- Oh Story: installation paths and host differences
- Oh Story: skill purposes and natural-language entry
- Story router: task selection and import order
- Current task routing: bare invocation, planning stop and explicit prose
- Rolling outline batches and explicit chapter ranges
- Existing-outline locks and future facts
- Reusable settings and author decisions
- Planning artifacts and initial tracking
- Current workflow source (2026-10-15)
- Current workflow source (2026-10-15)