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).

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured, actionable deployment guide with executable commands, a clear workflow, and properly signaled one-level-deep references. Main weaknesses are redundancy between the Authentication Pattern/Example Full Workflow and the main Workflow section, and a couple of minor validation/organization gaps.

Suggestions

Remove the redundant 'Example Full Workflow' section or fold it into the Workflow as a single copy-paste block, since it restates steps already detailed above.

Merge the 'Authentication Pattern' overview into Workflow Step 1 to eliminate the duplicated auth explanation.

Promote the preview-before-production guidance from a tip into an explicit validation checkpoint within the deploy workflow, since production deploys are effectively irreversible.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but contains redundant sections — the 'Authentication Pattern' duplicates Workflow Step 1 and the 'Example Full Workflow' restates the already-detailed Workflow as commented bash, adding length without new information.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands throughout (npx netlify status/login/link/init/deploy/deploy --prod), with minor gaps such as the placeholder <REMOTE_URL> and the vague 'detect and use appropriate command' for non-npm package managers.

4 / 5

Workflow Clarity

A clear six-step sequenced workflow with auth and link-status checkpoints plus an error-handling section; the preview-before-production validation exists but is relegated to a tip rather than an explicit checkpoint in the sequence.

4 / 5

Progressive Disclosure

Well-organized overview with clearly signaled, one-level-deep bundled references (verified: references/ has no nested links), though the inline 'Handling netlify.toml' framework-defaults detail overlaps content that could live in the netlify-toml.md reference.

4 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

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, third-person description that clearly states capabilities, trigger conditions, and scope boundaries with an explicit exclusion clause. Minor specificity deduction since the listed actions are mostly variants of a single deploy task rather than genuinely distinct operations.

DimensionReasoningScore

Specificity

Names the Netlify domain and several concrete actions ('deploy, host, publish, or link a site/repo', 'preview and production deploys'), but the actions are largely variants of one deployment task rather than fully distinct operations, leaving minor coverage gaps.

4 / 5

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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users would actually say ('deploy, host, publish, or link a site/repo on Netlify', 'preview and production deploys') with appropriate synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear Netlify niche with an explicit negative boundary ('Do NOT use for deploying to Vercel, Cloudflare, or Render'), minimizing conflict with sibling deploy skills.

5 / 5

Total

19

/

20

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.