CD tree
Universal radial-tree exploration engine — loads a preset, grounds a root, expands every node through 12 framing passes, derives each child in 12 evidence-bearing fields, scores it, and recurses on `advances` leaves until substantive convergence (or a user cap). Caps default to ∞; `defer / TODO / NEEDS-MORE-INFO` leaves are hard-banned. Use when the user wants the engine itself — a custom preset via `--preset <path>`, explicit control of a run, or "tree of thoughts" / 穷尽的树状探索 in general; for the four shipped use-cases prefer `/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`, whose descriptions carry the per-use-case triggers.
Promises a universal radial-tree exploration engine: takes a preset, grounds a root, runs 12 framing passes per node, derives children across 12 evidence-bearing fields with scoring, recurses on advancing leaves until convergence. Ships with four presets for brainstorming, attack planning, design, and code audit.
Checks show: grade C, 3478 body tokens, one file. Broken references in docs, code quality 67/100, process logic 36/100. No critical errors but structure needs work. No model runs or sandbox testing. Broad platform support: Claude, Cursor, DeepSeek, and eight others.
Install if you need the raw engine for custom presets and explicit run control. Otherwise stick with the `/cc-tree:*` commands—they're the point.
Universal radial-tree exploration engine — loads a preset, grounds a root, expands every node through 12 framing passes, derives each child in 12…
As a process D 36/100 · Unfinished process — References files that are not bundled: ../../docs/ENGINE.md, ../../docs/ENGINE.md, ../../docs/ENGINE.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/chaining.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/framings.md - warning
missing-refreference to a missing file: ../../docs/presets.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../docs/ENGINE.md - warning
missing-refreference to a missing file: ../../presets/ - warning
missing-refreference to a missing file: ../../commands/ - warning
missing-refreference to a missing file: ../../docs/EVALUATION.md
Process rating: all ten parameters 36/100
- 0Tools and files. 16 referenced file(s) missing: ../../docs/ENGINE.md, ../../docs/ENGINE.md, ../../docs/ENGINE.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 38 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3478 tokens
- low The response is described with custom markup (16 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 666: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.