oh-story-claudecode
Claude Code / Codex / OpenCode agent skills for writing Chinese web novels (网文): 扫榜、拆文、写作、去AI味、封面全流程，长篇短篇都支持 | 13 skills for novel writing and long-form fiction with file-based continuity tracking. MIT.
Runssource: GitHubhomepagePythonMITcommit 4a50d5583590
Python, MIT licensed. The project labels itself: agent skills, ai agent, ai novel writing, ai writing, antigravity, chinese novel, claude code and claude code skills.
oh-story-claudecode runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
oh-story-claudecode repo installs cleanly (npm install, 0 vulnerabilities). Dashboard server starts on port 43110, serves all API endpoints (/api/workspace, /api/tree, /api/file, /api/search, /health, static bundle) correctly. 27/27 unit tests pass. All 13 CI guard suites pass. Prose-net-parity all 4 layers pass after fixing a test fixture where node was never truly removed from PATH.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test-prose-net-parity.sh failed because the "node absent" test scenario still had node in PATH (/usr/bin), so node was never truly unavailable; only "/usr/bin:/bin" were in PATH2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- node --test tests/dashboard-server.test.mjs: 27 passed, 0 failed. Dashboard server live: health 200, static page 200+10KB, workspace 2 projects, tree 9 entries, file read with version hash, search returned results, PUT file mutation with version-gated concurrency. CI guards: static-check 13/13 PASS, skill-numbering 356 files, doc-budget OK, shared-files OK, hook-regex-sync OK, current-skill-contracts OK, agent-notes OK, adapters all 6 PASS, prose-net-parity 4 layers PASS, story-setup-deployment all PASS
- Model tokens used
- 155,229
- Exact commit tested
- 4a50d5583590
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
printf '\"launch_succeeded\":true,'
printf '\"install_minutes\":8,'
printf '\"errors\":[{\"msg\":\"test-prose-net-parity.sh failed because the \\\"node absent\\\" test…
printf '\"test_depth\":\"tier1_real\",'
printf '\"verified_how\":\"node --test tests/dashboard-server.test.mjs: 27 passed, 0 failed. Dashbo…
printf '\"final_state\":\"oh-story-claudecode repo installs cleanly (npm install, 0 vulnerabilities…
printf '}\\n'" in /work/repo
succeeded in 0ms:
The ARGUSIC_RESULT line has been emitted. All verification is complete and the result is a single p…
tokens used
155,229
The ARGUSIC_RESULT line has been emitted. All verification is complete and the result is a single p…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 19 agent-skills projects Argusic has installed and timed, oh-story-claudecode was the 14th fastest to reach a running state, and 14 of 19 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-skillsai-agentai-novel-writingai-writingantigravitychinese-novelclaude-codeclaude-code-skillsclaude-skillscodexcreative-writingfiction-writingnovel-writingopenclawopencodeskillweb-novelwebnovelwriting-assistantzenstory
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/oh-story-claudecode)Questions
- Does oh-story-claudecode run?
- Yes. oh-story-claudecode runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test oh-story-claudecode?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4a50d5583590. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test oh-story-claudecode?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does oh-story-claudecode take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does oh-story-claudecode need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing oh-story-claudecode?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does oh-story-claudecode compare with the alternatives?
- Of the 19 agent-skills projects Argusic has installed and timed, oh-story-claudecode was the 14th fastest to reach a running state, and 14 of 19 reached one at all.
- Where is the evidence for oh-story-claudecode?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.