Inspect and improve documentation discovery using trigger-tree's local telemetry. Use for trigger-tree status, live dashboard, heat/cold maps, documentation health, router suggestions, setup, or diagnostics.
Scanned 8/30/2026
Install to Claude Code
npx -y skills add Hedde/trigger_tree --skill trigger-tree --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Trigger Tree?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hedde-trigger-tree)More formats (shields.io, HTML) on the badges page.
---
name: trigger-tree
description: Inspect and improve documentation discovery using trigger-tree's local telemetry. Use for trigger-tree status, live dashboard, heat/cold maps, documentation health, router suggestions, setup, or diagnostics.
---
# trigger-tree for Codex
Invoke this skill as `@trigger-tree <what you want>`, for example
`@trigger-tree watch`, or simply ask in plain language ("show trigger-tree status",
"open the live dashboard"). Both reach the same workflows below.
Let `PLUGIN` be the plugin root: the directory two levels up from this `SKILL.md`.
**Always run the commands below from the user's project directory — never `cd` into
the plugin root** — and keep the `TT_PROJECT_DIR="$PWD"` prefix on every command, so
telemetry, dashboards, and reports bind to the project even though the scripts live
elsewhere. Keep output concise and never print raw telemetry unless requested.
- Status: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-stats.py" --client codex` and summarize current heat, lifetime reads,
untouched paths, and maturity.
- Live dashboard: run `TT_PROJECT_DIR="$PWD" TT_CLIENT=codex "$PLUGIN/scripts/tt-open.sh"`, optionally with `demo` or
`replay`, so the detached dashboard watches this project and loads only Codex-specific tips.
- Insights: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-report.py" --client codex` and link the generated local HTML report. The `agents` block counts persona invocations and lists never-invoked definitions; report it only when `agents.capture` is `on`, treat never-invoked as a review prompt rather than a removal recommendation, and note that Codex subagent capture is unverified rather than implying the counts are complete.
- Instructions: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-instructions.py"` and pass through `--init`, `--selftest`, `--explain ID`, `--json`, `--check`, `--min-rate N`, or `--min-measured N` when requested. Return its output verbatim. Never add or apply proposed probes without explicit user confirmation; unobserved means missing evidence, not a violation.
- Suggestions: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-suggestions.py"` and return its output verbatim.
- Badge: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-stats.py" --client codex --badge` and return the written path.
- Gate: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-gate.py"` and return its output verbatim.
- Tips: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-tips.py" --client codex` and return its output verbatim.
- Note: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-log.py" note "<text>"`.
- Doctor: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-doctor.py"` and return its diagnostics verbatim.
- Setup: ask for `truncate` (recommended; first 200 prompt characters stored locally),
`hash` (no prompt text), or `off` (marker only), then pass the answer explicitly as
`TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-setup.py" --prompt-mode truncate|hash|off`.
- Uninstall: run `TT_PROJECT_DIR="$PWD" python3 "$PLUGIN/scripts/tt-uninstall.py"`; explain that telemetry and ignore
entries remain until the user explicitly deletes them.
Telemetry is collected silently by official Codex lifecycle hooks. Treat heat as decaying
current attention and lifetime reads as durable evidence. Untouched never means obsolete;
only mature datasets may identify guarded dead-path candidates. Exclude retired paths from
current rankings, treat folder routers as routers rather than templates, and keep any insights
summary to at most 15 lines.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!