rmarsigli
UserA local hub for AI-assisted analysis and writing, with human at its core
Categories
Indexed Skills (22)
analyze-chapter
Analyzes one manuscript chapter for AI-generation markers across 14 stylistic categories, producing a structured _analysis.md with literal quotes, suggested treatments, and a prioritized verdict. Cross-references the persona, preserve list, and recurrence map before flagging anything. Use when the user asks to analyze a chapter, check a chapter for AI tics, or run analyze-chapter.
build-worldbuilding
Builds or updates .project/knowledge/worldbuilding.md as a consistency contract — rules with costs and knowledge distribution, plus the deliberately-unexplained list that protects the book's mysteries. Extract mode pulls rules from an existing manuscript; create mode co-builds through dialogue. Use when the user asks to build the worldbuilding, extract world rules, or define the world.
check-arc
Maps character trajectories, thematic development, and the tension curve from beats on the page, then compares against intent — finding flat stretches, rushed turns, abandoned threads, and unearned endings. Use when the user asks to check the arcs, map tension, or asks whether a character's arc is landing.
check-consistency
Checks chapters against the project's established facts — world rules, timeline math, character invariants, and knowledge states (who knows what, when). Flags only real contradictions with citations from both sides; never resolves silently. Use when the user asks to check consistency, run a continuity check, or asks whether a chapter contradicts anything.
commit
Writes a git commit for a book repository using p10t's commit convention — infers the type and scope from what actually changed, proposes a single line, and commits only after the author approves. Warns before moving the revision boundary that review-revision depends on. Use when the author asks to commit, says "commit this", or runs /commit. Never invoked by another skill.
consolidate-style
Mines the accumulated decision history — R annotations, revision log, the author's own rewrites — for patterns (three occurrences make a pattern; one makes an anecdote) and proposes evidence-backed updates to persona.md, applied only after the author's ruling. Use when the user asks to consolidate the style, or every 3-5 revised chapters.
create-character
Builds or updates a character sheet in .project/knowledge/characters/ — voice-first (verbatim sample lines), consistency rules, and the want/need/fear/lie engine. Extract mode pulls the character from an existing manuscript and detects voice drift; create mode develops a new character through dialogue. Use when the user asks to create, develop, extract, or update a character.
define-localization
Builds the crossing contract for one target-language edition — every style rule and persona signature classified as crossing intact, crossing with another tool, or not crossing at all, plus the typographic profile, the target-language tic watchlist, and the edition's own AI declaration. Run once per target language, before any chapter is translated. Use when the user asks to set up a translation, add a target language, or define how the book crosses into another language.
define-persona
Builds or updates the author's voice document (.project/config/persona.md) by extracting hypotheses from their corpus and refining them through interview — the persona is extracted, not invented. Runs in bootstrap mode (first build) or update mode (incorporate learnings). Use when the user asks to define or update their persona, or to work on their voice.
define-references
Builds or updates the reference sheets in .project/config/references.md — turning admired authors into concrete borrowing instructions with explicit exclusion lines, so influence seasons the voice without becoming pastiche. Use when the user asks to define references, add an author as a reference, or work on the book's influences.
draft-scene
Generates scene prose from a validated outline contract, loading the full project context — persona, references, style guide, world rules, character voices, preserve list, recurrence blocklist — and self-auditing against the 14 tic categories before delivery. The draft is a proposal marked for curation, never written into the manuscript. Use when the user asks to draft a scene or write a scene covered by an outline.
expand-beat
Turns a one-line beat or rough fragment into drafted prose — adding texture, interiority, and gesture without inventing plot beyond the beat. The author's fragments are load-bearing. Use when the user asks to expand a beat, turn a note into a scene, or develop a fragment.
init-project
Bootstraps a new book from the p10t template — seven-question interview, populates project.yaml, resets project-specific files, and routes to the right first steps (extraction path for existing manuscripts, creation path for blank pages). Never re-initializes an active project. Use when the user asks to init the project, set up this book, or start a new book.
outline-chapter
Builds a chapter's structure before any prose exists — obligations (debt to pay, seeds to plant, protections that must NOT happen) and scene contracts with purpose, conflict, and turn. The validated outline is the contract draft-scene executes against. Use when the user asks to outline a chapter or structure the next chapter.
restructure-chapter
Rebuilds the obligations of a chapter that already exists, from what is actually on the page, then proposes reordering, merging, cutting, or adding scenes to fix a diagnosed structural problem. Delivers a plan against the current structure — never rewrites the manuscript. Use when the user asks to restructure a chapter, when a chapter's problem is scene-level rather than sentence-level, or when check-arc, review-book, or revise-passage identified a structural fault.
review-book
Produces the whole-book report — literary review, commercial assessment, and technical AI-use analysis — with evidence for every claim, saved to .project/reports/literary/. Run at the end of each Act, not only at the end of the manuscript. Use when the user asks to review the book, run the full report, or review an Act.
review-revision
Evaluates the author's revision of a chapter against the R-annotated analysis file — introduced errors, rewrite quality, inverted problems, residual density, continuity gaps — and explicitly answers every question the author left in their annotations. Use when the user asks to check their notes and a chapter, review their revision, or evaluate their edits.
review-translation
Verifies a translated chapter independently of the pass that produced it — blind back-translation to expose meaning drift, a tic sweep against the target language's own markers, locked-pair and contract compliance, and staleness against the source commit. Produces its report in the project's output language, for an author who cannot audit the target language directly. Use when the user asks to review a translation, check a translated chapter, or clear a chapter for the native-reader gate.
revise-passage
Surgically rewrites a specific passage applying the full project checklist — diagnoses before cutting, preserves every author word that can stay, and presents the result as an annotated comparison, never applied directly. If the passage is fine, says so. Use when the user asks to revise, rework, or fix a specific passage, paragraph, or dialogue.
scan-recurrences
Sweeps the entire book for phrases, images, and structures repeated across chapters, distinguishing intentional motifs from accidental duplication, and updates the recurrence map in .project/reports/recurrences.md. Use when the user asks to find duplications, run scan-recurrences, or asks what repeats across chapters.
translate-chapter
Produces one chapter of a target-language edition by transcreation under the crossing contract — the book's own rules outrank fidelity to the source sentence — and delivers it with a report in the project's output language explaining every choice, so an author who cannot judge the target language can still rule on the work. Hard-stops on open lexicon terms and on an incomplete contract. Use when the user asks to translate a chapter or produce a chapter of a target-language edition.
update-preserve-list
Harvests the author's protection decisions from R-annotated analyses into .project/reports/preserve-list.md, and retires entries whose phrases were cut — proposed in batch, never promoted silently. Use when the user asks to update the preserve list or migrate their thesis decisions, or after review-revision sessions accumulate protection decisions.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.