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.

68

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

65%

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

The body is actionable with concrete executable commands and a clearly sequenced workflow, but it is verbose (duplicate workflow sections, redundant explanations) and under-uses its own reference files, keeping too much detail inline. Conciseness and progressive disclosure are the weakest dimensions.

Suggestions

Remove the redundant "Example Full Workflow" section and trim the "Overview" list, which restates steps already detailed in the Workflow section.

Move the inline "Handling netlify.toml" detail and CLI command listings into the existing reference files, replacing inline content with well-signaled links like the other References entries.

Add an explicit post-deploy verification checkpoint (e.g., confirming the deploy URL responds or checking `netlify status`/deploy success) to close the validation gap in the deploy step.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands, but padded with redundant content — an "Overview" that restates the workflow and a duplicated "Example Full Workflow" section — plus unnecessary explanations of concepts Claude knows (OAuth, what netlify.toml does).

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands throughout (`npx netlify status`, `npx netlify deploy --prod`, `git remote show origin`), with only justified placeholders like `<REMOTE_URL>`.

3 / 3

Workflow Clarity

The six-step sequence is clear and the auth step has explicit validation (expected output patterns, re-verify after login), but the deploy step reports results without an explicit deploy-success verification checkpoint for a risky operation.

2 / 3

Progressive Disclosure

Three real one-level-deep reference files exist and are linked, but the body is a largely monolithic ~236 lines with CLI-command and netlify.toml detail kept inline, and the "References" section is only a thin, weakly-signaled list at the very end.

2 / 3

Total

9

/

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, concise description that names concrete actions, natural trigger terms, and an explicit "Use when" clause tied to a distinct platform niche. It satisfies all four dimensions at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Deploy web projects to Netlify", "link a site/repo", and distinguishes "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"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Uses natural verbs users would say — "deploy, host, publish, or link a site/repo on Netlify" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

"Netlify" is a specific platform with distinct triggers, giving it a clear niche unlikely to conflict with other skills.

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.