BB specclaw
Spec-driven development framework for OpenClaw. Propose features, generate specs, spawn coding agents, validate implementations.
As a process B 74/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice
AnalyzerGitHubSoftware developmentAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- 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: 29. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 74/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 20 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4957 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 94 steps
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low The response is described with custom markup (34 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
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 13 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 128: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 94 items
- +4Has examples (32 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
SpecClaw is a real development automation skill, but it gives broad code-changing and command-running authority with weak scoping safeguards.
LLM: suspicious (high) · VirusTotal: · 28 May 2026