Canopy debug
Trace any Canopy skill with live phase banners and per-node tree tracing. Respects the current mode — in plan mode no changes are applied; in edit mode the skill executes normally.From its SKILL.md
npx -y skills add kostiantyn-matsebora/canopy --skill canopy-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.1 KB, 608 tokens by cl100k_base, as published. Nobody here has run it
Runtime required. This skill uses Canopy tree notation; canopy-runtime must be active.
Detect canopy-runtime — present if either:
canopy-runtime/SKILL.mdexists under.claude/skills/,.github/skills/, or.agents/skills/, OR- a canopy-runtime marker block exists in
CLAUDE.mdor.github/copilot-instructions.md.If neither is present — install canopy-runtime first (see the
compatibilityfield for the source and install options), then re-invoke this skill.Do not interpret the
## Treewithout canopy-runtime active.
Preamble: parse $ARGUMENTS — first token is target_skill, remainder is skill_args.
Tree
- canopy-debug
- IF << $ARGUMENTS is empty or skill name is missing
- END Usage: /canopy-debug <skill-name> [skill-arguments]
- bind target_skill = first token of $ARGUMENTS
- bind skill_args = remainder of $ARGUMENTS (may be empty)
- detect platform:
.claude/skills/present → claude;.github/skills/present → copilot - IF << platform == "claude"
- Read
../canopy-runtime/SKILL.mdfor the canopy execution engine overview - Read
../canopy-runtime/references/runtime-claude.mdfor Claude Code runtime rules - Read
../canopy-runtime/references/ops.mdfor the primitive-slice index (load specific slices on demand) - Read
../canopy-runtime/references/skill-resources.mdfor category semantics, op lookup chain, tree format, manifest
- Read
- ELSE
- Read
../canopy-runtime/SKILL.mdfor the canopy execution engine overview - Read
../canopy-runtime/references/runtime-copilot.mdfor Copilot runtime rules - Read
../canopy-runtime/references/ops.mdfor the primitive-slice index (load specific slices on demand) - Read
../canopy-runtime/references/skill-resources.mdfor category semantics, op lookup chain, tree format, manifest
- Read
- Read
assets/policies/debug-output.mdfor debug rendering and animation protocol - EMIT_PHASE_BANNER << phase=Initialize | skill=target_skill | args=skill_args
- EXECUTE_WITH_TRACE << target_skill | skill_args
- IF << $ARGUMENTS is empty or skill name is missing
Rules
- Load
assets/policies/debug-output.mdbefore any output — never emit debug output without it - Respect the current Claude Code mode — plan mode means simulate mutations; edit mode means execute normally
- Emit banners and tree-state blocks to the stream as Claude narrates; never buffer and emit at end
Response: target_skill | phases_executed | nodes_executed | final_status
What ships with it: 2 files
13.9 KB alongside SKILL.md
assets/
- policies/debug-output.md7.4 KB
references/
- ops.md6.5 KB
Gives 0 of the 12 instructions most debug triage skills give in 608 tokens
Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06
- Find root cause before attempting any fixin 134 of 1020, across 118 files
- Create a failing test case before implementing a fixin 109 of 1020, across 95 files
- Read error messages and stack traces completelyin 102 of 1020, across 88 files
- Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
- Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
- Trace data flow backward to find the sourcein 84 of 1020, across 70 files
- Form a single hypothesis before testingin 78 of 1020, across 64 files
- Implement only one fix at a timein 76 of 1020, across 63 files
- Question the architecture if three fixes failin 73 of 1020, across 59 files
- Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
- Compare broken code against working examplesin 68 of 1020, across 57 files
- Write a regression test before applying the fixin 62 of 1020, across 55 files
Said here and by no other author read
- Install canopy-runtime if not present
- Read canopy execution engine overview
- Read runtime rules for current platform
- Read primitive-slice index
- Read category semantics and tree format
- Load debug output policy before outputting
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.