AI Agent & Automation Workflows

Generates adversarial test cases targeting safe-failure behavior — refusals, hedging, graceful degradation. Use this when you want to stress-test an agent's safety boundaries, check for prompt injection, or build an adversarial eval set. Pairs with agent-eval for scoring: agent-redteam generates cases, agent-eval runs and scores them. Triggers on "red team my agent," "test for jailbreaks," "adversarial cases," "prompt injection testing," or "does my agent refuse correctly.

Build and run an adversarial de-identification ⟷ re-identification evaluation harness for clinical text: generate synthetic clinical notes with ground-truth identifier spans, run a de-id pipeline (defender) over them, and score leakage against an attacker. Use this whenever the task involves evaluating a PHI scrubber or de-id pipeline, measuring re-identification risk, testing HIPAA Safe Harbor coverage or Expert Determination risk, building a privacy-utility frontier for clinical NLP, or comparing de-identification approaches — even if the user only says "test my de-identifier," "how leaky is this scrubber," or "de-id eval." Prefer this over an ad-hoc script whenever synthetic clinical data, PHI, or de-identification evaluation is mentioned.

Reverse-engineers a codebase by reconciling what it claims to do against what it actually does. Runs two independent passes — top-down from docs/README/manifests/API surface, bottom-up from entry points through the actual implementation — then classifies every claim as Confirmed, Drift (was true, isn't anymore), Aspirational (documented but never built), or Silent (implemented but undocumented). The discrepancy list is the deliverable, not either summary alone. Use this when onboarding onto an unfamiliar codebase, auditing whether documentation matches implementation, evaluating a dependency or vendor repo before committing to it, or when a long-lived project's docs and code have drifted apart. Triggers on "reverse engineer this repo," "does the documentation match the code," "audit this codebase," "onboard me onto this project," or "find where the docs and code disagree." Runs standalone — no MCP or wiki setup required. If an obsidian-vault MCP server is connected, offers to compile its output into Sources/raw/ for wiki-operator's /source command to pick up.

Runs the wiki's self-governing maintenance loop and holds it accountable to its own constitution. Orchestrates wiki-librarian (structure), wiki-synthesizer (compilation), and wiki-warehouse (cold-storage integrity, if in use), then adds the things none of them do — a constitution-compliance audit, a tracked wiki health score, and a knowledge-gap queue. Use on a weekly cadence or when the vault hasn't been maintained in a while. Triggers on "govern my wiki," "maintain my wiki," "is my wiki healthy," "wiki health score," "check constitution compliance," "what am I missing in my vault," and the command /govern. Requires the obsidian-vault MCP server connected. Pairs with wiki-librarian, wiki-synthesizer, and wiki-warehouse, which it invokes rather than reimplements.

Maintains the structural health of the wiki. Audits for broken links, orphan pages, stale notes, near-duplicates, and contradictions. Proposes and applies fixes with user confirmation. Run weekly or before a major synthesis session. Triggers on "audit my wiki," "clean up my vault," "check wiki health," "find duplicates," "fix broken links," and the command /audit. Requires the obsidian-vault MCP server connected. Pairs with wiki-operator for on-demand edits and wiki-synthesizer for content compilation.

Operates a Karpathy-style personal knowledge wiki by reading and writing an Obsidian vault directly via MCP — searching before creating, updating existing concept pages over adding new ones, merging duplicates, and keeping all notes linked. Use this skill for any vault operation: processing new learning into wiki notes, improving a concept page, finding connections between ideas, reviewing note quality, generating study prompts, or running maintenance. Triggers on "add this to my wiki," "update my notes on X," "what do I know about Y," "connect these ideas," "clean up my vault," and the commands /learn /update /connect /review /quiz /map /source /clean /health. Requires an Obsidian MCP server connected with read and write tool access.

Compiles raw material into the wiki. Automatically preprocesses unstructured journal entries, then promotes ideas into Knowledge/ concept pages and compiles Sources/raw/ into source pages. Updates Maps/context.md after each run. Use this after learning sessions. Triggers on "synthesize my notes," "compile my wiki," "promote from journal," "process raw sources," and the command /synthesize. Requires the obsidian-vault MCP server connected. Pairs with wiki-operator for on-demand edits and wiki-librarian for maintenance.

Ingests raw research documents (PDFs, ebooks, scans, articles) into a separate private "cold storage" GitHub repo, then writes a lean pointer note into the Obsidian vault — keeping originals and full extracted text out of the vault so it stays fast and git-diffable. Use when the user wants to file, archive, warehouse, or "add a document/paper/PDF to my knowledge base," or to keep large source files outside the vault. Triggers on "warehouse this," "ingest this document," "add this PDF to cold storage," "file this paper," and the commands /ingest and /warehouse-audit. Requires the obsidian-vault MCP server connected and the knowledge-warehouse repo cloned locally. Pairs with wiki-synthesizer (which compiles the resulting Source note into concepts) and wiki-librarian (structural audits).