CtrlK
BlogDocsLog inGet started
Tessl Logo

netlify-cli-and-deploy

Guide for using the Netlify CLI and deploying sites. Use when installing the CLI, linking sites, deploying (Git-based or manual), managing environment variables, or running local development. Covers netlify dev, netlify deploy, Git vs non-Git workflows, and environment variable management.

96

1.12x
Quality

Does it follow best practices?

Impact

100%

1.12x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A lean, highly actionable CLI/deploy reference with excellent command coverage and organization. Its only weakness is workflow_clarity: production deploys and environment-variable deletion lack explicit validation/verification checkpoints, so the implicit draft→prod gating is the sole safeguard.

Suggestions

Add an explicit verification checkpoint to the deploy workflow, e.g. 'Review the draft preview URL, then run netlify deploy --prod only when the preview is correct.'

Note a verification step for destructive env operations, e.g. run 'netlify env:get VAR' or 'netlify env:list' to confirm values before/after 'netlify env:unset'.

Make the draft→prod gating explicit in the 'Manual / Local Deploys' section rather than leaving it implied by the two command examples.

DimensionReasoningScore

Conciseness

Dense, command-focused content with minimal prose, no over-explanation of concepts Claude already knows (e.g., what Git/CI is), and a summary command table; every section earns its tokens. Not the level below because it avoids the padded explanatory style of the 2-anchor.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands throughout (e.g., "netlify deploy --prod", "netlify env:set API_KEY \"value\" --secret", the vite.config.ts snippet), fully executable rather than descriptive. Not the level below because examples are complete, not pseudocode.

3 / 3

Workflow Clarity

Sequences are present (linking flow checks status first; deploy offers draft preview then --prod), but there are no explicit validation checkpoints for risky operations like production deploys or env:unset — the draft→prod checkpoint is only implicit. Not a 3 because explicit 'validate/verify before prod' steps and error-feedback loops are absent, and the rubric caps destructive-op workflows without validation at 2.

2 / 3

Progressive Disclosure

Well-organized flat sections (Installation, Linking, Deploying, Environment Variables) with a summary 'Useful Commands' table serving as navigation and one clearly-signaled one-level reference to the netlify-frameworks skill; no monolithic wall or nested references. This flat CLI reference does not need splitting into sub-files.

3 / 3

Total

11

/

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, well-constructed description: it names concrete capabilities, uses natural trigger terms, includes an explicit 'Use when' clause, and occupies a clear non-overlapping niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "installing the CLI, linking sites, deploying (Git-based or manual), managing environment variables, or running local development" — plus named commands (netlify dev, netlify deploy), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ("Guide for using the Netlify CLI and deploying sites... Covers netlify dev, netlify deploy...") and when via an explicit "Use when..." trigger clause, matching the top anchor.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — "deploying sites", "Netlify CLI", "environment variables", "netlify dev", "local development" — with good coverage and no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to the Netlify CLI niche with distinct triggers (Netlify CLI, netlify dev/deploy, Git vs non-Git deploys) and third-person voice, making conflict with other skills unlikely.

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
netlify/context-and-tools
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.