novel2agent-jp skill
novel2agent-jp guides Japanese fiction writing with an agent: TOML settings, script checks, human approval, multi-model revision.
- 107 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Python scripts run locally and read project files.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/novel2agent-jpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Python scripts run locally and read project files.
This is third-party code. Review the repository files before installing.
What it does
novel2agent-jp is a skill for writing a Japanese novel together with a coding agent. Characters, world, plot and chapters are described in TOML files, while chapter prose lives only in `novel/chNN.md`. The `scripts/validate.py` script checks files and `scripts/pack.py` builds a regenerable context pack, `.context/chNN.md`, that goes to the model. The process is split into phases with stops: agent suggestions get the `proposed` status and only a human moves them to `confirmed`. Character changes are tracked in `[[versions]]`, chapter events in `[[established]]`, and revision compares answers from several models. It has character sheets with over 40 items, illustration prompts and export for pixiv and Kakuyomu.
Who it is for. Authors writing Japanese prose with an agent who want names, world and plot to stay consistent from chapter to chapter.
Good fit when
- A multi-chapter novel: characters change and their versions need tracking.
- Revision runs on several models with side-by-side answer comparison.
- A context pack must be built before writing the next chapter.
- A finished chapter is converted for pixiv, Kakuyomu or vertical EPUB.
Not a fit when
- Texts and prompts are needed in a language other than Japanese.
- A one-off story without settings files is enough.
- You want fully automatic text without approval stages.
Example request
Start the planning phase of a new novel, create TOML for the main characters and show suggestions marked `proposed` for my approval.Limitations
All material, including instructions, is in Japanese. The flow demands discipline: phases stop until approval, and Python scripts run locally. Vertical PDF and EPUB use the separate `novel2epub-jp` project, and illustration generation relies on ComfyUI. The author states that responsibility for installation and results lies with the user. Work runs through several settings files and stages, so overhead is large for a short text.
How to disable. Delete the skill folder from the agent skills directory. Novel files (TOML and `novel/`) stay in your project.
FAQ
Where do I clone the repository?
The README command puts it into `~/.hermes/profiles/<name>/skills/novel2agent-jp`. Other agents use their own skills directory.
What are `proposed` and `confirmed` for?
Agent suggestions do not become canon without your confirmation.
What does `scripts/pack.py` do?
It builds a Markdown pack, `.context/chNN.md`, from TOML, and it can be regenerated at any time.
Which agents does it work with?
The README names Hermes, Claude Code, opencode and goose.
Which output formats exist?
Chapters can be converted for pixiv and Kakuyomu, while vertical PDF and EPUB come from the separate `novel2epub-jp` project.
Discussion
No questions or reviews yet.
Related
SkillsFour skills for a person with several AI assistants: a task register, evidence-based acceptance, beginner instructions
Personal agent context in plain Markdown files you own, plus an onboarding skill built on a short interview
cafe3310's personal skill collection: spec-driven project work, reviews, reports, browser, 3D and video in one repository
AGT Skill Pack gives an agent 24 free skills: review by another model, idea screening, UI checks and decision tracking
Twenty-two standalone skills: Notion, Todoist, Tavily, Context7, image generation, converting documents to Markdown
A scaffold for Claude Code and Codex: tasks in files, developer and QA roles, manual approval and shared state.
README in short
The README covers features, installation, project structure and version history. It has a sample story on note.com and links to related export utilities.