story: Web Novel Toolkit Router

You are the router entry for the Web Novel Toolkit. Distribute user requests to specific skills when the request is ambiguous.

Routing Table

In Codex CLI, prioritize using
$story-*
or
/skills
to trigger; continue using
/story-*
for Claude Code / OpenCode; OpenClaw can use
/skill story-*
or natural language to specify the skill. The table below uses slash commands as examples. Codex can replace
/story-long-write
with
$story-long-write
equivalently, and OpenClaw can replace it with
/skill story-long-write
equivalently.

User Intent	Keyword Examples	Route to
Write long-form novels	Start a book, write outline, long-form, serialized	`/story-long-write`
Write short-form stories	Short story, Yanyan, 10,000 words	`/story-short-write`
Deconstruct long-form novels	Deconstruct, analyze this book, golden three chapters	`/story-long-analyze`
Deconstruct short-form stories	Deconstruct short story, analyze this story	`/story-short-analyze`
Scan long-form novel rankings	Long-form rankings, what's popular, Qidian/Fanqie/Jinjiang	`/story-long-scan`
Topic selection decision	What can go viral, help me choose a topic, topic direction	`/story-long-scan`
Scan short-form story rankings	Short story rankings, Zhihu Yanyan rankings	`/story-short-scan`
Remove AI tone	Remove AI tone, too AI-like, tone adjustment	`/story-deslop`
Manuscript review	Review, check manuscript, help me review, consistency check, see if there are issues	`/story-review`
Cover	Cover, cover image	`/story-cover`
Environment deployment	Prepare to write, set up environment, initialize	`/story-setup`
Browser control	Browser, crawl, login state	`/browser-cdp`
Import novel	Import, reverse parsing, import novel, import my book	`/story-import`
Workspace	dashboard, workspace, view story deconstruction library, browse project files, open project panel	See "Dashboard Workspace" below
Check/update version	Check for updates, is there a new version, upgrade, update toolkit	See "Version Update Check" below
Switch/list books	Switch book, change book, list my books, which books am I writing, switch project	See "Multi-book Switching" below
Query story materials	Query characters, query foreshadowing, query progress, query settings, what's the status, where did I leave off	Spawn `story-explorer` agent (structured prompt: `Project directory: {dir}\nQuery type: {select based on intent}\nQuery parameters: {user query}` ); see "Query Degradation" below if agent is unavailable
Research materials	Research materials, help me research, investigate, search, look up	Spawn `story-researcher` agent; see "Query Degradation" below if agent is unavailable

Import and Continuation Order

When users ask "Should I run setup or import first for importing and continuing writing?", directly answer: It is recommended to run
/story-setup
first, then
/story-import
after opening/refreshing the session, and finally
/story-long-write daily-update
or
/story-long-write write-chapter-N
. If users have directly triggered

/story-import

, follow the built-in environment check of story-import: if setup is not completed, let users choose to run setup first or continue with serial import.

Dashboard Workspace

When users execute

/story dashboard

(Codex uses

$story dashboard

), or explicitly say "Open workspace / View project files", directly launch the local Dashboard distributed with this skill, and do not forward to other skills:

Use the current working directory as the default workspace; use the specified directory if users explicitly provide it. The directory must exist.
Locate
```
scripts/dashboard-server.mjs
```
from the currently loaded
```
story
```
skill directory, do not hardcode the repository path, global skill path, or user home directory.

After verifying that

node

is available, execute as a long-running process:

bash

node "<story-skill-dir>/scripts/dashboard-server.mjs" --root "<workspace>" --open

Wait for the output showing "Local address", and return the complete URL to the user. Keep the service running if the tool supports background processes/PTY; failing to automatically launch the browser is not considered a failure, still return the clickable URL.
Dashboard only listens to
```
127.0.0.1
```
by default. Do not actively add
```
--allow-network
```
, do not expose the workspace to the local area network or public network.

The workspace will recognize the standard

Story Deconstruction Library/{Book Name}/

, and is compatible with the existing

Story Deconstruction Library-{Book Name}/

. Writing project recognition supports:

Long-form directory structure: The directory contains any of the subdirectories
```
Text/
```
,
```
Outline/
```
,
```
Settings/
```
or
```
Tracking/
```
.
Short-form single-file structure: The directory contains the regular file
```
Text.md
```
, and also contains
```
Section Outline.md
```
or
```
Settings.md
```
.

Symbolic links are not treated as project markers, and regular data directories with only a single

Text.md

will not be misidentified. The browser can edit

.md

.txt

.json

.yaml

.yml

.toml

files, and uses modification time to prevent accidental overwriting of external updates before saving or confirming deletion.

To stop the service, terminate the corresponding Node long-running process. If users only ask about usage, do not launch it for them; provide the two platform-specific entries:

/story dashboard

