dstoic

Comprehensive challenge agent — runs ALL 9 debiasing patterns (anchor + verify + framing) in fresh context (no parent reasoning bias). Returns structured challenge report with explicit technique rationale.

Summarize large files (>25K tokens) using chunked reading for context baseline creation

Detect and anonymize PII (SSN, cards, emails, phones, names) and business data (companies, revenue, costs, pricing). Use when handling sensitive files or user requests anonymization. Check-only or full anonymization with 5 strategies (mask/hash/pseudo/token/mixed). GDPR/HIPAA aware.

Run a task in the background. Use when user wants to start a long-running task without blocking, run agent tasks or shell commands asynchronously. Triggers include "background", "run in background", "async", "non-blocking".

Divergent-convergent brainstorming with research, ideation, and trade-off analysis. Use when exploring options, generating ideas, comparing approaches. Triggers include "brainstorm", "explore options", "ideate", "compare approaches".

Challenge, push back, play devil's advocate on AI output. Use when: challenge this, are you sure, push back, prove it, what if you're wrong, devil's advocate, stress test, poke holes, second opinion, sanity check, too confident, really?, question this decision. Subcommands: anchor (committed too fast), verify (facts wrong?), framing (wrong problem?), deep (full devil's advocate in separate context).

Streamlined git commit for praxis-managed repos. Single human gate for scope + message approval. Use when committing changes, "commit repo", "commit praxis", "commit nano-vc".

Convert Word (.docx) files to clean markdown for LLM context (uses markitdown). Use when converting Word documents to markdown for analysis or summarization. Triggers include "convert docx", "word to markdown", "docx file".

Convert EPUB files to clean markdown for LLM context (uses epub-to-markdown). Use when converting ebooks or EPUB documents to markdown for analysis or summarization. Triggers include "convert epub", "epub to markdown", "epub file".

Convert Markdown files with Mermaid diagrams to styled PDF. Use when user wants to export/convert markdown to PDF, generate PDF documentation, or create printable documents.

Convert PDF files to LLM-ready formats using Docling (markdown/DocTags/JSON). Use when converting PDFs to markdown for analysis or summarization. Triggers include "convert pdf", "pdf to markdown", "pdf file", "docling".

Convert PowerPoint (.pptx) files to clean markdown for LLM context (uses markitdown). Use when converting presentations to markdown for analysis or summarization. Triggers include "convert pptx", "powerpoint to markdown", "pptx file", "slides to markdown".

Create baseline context from .in/ folder with manifest-driven organization (run once per project). Use when bootstrapping project context, setting up .ctx/ snapshot. Triggers include "create context", "bootstrap context", "setup context", "init context".

Deploy static sites to Surge.sh with inventory tracking. Use when deploying, tearing down, or listing surge deployments. Triggers include "deploy to surge", "surge deploy", "teardown surge", "list deployments".

Toggle automatic dumping of Claude's output to timestamped markdown files

Creates, updates, or optimizes CLAUDE.md files following Anthropic best practices. Use when user requests creating, updating, improving, or optimizing CLAUDE.md files for project context, coding standards, or persistent memory.

Automates agent-skills plugin version bumps and release metadata. Use when: adding/removing/updating skills or commands, bumping plugin version, preparing a release. Triggers: bump version, edit plugin, update plugin, release, version bump, new skill added, new command added.

Create or audit RISEN prompts with structure validation. Use when creating structured prompts from notes, auditing existing RISEN prompts, or improving prompt quality. Triggers include "risen prompt", "edit risen", "create risen", "audit risen", "structure prompt".

Creates, modifies, and orchestrates Claude Code tools (skills, agents, scripts). Use when user requests creating, updating, improving, or editing any Claude Code extension — skills, sub-agents, slash commands, script wrappers. Triggers include "create/make/new skill/command/agent/script", "tool for X", "slash command", "sub-agent", file paths with /skills/, /agents/. For plugin version bumps and release metadata, route directly to edit-plugin.

Chaotic domain: act to impose minimal constraints when cause-effect is invisible. Use when: production down with gibberish logs, completely novel problem, crisis, deliberate disruption, nothing makes sense. NOT for problems with any visible pattern — use /probe instead.

Sense-making before action. Classify problem using Cynefin to route to the right skill chain. Use when: frame, what approach, how should I start, which skill, where to begin, unsure what to do. NOT for known tasks — just do them.

Import Google Docs from Drive into local google-in/ folder with manifest tracking. Use when importing Google documents for local analysis. Triggers include "import gdoc", "google doc", "import from drive", "google docs import".

Convert markdown documents into AntV infographic SVGs. Analyzes content structure, selects optimal template, generates AntV syntax, and renders to SVG. Use when user wants to create infographics, visual summaries, or storytelling visuals from markdown.

Install dependencies with monorepo awareness. Use when: user asks to install a package, add a dependency, or setup Python/JS packages. Triggers: "install X", "add package", "setup dependency", "I need lodash", "install docling".

