update-allowed-tools

Invoking this skill IS the request. If the user message looks empty, that is normal and expected, the task is fully specified here. Never ask what to do. # Overview Analyzes a skill's full content, SKILL.md and any sibling files in the same directory, to find tools it references or requires, then compares against the skill's `allowed-tools` frontmatter to find missing entries. ## Usage ``` /update-allowed-tools <skill name> /update-allowed-tools @path/to/SKILL.md ``` ## Instructions 1. **Parse argument**: The argument is either a file path to a SKILL.md file, or a skill name/description. If no file path is provided, search for the skill using Glob in the current working directory (e.g., `**/skills/**/<name>/SKILL.md`). If there is no argument at all, run `git status` and target the most recently modified skill file in the working tree. 2. **Read the skill file** and separate the YAML frontmatter from the body content. Also read any other files in the same directory (sibling files referenced by or bundled with the skill). 3. **Extract declared allowed-tools**: Parse all entries under `allowed-tools:` in the frontmatter. 4. **Scan all skill content** (SKILL.md body + sibling files) for tool usage. Look for: - Explicit tool names: e.g., `Read`, `Write`, `Edit`, `Bash`, `WebFetch`, `WebSearch`, `Task`, `AskUserQuestion`, `Skill`, etc. - Bash command patterns: e.g., `git diff`, `git commit`, `make`, `npm`, `docker`, `python`, `curl`, etc. - For Bash commands foun...