SKILLEMALL.ai

AC spec-driven-development

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague ide Use when 需要Development领域自动化处理、数据分析和流程编排时使用。不适用于无明确需求的模糊场景。

ClawHub Agent Skills author: 天轰穿 v1.0.1 MIT-0 2 files body ≈ 1 513 tokens Open the sourceclawhub.ai analyzed 33 h ago

Creates specs before coding.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorGitHubSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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

    • note frontmatter-key unknown frontmatter key "slug"
    • note frontmatter-key unknown frontmatter key "displayName"
    • note frontmatter-key unknown frontmatter key "summary"
    • note frontmatter-key unknown frontmatter key "edition"
    • note frontmatter-key unknown frontmatter key "tools"
    • note frontmatter-key unknown frontmatter key "homepage"
    • note frontmatter-key unknown frontmatter key "suggested_price"
    • note frontmatter-key unknown frontmatter key "pricing_tier"
    • note frontmatter-key unknown frontmatter key "pricing_model"

    Process rating: all ten parameters 53/100

    • 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
    • 20When it triggers. No condition that starts the skill
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 28 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1513 tokens
    • 100Running it twice. No mutating operations
    • low 15 top-level sections: this looks like several domains in one skill

    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
    • +2Single-language instructions
    • +3Description length 259: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 28 items
    • +4Has examples (1 code blocks)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    The skill does not show malicious behavior, but it asks for broad command, file, API, and credential-related authority that is not well scoped to writing specifications.
    LLM: suspicious (high) · 14 Aug 2026