$story dashboard

Routing Process

Analyze user requests and extract intent keywords
Match the table above to find the corresponding skill
If a clear match is found, directly call the corresponding skill (Claude/OpenCode can use
```
Skill("skill-name")
```
or slash command; Codex uses
```
$skill-name
```
/
```
/skills
```
; OpenClaw uses
```
/skill skill-name
```
or natural language to specify)
If no match is found, ask users what they want to do (select from the table above)
If users say "I want to write a novel" but do not specify long-form/short-form, ask about the length type before routing

Query Degradation

Spawn version prompt (does not block spawn): First read
agents_version
from the project root
.story-deployed
. If it is inconsistent with the current version
agents_version: 25
(missing marker, missing/non-integer field, less than or greater than 25) still check file existence and spawn as usual, and report
Notice: agents bundle version mismatch (project {N}, current version 25)
while prompting users to re-run
/story-setup
and open a new session; if it is greater than 25, additionally prompt users to update oh-story-claudecode first, do not use the local old setup to downgrade and overwrite. Only degrade to solo/direct when agent files are missing or custom agent is not exposed during runtime, and report
Fallback: ... -> solo
.

Before using agents for "Query story materials" and "Research materials", perform a lightweight availability check (the router only does this layer, does not undertake global deployment strategy): If not in sub-agent context, Agent/Task tool is available, and

.claude/agents/{story-explorer|story-researcher}.md

.opencode/agents/{story-explorer|story-researcher}.md

.codex/agents/{story-explorer|story-researcher}.toml

exists → can attempt to spawn. If any condition is not met, or Codex runtime returns

unknown agent_type

/ does not expose custom-agent registry, degrade without hard failure:

If
```
story-explorer
```
is unavailable → The main thread directly retrieves from project files using Read/Grep (character status/foreshadowing/progress/settings), and mark
```
Fallback: agent unavailable -> direct lookup
```
before answering; prompt users to run
```
/story-setup
```
first (use
```
$story-setup
```
in Codex) if the project has not been deployed.
If
```
story-researcher
```
is unavailable → The main thread completes using existing retrieval/answering capabilities, or prompts users to use
```
/browser-cdp
```
for collection, and also mark
```
Fallback: agent unavailable -> direct lookup
```
.

Project Status Awareness

Check the current project status before routing:

No project directory (no book directory containing
```
Tracking/
```
or
```
Settings/
```
):
- If users want to write, the next step is to run
```
/story-setup
```
  to initialize the environment (use
```
$story-setup
```
  in Codex)
- If users want to scan rankings/deconstruct stories, route directly
Existing project: Check the
```
.story-deployed
```
marker, run
```
/story-setup
```
first (use
```
$story-setup
```
in Codex) if not deployed

Multi-book Switching

When users want to switch or view the books they are writing (a project can have multiple books at the same time):

Find all book directories in the project root: directories containing
```
Tracking/
```
or
```
Settings/
```
subdirectories (including subdirectories under
```
Long-form/
```
and
```
Short-form/
```
).
List the book names, and mark the one pointed to by the current
```
.active-book
```
.
Let users select, and write the relative path of the selected book into the project root
```
.active-book
```
(overwrite the original content).
If only one book is found, directly confirm it as the active book without asking.

Version Update Check

Execute when users ask "Is there a new version", "Check for updates", "Upgrade". Only notify, let users decide whether to update, do not install automatically.

Current version: Read the
```
VERSION
```
file in the same directory as this skill; treat as unknown if missing.
Latest version:优先 use
```
gh release view --json tagName,name,url -R zenstory-ai/oh-story-claudecode
```
to get
```
tagName
```
; if gh is unavailable, use
```
curl -fsS --max-time 5 https://api.github.com/repos/zenstory-ai/oh-story-claudecode/releases/latest
```
to get
```
.tag_name
```
(using jq or grep). If not found → inform "Failed to retrieve the latest version temporarily, you can check manually at Releases", do not report an error.
Comparison: Remove the
```
v
```
prefix and compare according to semantic versioning (major.minor.patch).
```
gh release
```
defaults to the latest stable version, excluding pre-releases.
Notification:
- Up to date → "Already the latest version vX.Y.Z".
- New version available → List current vA → latest vB + Releases/CHANGELOG (attach key points of this release if available), then use AskUserQuestion to ask "Update now?":
  - Select update → Run
    npx skills add zenstory-ai/oh-story-claudecode -y -g
    (
    -g
    for global, remove it to update only the current directory); after completion, prompt: Re-run
    /story-setup
    (use
    $story-setup
    in Codex) in the project root of deployed projects to synchronize hooks/agents/references, and open a new session to re-register agents.
  - Select later → Do nothing, inform users they can come back anytime.

story

NPX Install

Tags

SKILL.md Content (Chinese)