SKILLEMALL.ai
GitHub ↗ RU Sign in

AB api-versioning-strategy

Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.

ClawHub Agent Skills author: mohitagw15856 v1.0.0 MIT-0 2 files body ≈ 3 685 tokens Open the sourceclawhub.ai↗ analyzed 16 h ago

Write an API versioning strategy document for a service or API platform.

As a process B 72/100 · Nearly there — weak spots: failures and branches, running it twice

IntegrationWriting and documentstype 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
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
B
72/100
Nearly there
Failures and branches w 10
0
Running it twice w 4
30
When it triggers w 12
50
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 "homepage"
    • note edit-residue the text marks something as outdated (lines 40, 68, 80, 86, 96, 275): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 72/100

    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 13 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 35 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3685 tokens
    • 100Progress reporting. Reports progress
    • low 12 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 362: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 35 items
    • +3Output format is stated explicitly
    • +4Has examples (7 code blocks)

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

    External checks

    ClawHub: clean
    This skill is a document-writing aid for API versioning strategy and does not request unusual access or perform actions outside that purpose.
    LLM: benign (high) · VirusTotal: · 16 Jul 2026