token-reducelisted

# Token Reduction Skill ## Description Use targeted retrieval and short summaries when paths are unknown, the repo is large, or the task spans multiple files. Skip exact-path tiny edits. ## Triggers - The user asks to review, explore, search for context, or find where something lives. - The user asks to validate, check, verify, improve, fix, or update a skill, hook, script, or file. - The user's request implies the skill is not being used correctly or needs to work better. - You do not know the exact file path yet. - The task spans several files or areas of the repo. - Broad scans or full-file reads would likely waste context. - When maintaining this skill itself, the same narrow-discovery rules apply. ## First Move - If file location is unknown, start with one standalone discovery command: - `scripts/token-reduce-paths.sh topic words` - `scripts/token-reduce-snippet.sh topic words` - If the exact symbol is already known and `token-savior` is installed, you may use: - `uv run python scripts/token-reduce-structural.py --project-root . find-symbol ExactSymbol` - `uv run python scripts/token-reduce-structural.py --project-root . change-impact ExactSymbol` - Prefer `scripts/token-reduce-paths.sh` for the initial path-only kickoff. - Prefer the structural helper only for exact symbol or dependency questions; do not use it as the default for vague repo discovery. - Use `scripts/token-reduce-snippet.sh` only when the path list is not enough. - Do not treat raw `qmd sea