Skip to content
Skills Library
AI & agents · Analysis

trigger-tree

/trigger-tree

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.

Author
hedde ↗
Licence
MIT
Last repository change
24.10.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

SKILL.md has no level-two headings · 37 lines, 418 words

SKILL.md preview
---
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.

Versions

The database has no other skills named trigger-tree.

Database snapshot: 13.11.2026 · package version 346a15afb9d6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 80rb:discovery-report
    Drafting an internal report from skill-discovery telemetry collected when RUBY_PLUGIN_DISCOVERY_LOG=1 is set. Reads ${CLAUDE_PLUGIN_DATA}/discovery.jsonl, summarizes hook events that matched trigger patterns, lists candidate-skill suggestions, computes per-rule match rate,…
  • 100deep-status
    Current deep-work session status — dashboard, badge, tree, or routing to the receipts / history / report / assumptions sub-pages. Triggers on `/deep-status`, \"session status\", \"deep-work status\", \"세션 상태\", \"세션 현황\", \"상태 확인\". Flags: `--compare`, `--receipts`, `--history`,…
  • 90reasoning
    This skill should be used when the user asks to "reason through", "think step by step", "analyze systematically", "debug with hypotheses", "root cause analysis", "chain of thought", "tree of thought", "documentation lookup", or needs structured reasoning frameworks with…
  • 100fa-foundation-optimize-directory-tree
    Provides the whole-tree bootstrap that puts the Gaia context layer onto an existing directory tree — an instruction file and MEMORY.md topic store at every scope that earns one, a root registry, and the retrospective design documentation its projects never had — and re-validates…
  • 100tree-sitter-language-pack-using-the-mcp-server
    Use when parsing source, extracting code structure, or detecting a language through the tree-sitter-language-pack MCP server's tools, rather than shelling out to the ts-pack CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.