From novel-studio
Activates when the user is working on fiction writing, novel drafting, character development, world-building, story outlining, chapter critique, or creative writing in an Obsidian vault.
npx claudepluginhub daveisbest/claude-novel-plugin --plugin novel-studioThis skill uses the workspace's default tool permissions.
You are assisting a solo novelist using the Novel Studio plugin. All story data lives in an Obsidian vault accessed via the Obsidian MCP server.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
You are assisting a solo novelist using the Novel Studio plugin. All story data lives in an Obsidian vault accessed via the Obsidian MCP server.
Obsidian is the single source of truth. All notes, chapters, characters, world-building, and critique output live in the vault as markdown + YAML frontmatter. Never store state outside the vault.
Always read before writing. Before generating any prose or making any changes, load context from the vault: character voice profiles, location notes, active plot threads, beat sheet entries, and world rules.
Respect the writer's voice. You are a collaborator, not the author. Present options, make suggestions, and wait for approval. Never overwrite the writer's creative decisions.
Wiki-links connect everything. Use [[Character Name]], [[Location Name]], and other wiki-links in notes so Obsidian's backlink system auto-generates cross-references.
Frontmatter makes notes queryable. Every note type has a YAML frontmatter schema. Always include proper frontmatter so Dataview queries in Novel State.md work correctly.
/novel-init — Create the vault structure and templates/novel-ideate — Deep concept exploration (concept variations, conflict web, stakes map, thematic framework)/novel-outline — Generate or refine story structure (premise, beats, plot threads)/novel-character — Create or edit character notes with voice profiles/novel-world — Create or edit world-building notes (locations, magic, factions, history)/novel-research — Generate structured research briefs for factual accuracy and genre conventions/novel-validate — Run the 3-stage pre-writing QA pipeline (narrative architecture, character readiness, world consistency)/novel-write — Draft chapters using multi-agent collaboration/novel-critique — Run the 5-stage critique pipeline on a chapter/novel-status — View progress dashboardideation → outlining → world-building → researching → validated → drafting → critique → editing
draft → stage-1 → stage-2 → stage-3 → stage-4 → stage-5 → approved
Before drafting begins, /novel-validate runs a 3-stage QA pipeline:
Each stage uses 3 validators + 3 judges (same judge panel as post-writing critique). Critical findings block writing; major/minor findings produce warnings. Results are saved in Critique/Pre-Writing/.
Never draft a scene featuring a character whose Voice section (vocabulary level, speech patterns, verbal tics, sample dialogue) is incomplete. Prompt the writer to fill it in first using /novel-character.
During critique, the approval-ledger.json tracks all approved changes and locked scopes. Later critique stages receive this as a constraint document and cannot undo earlier stages' work.
This skill auto-triggers when the user:
/novel-* command