skills/authors-build-character/SKILL.md
Build a character entry for the project bible via an interactive interview. Usage - /authors-build-character <name> [--author <author-name>]. Optional --author flag shapes the interview questions through one of the ten author personas (e.g., --author king adds small-town and pop-culture questions; --author le-guin adds social-position questions). Use when the user is creating a new character for a long-form project and wants a structured bible entry that author personas will read before editing passages with this character.
npx skillsauth add sethshoultes/great-authors-plugin authors-build-characterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build a structured character entry in the project bible.
Not for: writing scene prose where this character appears (use /authors-channel <author> for that); editing an existing passage (use /authors-edit).
When this skill is invoked:
Parse the arguments:
--author <name>. Valid values: hemingway, orwell, didion, mcphee, king, vonnegut, baldwin, mccarthy, wallace, le-guin. Case-insensitive. If passed, note it for the builder dispatch.Verify .great-authors/ exists in the current working directory. If not, tell the user to run /authors-project-init first and stop here.
Check for existing character file. If .great-authors/characters/<name>.md already exists, ask: "A character file for <name> already exists. Overwrite? (yes/no)" — default no. If no, exit.
Dispatch the character-builder agent. Use the Agent tool with:
subagent_type: character-builderMode: interactiveCharacter name: <name>Author lens: <author> (if --author was passed, else none)Working directory: <cwd> so the sub-agent can read bible filesRelay the interview. The builder will ask questions one at a time. Pass each question through to the user verbatim, pass the user's answers back to the builder verbatim. Do not paraphrase or answer on behalf of the user.
Confirm creation. After the builder returns, confirm the file was created at .great-authors/characters/<name>.md and report back:
Created .great-authors/characters/<name>.md
Referenced by: (list any other character files that now point to this one via the Connections section, if the user chose to add a relationship)
Next: run /authors-channel <author> and paste a draft passage featuring <name>, or continue with /authors-build-character for the next character.
Agent tool semantics; it does not inherit your conversation history. Pass all necessary context in the dispatch prompt..great-authors/characters/.documentation
Dispatch a named author persona as a sub-agent to rewrite an existing manuscript file from scratch with full bible context. Usage - /authors-rewrite <file> <author>. Use when an existing chapter or scene needs more than a critique pass — when the prose itself isn't working and a clean rewrite by the named author is required. The skill assembles a self-contained brief (bible files, prior/next chapters, architecture beats, voice rules), dispatches the author, and confirms save.
tools
Top-level autonomous workflow for writing a novel end-to-end with the great-authors plugin. Composes existing skills (project-init, build-character, build-place, build-relationship, draft, channel, rewrite, continuity, critique, edit, debate, journal, consolidate) into a multi-phase pipeline with human checkpoints. The human provides direction (premise, genre, characters, voice); the AI orchestrator dispatches author personas as sub-agents to do the work. Use when a user wants the full great-authors pipeline run for them with minimal hand-holding — analogous to great-minds-plugin's agency-* workflows. Usage - /authors-orchestrate-novel, optionally with --phase <N> to run a single phase or --resume to continue from the last checkpoint.
data-ai
Run ONE editor across MULTIPLE files in parallel, then consolidate into a corpus-level pattern report. Surfaces patterns no per-file critique catches — voice drift, recurring tics, structural failures that only become visible across multiple pieces. Usage - /authors-corpus-critique <author> <path-or-glob> [<path-or-glob>...]. Different from /authors-critique (N authors on 1 file). This is 1 author on N files.
tools
Initialize the per-project memory bible (.great-authors/) in the current working directory. Creates project.md, voice.md, timeline.md, glossary.md, and empty characters/, places/, scenes/ directories. Use when the user is starting a new writing project (novel, essay collection, long-form nonfiction) and wants author personas to have persistent context across sessions.