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

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./packages/skills-catalog/skills/(cloud)/netlify-deploy/SKILL.md

Quality

Discovery

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.

This is an excellent skill description that clearly defines what it does (deploy to Netlify via CLI), when to use it (deploy/host/publish/link on Netlify), and when NOT to use it (other hosting platforms). It uses third-person voice, includes natural trigger terms, and has strong boundary-setting to avoid conflicts with similar deployment skills.

Dimension	Reasoning	Score
Specificity	Lists concrete actions: deploy web projects, use Netlify CLI (`npx netlify`), preview and production deploys, link a site/repo. Specifies the tool and multiple deployment modes.	3 / 3
Completeness	Clearly answers both 'what' (deploy web projects to Netlify using Netlify CLI, including preview and production deploys) and 'when' (explicit 'Use when' clause with trigger scenarios). Also includes a 'Do NOT use' clause that further clarifies boundaries.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'deploy', 'host', 'publish', 'link', 'site', 'repo', 'Netlify', 'preview', 'production deploys'. These are terms users would naturally use when requesting deployment to Netlify.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — explicitly names Netlify as the target platform and proactively excludes competing platforms (Vercel, Cloudflare, Render), making it very unlikely to conflict with similar deployment skills.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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

The skill provides comprehensive, actionable deployment guidance with executable commands at every step, but suffers from significant verbosity—explaining concepts Claude already knows (package managers, environment variables, OAuth) and duplicating the workflow in both detailed and summary forms. The workflow is well-sequenced but lacks explicit validation checkpoints after key operations like builds and deploys. Content that belongs in reference files is inlined, inflating the main skill body.

Suggestions

Remove explanations of concepts Claude already knows: what OAuth is, how environment variables work, what different package managers exist, and common framework build defaults. Trust Claude to infer these.

Remove the 'Example Full Workflow' section entirely—it duplicates the detailed numbered steps above and wastes tokens.

Move the 'Handling netlify.toml', 'Environment Variables', and 'Tips' sections into the referenced files (e.g., references/netlify-toml.md or references/deployment-patterns.md) to keep SKILL.md as a lean overview.

Add explicit validation after deployment: e.g., verify the deploy URL is accessible, check `netlify status` shows the new deploy, or review deploy logs for warnings before reporting success.

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. Explains obvious concepts Claude already knows (what OAuth is, what package managers exist, what environment variables are, how to install npm dependencies). The 'Handling netlify.toml' section explains framework defaults Claude would already know. The 'Environment Variables' and 'Tips' sections add little unique value. The authentication section over-explains browser-based OAuth vs API key patterns.	1 / 3
Actionability	Provides fully executable bash commands at every step. Commands are copy-paste ready (e.g., `npx netlify status`, `npx netlify deploy --prod`, `npx netlify link --git-remote-url <REMOTE_URL>`). Error handling section maps specific error messages to concrete resolution commands.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced with a logical flow from authentication through deployment. However, there are no explicit validation checkpoints after deployment (e.g., verifying the deploy URL returns 200, checking build output before deploying). The 'Example Full Workflow' section is redundant with the detailed steps above. Missing a feedback loop for build failures before attempting deploy.	2 / 3
Progressive Disclosure	References to bundled files (cli-commands.md, deployment-patterns.md, netlify-toml.md) are well-structured at the bottom. However, the main body contains too much inline content that could be offloaded—the full authentication pattern, netlify.toml handling, environment variables section, and tips could all be in reference files, keeping the SKILL.md leaner as an overview.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 906a57d

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.