CtrlK
BlogDocsLog inGet started
Tessl Logo

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. Do NOT use for deploying to Vercel, Cloudflare, or Render (use their respective skills).

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and well-sequenced with concrete Netlify CLI commands, but it is verbose with redundant sections and inlines detail better suited to the bundled reference files. Validation checkpoints around the actual deploy step are implicit rather than explicit.

Suggestions

Remove the standalone "Example Full Workflow" section and the restated Tips; keep one canonical sequenced workflow to cut duplication and reduce token load.

Push the framework-defaults table, full error-handling catalog, and netlify.toml details into the existing reference files, leaving SKILL.md as a lean overview that links out.

Add an explicit post-deploy validation checkpoint (e.g., verify the returned deploy URL responds or check `netlify status` for the new deploy) before reporting success, turning the deploy step into a validate-then-report feedback loop.

DimensionReasoningScore

Conciseness

The body avoids explaining basics Claude already knows, but is padded with duplication — a full "Example Full Workflow" section re-runs commands already shown step-by-step, and the Tips section restates earlier guidance. It could be tightened considerably.

2 / 3

Actionability

Concrete executable commands appear throughout (npx netlify status, deploy --prod, git remote show origin), but placeholders like <REMOTE_URL> require substitution and npx netlify init is described as guiding the user interactively rather than being fully scripted.

2 / 3

Workflow Clarity

A clear 6-step sequence with expected output patterns and an error-handling section is present, but for a deployment operation the post-deploy validation feedback loop is only implicit (results are reported, not verified), leaving a checkpoint gap.

2 / 3

Progressive Disclosure

A clearly signaled "Bundled References (Load As Needed)" section links three real one-level-deep files (cli-commands.md, deployment-patterns.md, netlify-toml.md), but the body still inlines substantial detail — framework defaults, a full worked example, and error handling — that overlaps with those references rather than staying a lean overview.

2 / 3

Total

8

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that concretely states capabilities, includes natural trigger terms, gives explicit when-to-use guidance, and disambiguates from competing deploy skills. It is concise and free of fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Deploy web projects to Netlify using the Netlify CLI", plus "deploy, host, publish, or link a site/repo" and "preview and production deploys" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Deploy web projects to Netlify using the Netlify CLI") and when ("Use when the user asks to deploy, host, publish, or link a site/repo on Netlify").

3 / 3

Trigger Term Quality

Covers natural terms users would say — "deploy", "host", "publish", "link a site/repo", "Netlify", "preview and production deploys" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Netlify-specific triggers plus an explicit exclusion ("Do NOT use for deploying to Vercel, Cloudflare, or Render") make it clearly distinguishable and unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.