sethshoultes/authors-build-scene
skills/authors-build-scene/SKILL.md
Build a scene entry (beat card) for the project bible via an interactive interview. Usage - /authors-build-scene [<id>] [--author <author-name>]. Optional --author flag channels McPhee (start with scene shape) or Vonnegut (start-close-to-end and glass-of-water want). Use when the user is planning a scene, has a scene that's drifting off-structure, or wants to ensure cross-chapter callbacks don't get lost.
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add sethshoultes/great-authors-plugin authors-build-sceneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 6:54 PM35.3s1 file scanned
SKILL.md
- name:
- authors-build-scene
- description:
- Build a scene entry (beat card) for the project bible via an interactive interview. Usage - /authors-build-scene [<id>] [--author <author-name>]. Optional --author flag channels McPhee (start with scene shape) or Vonnegut (start-close-to-end and glass-of-water want). Use when the user is planning a scene, has a scene that's drifting off-structure, or wants to ensure cross-chapter callbacks don't get lost.
/authors-build-scene [<id>] [--author <author>]
Build a structured scene entry (beat card) in the project bible.
When to use
- You're planning a scene before drafting and want its shape nailed down.
- A draft scene is meandering and you need to name its turn and exit state.
- You're tracking callbacks across chapters and need a coherent scene index.
Not for: writing the actual scene prose (use /authors-channel <author> for that); editing an existing scene (use /authors-edit).
Instructions for Claude
When this skill is invoked:
-
Parse the arguments:
- First positional: scene ID (optional). If missing, ask the user for a short ID they can use to reference this scene (e.g.,
ch14-confrontation,opening-diner). Derive a kebab-case ID from their answer. - Optional flag:
--author <name>. Valid values:hemingway,orwell,didion,mcphee,king,vonnegut,baldwin,mccarthy,wallace,le-guin. Dedicated lenses ship formcpheeandvonnegut; others fall back to default with a note.
- First positional: scene ID (optional). If missing, ask the user for a short ID they can use to reference this scene (e.g.,
-
Verify
.great-authors/exists. If not, tell the user to run/authors-project-initfirst and stop. -
Check for existing scene file. If
.great-authors/scenes/<id>.mdexists, ask about overwrite — default no. -
Dispatch the scene-builder. Use the
Agenttool with:subagent_type: scene-builder- Prompt includes:
Mode: interactive,Scene ID: <id>,Author lens: <author>,Working directory: <cwd>.
-
Relay the interview. Eight questions, one at a time, user answers pass back to the builder. Do not answer on the user's behalf.
-
Confirm creation.
Created .great-authors/scenes/<id>.md POV: <character name> Turn: <one-line turn from the card> Callbacks: <any earlier scenes this pays off> Sets up: <any later scenes this sets up> Next: run /authors-channel <author> to draft this scene, or /authors-build-scene for the next one.
Notes
- Scene cards are bible metadata, not manuscript. Do not write to chapter files.
- The scene-builder will reference existing characters and places. If the user mentions a character that doesn't exist in
.great-authors/characters/, offer to run/authors-build-characternext (but complete the scene card first). - If the user says "cancel" or "abort," stop the dispatch and confirm no file was written.
Related Skills
sethshoultes/authors-rewrite
documentation
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-orchestrate-novel
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-corpus-critique
data-ai
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-project-init
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 25, 2026