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).
80
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(cloud)/netlify-deploy/SKILL.mdQuality
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 the tool (Netlify CLI), lists specific actions (deploy, host, publish, link, preview/production deploys), provides explicit trigger guidance via a 'Use when' clause, and proactively reduces conflict risk with a 'Do NOT use' exclusion for competing platforms. It uses proper third-person voice and is concise without being vague.
| 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 for disambiguation. | 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 Netlify deployment. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — explicitly scoped to Netlify and explicitly excludes Vercel, Cloudflare, and Render with a 'Do NOT use' clause, making conflict with other deployment skills very unlikely. | 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 solid, actionable deployment guidance with executable commands and clear decision trees, but suffers significantly from verbosity. It explains concepts Claude already knows (OAuth, environment variables, package managers), duplicates content (sandbox escalation mentioned twice, full workflow example repeats the step-by-step), and includes sections that add marginal value (Tips, Environment Variables). Moving detailed reference content to the bundled files and trimming explanatory prose would substantially improve this skill.
Suggestions
Remove redundant sections: the 'Example Full Workflow' duplicates the step-by-step workflow, the sandbox escalation is mentioned in both Prerequisites and Troubleshooting, and the Environment Variables section teaches concepts Claude already knows.
Move the netlify.toml framework defaults table and the detailed error handling/troubleshooting content into the bundled reference files, keeping only a brief mention and link in the main skill.
Integrate validation checkpoints directly into the workflow steps (e.g., after deploy, verify the returned URL is accessible) rather than having a separate 'Report Results' step with no verification.
Trim explanatory prose throughout—remove phrases like 'This skill automates Netlify deployments by:', 'The skill uses the pre-authenticated Netlify CLI approach', and descriptions of what OAuth is or how environment variables work.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose for its purpose. It explains concepts Claude already knows (what OAuth is, what package managers exist, what environment variables are), includes unnecessary sections like 'Tips' and 'Environment Variables' that add little value, and repeats the sandbox escalation guidance in both Prerequisites and Troubleshooting. The 'Example Full Workflow' section largely duplicates the step-by-step workflow above it. | 1 / 3 |
Actionability | The skill provides concrete, executable bash commands throughout every step of the workflow. Commands are copy-paste ready (e.g., `npx netlify status`, `npx netlify deploy --prod`, `npx netlify link --git-remote-url <REMOTE_URL>`) with clear expected output patterns and decision points. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps and decision branches (linked vs not linked, authenticated vs not). However, there are no explicit validation checkpoints after deployment beyond 'Report Results', and the error handling section is separate from the workflow rather than integrated as feedback loops within the steps. | 2 / 3 |
Progressive Disclosure | The skill references bundled files at the bottom (cli-commands.md, deployment-patterns.md, netlify-toml.md) which is good, but the main body contains too much inline content that could be offloaded (e.g., the full netlify.toml framework defaults section, environment variables section, tips). The overview-to-detail ratio is skewed toward too much detail inline. | 2 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.