plugins-claude/kb-capture/skills/capture/SKILL.md
Capture findings as schema-valid markdown with frontmatter, linting, and optional commit
npx skillsauth add st0nefish/claude-toolkit captureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Capture conversation findings or research as a markdown document with schema-valid frontmatter.
/kb-capture:capture create — force create mode (new document)/kb-capture:capture update <file> — force update mode on the given file/kb-capture:capture (no args) — detect mode from conversation contextbash ${CLAUDE_PLUGIN_ROOT}/scripts/detect-schema.sh
Returns JSON with valid frontmatter field values. Empty fields if no schema found.
Use AskUserQuestion to confirm:
Show the detected schema file (if any) so the user can verify it is correct.
title, date (YYYY-MM-DD). Include constrained fields from schema output.bash ${CLAUDE_PLUGIN_ROOT}/scripts/validate-frontmatter.sh <file>
Fix any issues (exit 1) and re-validate until clean (exit 0).
If rumdl is available, run it with auto-fix:
rumdl check --fix <file>
If the file was modified, re-validate frontmatter. If rumdl is not installed, skip and inform the user.
Use AskUserQuestion — never auto-commit. If approved, stage and commit with a descriptive message.
development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Review, clean up, and open a PR to finalize the work