Summary
If you're writing a technical book and need more than a folder full of Markdown files, this sets up a complete manuscript workspace with per-section files, writing and review agents, page allocation docs, and character counting scripts. It defaults to a clean Markdown workflow but can scaffold Re:VIEW and PDF build tooling when you pass the flag. The agent setup is nice: a dedicated writing agent and a separate reviewer that flags P1/P2/P3 issues. Built by someone who clearly writes technical books in Japanese and English, so the bilingual triggers and attention to manuscript structure feel lived-in. It won't manage your Git commits, which is the right call.
Install to Claude Code
npx -y skills add aktsmm/agent-skills --skill book-writing-workspace --agent claude-codeInstalls into .claude/skills of the current project.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.mdView on GitHub
Book Writing Workspace
Create and maintain a reusable manuscript workspace with folders, writing agents, instructions, review rules, and optional Markdown -> Re:VIEW -> PDF support.
When to use
- Book writing, technical writing, 執筆プロジェクト, Re:VIEW
- Assessing or standardizing an existing book manuscript repository
- Creating a new technical writing project from templates when needed
- Setting up Markdown → Re:VIEW → PDF workflow
- Upgrading an existing manuscript workspace so it can generate Re:VIEW output and printable PDFs
- Standardizing chapter/section file layout, writing rules, review workflow, and page allocation
- Adding optional Re:VIEW/PDF support without turning the writing workspace into a general Git or publishing operations toolkit
Quick Start
Start by assessing the manuscript workspace, even when creating a new project:
- Confirm the main manuscript lives in
sections/and uses one file per section. - Confirm outlines or key points live separately from final manuscript files.
- Confirm chapter intro files use kebab-case naming (e.g.
00-introduction/00-introduction.md). - Confirm writing, heading, notation, page allocation, and review rules are available.
- Decide whether Re:VIEW/PDF output is needed for this project; keep it optional unless the workflow requires it.
Operating Workflow
When the workspace already exists, do not stop at setup-oriented advice. This skill should also support:
- Normalizing manuscript folders and section naming.
- Keeping outlines, drafts, final manuscript, and images aligned by chapter.
- Running focused writing and review loops until P1/P2 issues are resolved.
- Checking word count targets and source confidence before finalizing text.
- Enabling Re:VIEW/PDF support only when the project needs reproducible output.
Bootstrap Workflow
Use the setup script only when creating a new workspace or adding missing structure deliberately.
python scripts/setup_workspace.py `
--name "project-name" `
--title "Book Title" `
--path "D:\target\path" `
--chapters 8
# Include Re:VIEW/PDF scaffolding only when needed.
python scripts/setup_workspace.py `
--name "project-name" `
--title "Book Title" `
--path "D:\target\path" `
--chapters 8 `
--with-review
- Gather info: Project name, title, location, chapter count
- Run script:
scripts/setup_workspace.py - Review output: Confirm README, agents, instructions, and docs were created
- Customize: Edit
docs/page-allocation.md,docs/schedule.md, and.github/copilot-instructions.md. If--with-reviewis used, also customizeconfig/review-metadata/project.yml.
Git workflows are project-specific. Do not add generic commit/push prompts here; follow the repository's existing version-control conventions.
Metadata, migration, converter verification, and sync-back rules live in references. Keep the main SKILL focused on manuscript structure and writing workflow.
Generated Workspace
- Manuscript folders under
keypoints/,sections/, andimages/ - AI workflow files under
.github/agents/and.github/instructions/ - Project docs such as
README.md,docs/page-allocation.md, anddocs/schedule.md - Helper scripts such as
scripts/count_chars.py - Optional Re:VIEW scripts and metadata when
--with-reviewis used
Recommended Writing Unit
- Use 1 file = 1 section as the default manuscript unit.
- Keep chapter intro in
{NN}-{slug}/{NN}-{slug}.mdand section files alongside it. - For PDF/Re:VIEW output, heading levels define hierarchy, while file split mainly improves authoring and review workflow.
Agents Overview
| Agent | Role | Default |
|---|---|---|
@writing | Write and edit manuscripts | Yes |
@writing-reviewer | Review manuscripts (P1/P2/P3) | Yes |
@converter | Convert Markdown to Re:VIEW | Only with --with-review |
Dependencies
| Tool | Purpose | Required |
|---|---|---|
| Python 3.8+ | Scripts | Yes |
| Git | Version control | Yes |
| Docker | Re:VIEW PDF build | Optional, only with --with-review |
Reference Map
| Topic | Reference |
|---|---|
| Folder structure | references/folder-structure.md |
| Setup workflow | references/setup-workflow.md |
| Customization points | references/customization-points.md |
| Re:VIEW / PDF tips | references/review-pdf-tips.md |
Done Criteria
- Workspace folder structure created
- Writing and review agents deployed to
.github/agents/ -
docs/page-allocation.mdconfigured -
README.mdanddocs/schedule.mdcustomized - Manuscript files follow the chapter/section naming convention
-
scripts/count_chars.pyworks for target manuscript files - Re:VIEW/PDF output is either explicitly out of scope or enabled and verified
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
