sethshoultes/authors-consolidate
skills/authors-consolidate/SKILL.md
Scan journal entries and offer to promote repeated decisions into the permanent bible. Usage - /authors-consolidate. Reads .great-authors/journal/* and identifies decisions that appear in multiple entries; for each, proposes which bible file to promote to (project.md, voice.md, a character file, etc.). Every promotion requires user confirmation. Use periodically - after 5+ sessions - to keep the bible current without losing fidelity to in-flux ideas.
testing
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add sethshoultes/great-authors-plugin authors-consolidateInstall 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:55 PM52.5s1 file scanned
SKILL.md
- name:
- authors-consolidate
- description:
- Scan journal entries and offer to promote repeated decisions into the permanent bible. Usage - /authors-consolidate. Reads .great-authors/journal/* and identifies decisions that appear in multiple entries; for each, proposes which bible file to promote to (project.md, voice.md, a character file, etc.). Every promotion requires user confirmation. Use periodically - after 5+ sessions - to keep the bible current without losing fidelity to in-flux ideas.
/authors-consolidate
Promote recurring journal decisions to the permanent bible.
When to use
- You've been journaling for several sessions and want to move settled decisions out of the journal and into the appropriate bible file.
- Something that started as "tentative" in a journal entry has now survived 3+ sessions — it deserves a permanent home.
Not for: initial bible setup (use /authors-project-init); one-off session capture (use /authors-journal).
Instructions for Claude
When this skill is invoked:
-
Verify
.great-authors/journal/exists and contains at least 3 entries. If fewer than 3, tell the user there's not enough journal history to consolidate yet and stop. -
Read all journal entries in
.great-authors/journal/*.md, sorted by date. -
Extract "Decisions made" bullets across all entries. Group similar decisions (e.g., multiple entries mentioning "Marcus's age is 42" or "shifted opening to present tense"). A "recurring" decision appears in 2+ entries OR is clearly a ratification of an earlier decision.
-
For each recurring decision, propose a promotion:
- Character-related →
.great-authors/characters/<name>.md - Voice/rule related →
.great-authors/voice.md - Timeline related →
.great-authors/timeline.md - Premise/POV/tense related →
.great-authors/project.md - Invented term / brand →
.great-authors/glossary.md
- Character-related →
-
Ask for each promotion individually:
"Promote this decision to
<target-file>?Decision: <one-line summary> Source: appears in <N> journal entries (first: <date>) Target: <file path> Proposed edit: <one-line description of what gets added or changed>
(yes/no/edit first)"
-
If user says yes, apply the edit. If "edit first," let the user revise the proposed edit before applying.
-
After all promotions processed, offer to add a consolidation note at the top of the journal:
"Add a consolidation marker to
<most-recent-journal-entry>showing what was promoted? (yes/no)"If yes, append a section at the top of the most recent entry:
## Consolidated on YYYY-MM-DD - Promoted to characters/marcus.md: Marcus's age (42) - Promoted to voice.md: no interiority in italics - (etc.) -
Final report:
Consolidation complete. Promoted N decisions across M bible files. The journal remains intact — promotions are additive, not destructive.
Notes
- Never delete journal entries. Consolidation is additive.
- If a user flags a proposal as wrong ("that's not settled, it's still in flux"), skip the promotion and move to the next.
- Never promote a decision that appears in only one journal entry unless the user explicitly overrides.
- This skill is a dialog, not a batch job. Expect it to take several minutes.
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