What problem does it solve? SKILL.md files often declare the wrong allowed-tools set — either missing tools that trigger mid-run permission prompts, or declaring overly broad permissions that were never needed. Manually reconciling frontmatter declarations against what a skill actually invokes is tedious and error-prone. ## Core Features & Use Cases - Static audit: Scans a SKILL.md body for tool evidence (named tools, Bash CLI families, MCP references) and diffs it against the declared allowed-tools, classifying each entry as OK, MISSING, or UNUSED. - Session audit: Parses a Claude Code session JSONL transcript via a bundled Python script to report which tools were actually invoked, including per-command Bash breakdowns. - Cross-reference mode: Compares declared, statically detected, and observed tool sets to surface undocumented runtime dependencies and clear removal candidates. - Use Case: After writing a new skill, ask to audit its allowed-tools; the skill recommends a minimal permission set and can patch the frontmatter line directly after your confirmation. ## Quick Start Ask the assistant to audit the allowed-tools declaration for a specific SKILL.md path and apply the recommended fixes.
