SKILLEMALL.ai

AF solo-plan

Explore codebase and create spec + phased implementation plan with file-level task breakdown. Use when user says "plan this feature", "create implementation plan", "write a spec", "battle plan", or describes a feature/bug/refactor. Zero questions — researches code instead. Do NOT use for idea validation (use /validate) or execution (use /build).

ClawHub Agent Skills author: Rust v2.2.1 2 files body ≈ 2 825 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 55/100 · Will not run — References files that are not bundled: spec.md

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
91
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: spec.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Grep Bash Glob Write Edit AskUserQuestion mcp__solograph__session_search mcp__solograph__project_code_search mcp__solograph__codegraph_query mcp__solograph__codegraph_explain mcp__

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: spec.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: spec.md
  • 0Tools and files. 1 referenced file(s) missing: spec.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 14 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 54 steps
  • 100Failures and branches. 7 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2825 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

  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 347: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 54 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This is a coherent planning skill, but it can automatically search past chats, other projects, and external sources before the user has clearly approved that scope.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026