Deep proactive analysis for complex technical problems requiring upfront thinking and design. Use when: investigate, deep dive, technical spike, design strategy, complex multi-constraint problem, figure out how to, how should I approach. NOT for errors (use troubleshoot) or option brainstorming (use brainstorm).

List all CONTEXT files across code/, projects/, repos/, and vaults/ with status and metadata. Use when viewing context registry, checking saved sessions, or syncing INDEX.md. Triggers include "list contexts", "show contexts", "context registry", "sync index".

On-demand code annotator for LLM context preservation. Adds section-level comments capturing intent, rationale, and gotchas. Use when "literatize", "add literate comments", "annotate this file", "add section comments".

Resume session from CONTEXT-llm.md. Use when resuming work, loading saved context, continuing a previous session. Triggers include "load context", "resume session", "continue where I left off".

Create OpenSpec design artifacts. Use when: user wants to design a feature before tasking, run a bounded context check, produce design.md, or create C4/ER/flow diagrams for an OpenSpec change. Triggers: design, openspec-design, BC check, bounded context, design.md.

Implement OpenSpec change proposals. Use when: implementing approved changes, working through task lists, or checking implementation progress.

Initialize OpenSpec in a project. Use when: user says 'init openspec', 'setup openspec', or asks to add OpenSpec to a project.

Create OpenSpec change proposals. Use when: user wants to plan a feature, create a proposal, or start a new OpenSpec change.

Pre-gate self-check for drift detection and philosophy alignment. Use when: preparing for human gate review, checking implementation quality, or detecting scope drift.

Adaptive refinement for blocked or drifted changes. Use when: implementation is blocked, scope drifts >20%, or direction needs to change.

Pre-implementation tech lead review gate for OpenSpec changes. Reviews proposal+design+tasks+tests as a whole. Use when: review change, openspec review, tech lead review, architecture review, ready to implement?, pre-implementation check, review before developing.

Update docs and context for OpenSpec changes. Use when: saving session state, refreshing docs after implementation, or syncing change status.

Generic test executor for OpenSpec changes. Use when: running checkpoint verification at gates, executing test.md strategies.

Recommend optimal Claude model (haiku/sonnet/opus) for a task. Use when user asks "which model", "pick model", "model for", or before starting costly/complex tasks. Covers tech and non-tech tasks.

Pin session decisions, questions, objections, scope constraints, and corrections to a persistent board that survives context compaction. Use PROACTIVELY when: (1) user approves/rejects a recommendation, (2) user asks a clarifying question about a proposal, (3) user states a scope constraint, (4) user corrects a misunderstanding. Also use when user says "pin", "track this", "mark as approved", "board", "show pins". This skill should be auto-invoked by the model without user asking — whenever a decision, question, or constraint is detected in conversation, pin it immediately after responding.

Safe-to-fail experiment for Complex domain problems where cause-effect is only visible in retrospect. Two-phase: foreground qualify → background probe → sense result. Use when: probe, safe-to-fail, test hypothesis, experiment with hypothesis, Complex domain with hypothesis. NOT for brainstorming (use brainstorm) or known cause-effect (use investigate).

Analyze collaboration patterns (HOW) and compute metrics from captured sessions. Use when reviewing collaboration quality, analyzing human-AI interaction, computing session metrics. Triggers include "retrospect collab", "collaboration analysis", "session patterns", "how am I collaborating".

Analyze domain insights (WHAT/WHY learned) from captured sessions. Use when reviewing learnings, extracting patterns, analyzing decisions. Triggers include "retrospect domain", "domain analysis", "what did I learn", "session insights".

Generate aggregate reports with trends and visualizations across sessions. Use when reviewing activity patterns, generating retrospective summaries. Triggers include "retrospect report", "aggregate report", "activity summary", "session trends".

Save session to CONTEXT-llm.md with conversation summary. Use when saving work, checkpointing progress, preserving session state. Triggers include "save context", "save session", "checkpoint", "save my progress".

Session scratch pad for parking side-thoughts during deep work without losing flow. Use when user says "scratch", "note this", "park this", "jot this down", "remember for later", or wants to capture a quick thought mid-task. Always use this skill for any /scratch command — even for simple captures — because it manages numbered storage and stable IDs.

Discover and evaluate Claude Code skills from curated sources. Use when searching for existing skills, finding skill inspiration, or before creating a new skill. Triggers include "search skill", "find skill", "skill for X", "what skills exist for", "discover skills".

Scaffold and run behavioral tests for skills. Triggers: test my-skill, add test for X, run skill test, test-skill. Generates pytest file from template + runs in Docker.

Concise recap of the previous response. Use when user wants a quick summary of what just happened. Triggers include "tldr", "recap", "summarize last response", "what just happened".

Toshl Finance automation - sync data to local cache and generate monthly financial reports

Use when user reports an error, bug, or something not working. Search-first troubleshooting with diagnostic phase. Triggers: debug, error, broken, not working, failing, crash, exception.

20 hooks across 10 events