author-handoff
Use when creating or restoring a concise author-toolkit session handoff for a new chat or another host without copying manuscript, Story Bible, creation state, draft-baseline, or fresh reader-state content.
How do I install this agent skill?
npx skills add https://github.com/shengchen1998/author-toolkit --skill author-handoffIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The author-handoff skill is a project management tool designed to track and transfer the state of a creative writing project between sessions or different computer systems. It creates concise metadata files (handoffs) that record which parts of a project are currently being worked on without exposing the actual content of the manuscript or sensitive project data. No malicious patterns or security risks were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Author Handoff
Create or restore a portable pointer to shared project state. Accept create or restore, a project root, and optionally a handoff path. Toolkit skills from one installation are siblings. Resolve <setup-skill-root> as ../setup-author-toolkit relative to this skill's installed directory and use the controlled workflow terminology in <setup-skill-root>/assets/references/terminology.md for shared terms and exact contract values. If author-project reports an incomplete toolkit installation, stop creation or restoration and report the missing installed files; do not deploy contracts into the project.
Create
- Read
../author-project/SKILL.mdand../author-project/references/read-operations.md, then run itsread,validate, and ordinarystatusprocedures separately. Pass the current scope ID through--scope-idwhen available. If the manifest is missing, display the host command for user-invokedsetup-author-toolkitand stop. If its schema version is not3.1.0, report that it is unsupported and stop without changing it. Treat recorded statements of current-draft revision convergence as historical; when a handoff recommendsrevise-requestorrevise-increment, apply that strategy's entry gate for this state, including strict execution status, instead of forwarding the statement as verified. - Read the registered audit tracker, current revision or writing plan, active creation batch, review job, and recent session notes. Include only decisions explicitly approved by the author. Treat proposals, open findings, and model recommendations as open questions or paths, not approved decisions.
- Start with
assets/handoff-template.md. Record current scope and confirmation status, pending action and status, blocked or stale evidence with reasons, shared approvals, unresolved questions, portable paths, and one next action. Link reports and finding IDs instead of reproducing findings. - Resolve creation artifacts through registered
paths.creation. Record creation pointers when present: creation batch ID and path, staging directory, chapter and volume/phase state paths, commit ID and journal path, coverage index, review job ID and path, and fresh reader-state path. Record the last explicitly invoked skill and recommend the actualwrite-fiction,revise-fiction,revise-draft,revise-increment, orrevise-requestcommand for the next action. This recommendation is advisory and does not change scope or pending action. - Resolve the manifest's
paths.handoffsdirectory and write the handoff to<paths.handoffs>/<UTC-stamp>_<scope-id-slug>.mdunless the author supplied another in-project path. The default for a new manifest is.author-toolkit/handoffs/; an existing custom directory takes precedence. Use a unique filename and leave prior handoffs unchanged. - Return the handoff path and the exact command for restoring it on the current host.
Keep manuscript, Story Bible, draft-baseline, creation batch, chapter or volume state, commit content, and full findings out of the handoff. Do not include chapter excerpts, character bios, plot summaries, prose rewrites, baseline text, or full audit findings. Fresh-reader state remains independent: include only its path and review job identity, never its observations or another perspective's state. Paths, finding IDs, approval IDs, batch and commit IDs, and concise approved decision summaries provide continuity.
Restore
- Read the supplied handoff and resolve its project root. Use the stored absolute root only when it exists on this host; otherwise ask for or use the supplied local root and resolve every relative path against it.
- Run
author-projectseparately withread,validate, and ordinarystatus, passing the current scope ID through--scope-idwhen available, when a v3.1 manifest is available. Confirm the manifest creation timestamp and manuscript root recorded in the handoff, then reconcile it with newer shared state. Current manifest, tracker, approval, batch, commit, and evidence state wins; retain unresolved questions that still apply. Before recommending an entry that requires a previous or base scope to have reached current-draft revision convergence, apply that strategy's complete procedure for this state and its strict-execution gate. If strict status fails, report the execution blocker and showrevise-draftrather than recommending the dependent entry. - If the manifest is missing, display the host command for
setup-author-toolkitso the author can register the project. Do not start that user entry internally. If its schema version is not3.1.0, report that it is unsupported and stop without changing it. - Display current scope, pending action and status, blocked or stale evidence, creation and review pointers, approved decisions by reference, unresolved questions, and the exact next action. Include an advisory
write-fiction,revise-fiction,revise-draft,revise-increment, orrevise-requestcommand based on the author's explicit goal. Wait for the author to start it. Restoration alone does not edit a manuscript, change shared state, resume pending writes, or continue a review job.
Switching among all five strategies at a stable operation gate preserves shared project state and does not change current scope. A fresh review resumes only through its own reader-state path and the layered-review procedure. For a new session on the same host, use the handoff path as restore input. For another host, copy the project and handoff, then run author-handoff with the local project root and handoff path. The receiving host needs the skill files used by the next action.
Host commands
Start author-handoff, write-fiction, revise-fiction, revise-draft, revise-increment, and revise-request through the current host's skill command or skill picker with unqualified registered skill names. Never present an internal skill call as an author-facing command.
Creation is complete when the file contains only approved handoff categories and every referenced path resolves or is marked missing. Restoration is complete when the author can see current shared state and the next command; neither result implies operation completion.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/shengchen1998/author-toolkit/author-handoff">View author-handoff on skillZs</a>