About skill-trace-debugger
A repository skill that checks static trace and evaluation readiness for skills before live behavioral runs. It reports coverage signals for one skill or the full repository without executing evaluations or collecting session logs.
Key features
- 01Check trace readiness for one skill
- 02Summarize readiness across the repository
- 03Check evaluation and validator signals
- 04Identify explicit-invocation coverage gaps
- 05Provide machine-readable reports
Use cases
- 01Review a skill before behavioral evaluation
- 02Find trace coverage gaps across skills
- 03Check for missing readiness signals
- 04Generate a repository-wide readiness report
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ wyattowalsh/ agents --skill skill-trace-debuggerAfter installing, type/skill-trace-debuggerin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
evals/evals.jsonscripts/check.pytrace_report.pyscripts/asset_toolkit/validate_hooks.pyDetails
From the project READMESkill Trace Debugger
Surface trace and eval coverage gaps for repository skills before live behavioral runs.
Scope: Static trace readiness checks only. Does not execute live evals or harvest session logs.
Dispatch
| $ARGUMENTS | Action |
|---|---|
<name> | Trace readiness report for one skill |
repo / --all | Fleet trace readiness summary |
--format json | Machine-readable report |
| Empty | Show trace signal checklist |
Trace Readiness Checklist
| Signal | Meaning |
|---|---|
evals/evals.json | Behavioral cases exist for post-hoc grading |
scripts/check.py | Portable validator contract is wired |
| explicit-invocation case | Eval includes a slash-command or named dispatch prompt |
| NOT-for boundary | Description names the correct alternate skill |
Workflow
uv run python skills/skill-trace-debugger/scripts/trace_report.py <name>
uv run python skills/skill-trace-debugger/scripts/trace_report.py --all --format json
Route live trace grading to agent-eval-runner or maintainer CI workflows.
Validation Contract
uv run python skills/skill-trace-debugger/scripts/check.py
Critical Rules
- Never claim live trace capture from static reports alone.
- Treat missing explicit-invocation eval cases as a coverage gap, not a hard failure for internal skills.
- Do not mutate eval manifests without maintainer approval.
- Pair trace reports with skill-eval-scaffolder when adding new cases.
- Keep prompts grounded in each skill's dispatch table.
Comments
Markdown supported