SKILLEMALL.ai
GitHub ↗ RU Sign in

AB netlify-deploy

Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.

foryourhealth111-pixel/Vibe-Skills Agent Skills author: foryourhealth111-pixel Apache-2.0 6 files body ≈ 1 688 tokens Open the sourcegithub.com↗ analyzed 33 h ago

Deploy web projects to Netlify using the Netlify CLI (npx netlify).

As a process B 68/100 · Nearly there — weak spots: result and completion, progress reporting

IntegrationGitHubInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Tools and files w 18
60
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: netlify-deploy (openai/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: 6. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 68/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 47 steps, 3 vague phrases
    • 100Failures and branches. 3 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1688 tokens
    • 100Running it twice. Mutating operations check current state
    • 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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 192: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 47 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

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