SKILLEMALL.ai

AB openapi-spec-generator

Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 466 tokens Open the sourcegithub.com analyzed 2 d ago

Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs.

As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
69/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Steps w 15
60
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"

    Process rating: all ten parameters 69/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 60Steps. 49 steps, 4 vague phrases
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Failures and branches. 4 branches
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2466 tokens
    • 100Running it twice. Mutating operations check current state

    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)
    • -5TODO / placeholder text left in the skill
    • +2Single-language instructions
    • +3Description length 138: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 49 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)
    • +1License stated

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