From critic
Extract ground truth facts from a chapter and compare against world state. Use when the user asks to extract canon, check consistency, or update world-building notes.
npx claudepluginhub jdpedrie/critic --plugin criticThis skill uses the workspace's default tool permissions.
The vault path for all tool calls is: ${user_config.vault_path}
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
The vault path for all tool calls is: ${user_config.vault_path}
Extract factual assertions from a chapter and diff them against the existing world state.
$ARGUMENTS should be a chapter name (e.g., "chapter-01") or a chapter filename.
Call the extract-canon tool with the chapter name.
The tool returns a JSON object with a facts array. Each fact has:
type: character, relationship, location, timeline, ruleentity: the entity nameclaim: what the chapter assertssource_passage: quote from the chaptercanon_status: confirmed, new, or contradictscanon_reference: path to the relevant canon file (if any)conflict_detail: explanation (if contradicts)Group facts by status and present as readable text:
New Facts (not yet in canon): For each, show the entity, claim, and source passage. Note which canon file it should be added to (or suggest creating a new one).
Confirmed (matches existing canon): Brief summary — "X facts confirmed against existing canon."
Contradictions (conflicts with canon): For each, show:
Ask the user how to handle each category:
For accepted updates, help the user write or update the canon files directly. Propose Obsidian-compatible markdown with frontmatter properties that work with Bases:
---
type: character
name: Entity Name
status: active
introduced: chapter-XX
last_updated: chapter-XX
---
Freeform notes about the entity.