book-writing-workspace — Claude Code skill: manuscript workspace setup
book-writing-workspace turns a book repo into a structured workspace: section files, a reader persona, agent files and a review loop, with Re:VIEW and PDF output as an option.
CC-BY-NC-SA-4.0 244 installs ★ 27 updated 2026-10-23
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a claude-codeWhat book-writing-workspace does
The skill sets a manuscript repo into a fixed layout: chapters as individual files under sections/, outlines kept apart in keypoints/, figures in images/. It starts by auditing what the repo already holds. A new project comes from python scripts/setup_workspace.py, given a name, title, parent path and chapter count.
What lands in the repo: agent and instruction files under .github/agents/ and .github/instructions/, planning docs for personas, page budget, schedule and release readiness, plus scripts/count_chars.py. Then the loop — reviewer findings at P1 and P2, each chapter checked against the declared reader persona and its completion outcomes.
Print output is opt-in. Add --with-review and you also get conversion scripts and config/review-metadata/project.yml to fill in. Skip the flag and those files never appear in a fresh workspace. The setup script is Python, so have an interpreter ready. Page budget deserves a built count: character estimates overshoot, and an author build differs from the publisher's page count.
What it helps with
- split a manuscript into one file per section
- pin down the target reader once and audit chapters against it
- work through proofreader comments item by item
- check chapter length before handing text to typesetting
- add PDF output only to projects that need it
Example prompts for the agent
- Audit the
my-bookrepo and tell me which files to rename so it matches the skill layout. - Compare the interfaces chapter against
docs/reader-personas.mdand flag passages aimed at the wrong reader. - Turn on Re:VIEW and PDF support for this project and fill in
config/review-metadata/project.yml.
How to install book-writing-workspace
1Skills CLI (Vercel)
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a claude-code2Manually: put the files in place
~/.claude/skills/book-writing-workspace/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/book-writing-workspace/
1Skills CLI (Vercel)
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a codex2Manually: put the files in place
.agents/skills/book-writing-workspace/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a cursor2Manually: put the files in place
.cursor/skills/book-writing-workspace/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aktsmm/Agent-Skills book-writing-workspace2Manually: put the files in place
.github/skills/book-writing-workspace/SKILL.md1Skills CLI (Vercel)
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a gemini-cli2Platform CLI
gemini skills install https://github.com/aktsmm/Agent-Skills --path book-writing-workspaceManually: put the files in place
.devin/skills/book-writing-workspace/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about book-writing-workspace
How do I install book-writing-workspace in Claude Code?
Run npx skills add aktsmm/Agent-Skills --skill book-writing-workspace -a claude-code. The skill then sits at ~/.claude/skills/book-writing-workspace/SKILL.md.
What does book-writing-workspace do?
It builds and maintains the repo layout for a technical book: section folders, persona and page-budget docs, agent files, and a review loop.
What changes with --with-review?
The flag adds Re:VIEW conversion scripts and config/review-metadata/project.yml to the new workspace. Without it the project stays manuscript-only.