SKILLEMALL.ai
GitHub ↗ RU Sign in

BC decompose-plan

Forces M2.7 to produce an explicit structured plan before writing code. This makes Tree-of-Thought reasoning explicit instead of implicit, which is how Sonnet's extended thinking mode works. Captures sub-problems, APIs involved with version requirements, risks, and implementation order.

ClawHub Agent Skills author: Stephen Thorn v1.0.0 MIT-0 2 files body ≈ 1 484 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

GeneratorSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "inputs"
  • note frontmatter-key unknown frontmatter key "outputs"

Process rating: all ten parameters 64/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1484 tokens

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 287: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 7 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: suspicious
The skill appears to send the user’s task and retrieved context to an external AI service without clearly telling the user.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026