pyrite

This skill should be used when working in the /Users/markr/pyrite repo — fixing a bug, adding a feature, writing or running tests, debugging, completing or filing a backlog item, releasing dev→main, or deploying to demo.pyrite.wiki / capturecascade.org / pyrite.ink. Enforces TDD, root-cause debugging, evidence-before-claims verification, and CLI-driven backlog management.

This skill should be used when the user asks to "create a KB", "build a KB", "populate a KB", "expand a KB", "add entries", "batch create entries", "fill in gaps", "cross-link KBs", "run QA on a KB", or asks to build out a knowledge base from a description or spec. Provides the orchestration workflow for creating, populating, validating, and cross-linking intellectual-biography and movement knowledge bases using pyrite CLI and Claude Code subagents.

Use when verifying claims in a journalism-investigation KB. Evaluates unverified claims, searches for corroborating evidence, updates claim status and confidence, and creates evidence entries linking claims to sources.

Use when mapping relationships between entities in a journalism-investigation KB. Discovers ownership chains, board memberships, funding flows, and other connections. Creates structured connection entries with sources and identifies multi-hop relationships.

Use when conducting web research for an investigation topic. Searches the web, creates well-sourced KB entries with proper source chain tracking, and enforces the source tier system. Every entry created must link to a source.

Use when working with a software-type Pyrite KB for development workflow: pulling work items, checking the board, claiming tasks, submitting for review, or managing backlog. Covers the full kanban cycle via sw_* MCP tools and CLI commands.

Use when the user wants to scaffold a new Pyrite extension from a description. Generates the full directory structure, plugin class, entry types, validators, preset, tests, and installs in dev mode.

Use when investigating a specific entity (person, organization, event) across Pyrite knowledge bases. Enforces source chain tracking, relationship mapping, and confidence-rated findings. Every claim must link to a source.

Use when conducting structured research on a topic across Pyrite knowledge bases. Enforces a Gather-Connect-Analyze-Synthesize methodology with source tracking and confidence assessments.