agentleFS
Sign inStart free
kostiantyn-matseborakostiantyn-matsebora/canopy-examples/.agents/skills/canopy-debug/SKILL.md

canopy-debug

Skill0 starsChanged 6 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    IF << $ARGUMENTS is empty or skill name is missing

    line 34
  2. Very specific:

    Read ../canopy-runtime/SKILL.md for the canopy execution engine overview

    line 40
  3. Very specific:

    Read ../canopy-runtime/references/runtime-claude.md for Claude Code runtime rules

    line 41
  4. Very specific:

    Read ../canopy-runtime/references/ops.md for the primitive-slice index (load specific slices on demand)

    line 42
  5. Very specific:

    Read ../canopy-runtime/references/skill-resources.md for category semantics, op lookup chain, tree format, manifest

    line 43
  6. Very specific:

    Read ../canopy-runtime/references/runtime-copilot.md for Copilot runtime rules

    line 46
  7. Very specific:

    Read assets/policies/debug-output.md for debug rendering and animation protocol

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Runtime required. This skill uses Canopy tree notation; canopy-runtime must be active.

Detect canopy-runtime — present if either:

  • canopy-runtime/SKILL.md exists under .claude/skills/, .github/skills/, or .agents/skills/, OR
  • a canopy-runtime marker block exists in CLAUDE.md or .github/copilot-instructions.md.

If neither is present — install canopy-runtime first (see the compatibility field for the source and install options), then re-invoke this skill.

Do not interpret the ## Tree without 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.md for the canopy execution engine overview
      • Read ../canopy-runtime/references/runtime-claude.md for Claude Code runtime rules
      • Read ../canopy-runtime/references/ops.md for the primitive-slice index (load specific slices on demand)
      • Read ../canopy-runtime/references/skill-resources.md for category semantics, op lookup chain, tree format, manifest
    • ELSE
      • Read ../canopy-runtime/SKILL.md for the canopy execution engine overview
      • Read ../canopy-runtime/references/runtime-copilot.md for Copilot runtime rules
      • Read ../canopy-runtime/references/ops.md for the primitive-slice index (load specific slices on demand)
      • Read ../canopy-runtime/references/skill-resources.md for category semantics, op lookup chain, tree format, manifest
    • Read assets/policies/debug-output.md for debug rendering and animation protocol
    • EMIT_PHASE_BANNER << phase=Initialize | skill=target_skill | args=skill_args
    • EXECUTE_WITH_TRACE << target_skill | skill_args

Rules

  • Load assets/policies/debug-output.md before 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free