CtrlK
BlogDocsLog inGet started
Tessl Logo

netlify-deployment

Deploy sites, configure serverless and edge functions, and verify builds on Netlify. Use when the user mentions: 'deploy preview', 'configure netlify.toml', or 'debug a failed deploy'. Trigger terms: build error, Netlify Functions, deploy logs, deploy preview

74

Quality

91%

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

100%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.

An exemplary lean skill body: dense with platform-specific hard limits and gotchas Claude would otherwise get wrong, fully executable commands, and a deploy-verify-fix-redeploy loop with an explicit validation checkpoint. Structure is appropriately compact for a simple, single-purpose skill with no bundle files.

DimensionReasoningScore

Conciseness

Every line carries Netlify-specific facts Claude cannot reliably know (10s/26s/15-min function limits, Deno-based edge functions, non-cascading env scopes, NODE_VERSION as top build-failure cause) with zero padding or explanation of known concepts. Matches the lean anchor exactly; the platform limits are current facts rather than time-sensitive version info, so no date penalty applies.

5 / 5

Actionability

Copy-paste-ready commands throughout: 'netlify build --debug', 'netlify env:list', 'netlify status', the curl '%{http_code}' 200-check, and the concrete cron snippet 'config: Config = { schedule: "0 0 * * *" }'. These cover the common cases (local build repro, env scope confirmation, post-deploy verification); the '<DEPLOY_URL>' placeholder is an inherent per-site substitution, not a gap.

5 / 5

Workflow Clarity

A clear sequence with explicit validation and an error-recovery feedback loop: reproduce the build locally 'before pushing', then post-deploy 'verify each critical route returns 200', then 'Any non-200 → read the deploy log in the Netlify UI, fix, redeploy.' This matches the anchor with validation steps and feedback loops; deployment is not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The body is under 50 lines, single-purpose, and organized into clear sections (Hard limits, Gotchas, Commands), with one clearly signaled external reference ('.opencastle/stack/deployment-config.md' for project architecture) and no nested references. Per the simple-skill guideline, this earns the top anchor; no bundle files exist, so nothing further to verify.

5 / 5

Total

20

/

20

Passed

Description

83%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 explicitly states what the skill does and when to use it, with mostly natural trigger terms. Its only weaknesses are a generic 'build error' trigger that risks overlap with non-Netlify build failures and a few missing common failure phrasings.

Suggestions

Add natural failure-synonym trigger terms such as 'deploy failed', 'deployment failed', or 'rollback a deploy' to broaden match coverage without losing precision.

Qualify or drop the generic 'build error' trigger (e.g., 'Netlify build error') to reduce conflict risk with non-Netlify CI skills.

Consider mentioning env-var scoping or build troubleshooting in the action list, since the body devotes substantial space to those capabilities.

DimensionReasoningScore

Specificity

Lists three concrete actions in a named domain — 'Deploy sites, configure serverless and edge functions, and verify builds on Netlify' — matching the anchor for several specific actions with minor gaps. Not 5: coverage omits capabilities the body actually delivers (env-var scoping, build-failure troubleshooting beyond 'verify builds'), so it is comprehensive-but-not-complete.

4 / 5

Completeness

Explicitly answers both: what ('Deploy sites, configure serverless and edge functions, and verify builds on Netlify') and when, via a literal 'Use when the user mentions:' clause with quoted concrete trigger phrases. Clear anchor-5 match; the when-clause requirement is satisfied verbatim.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'deploy preview', 'configure netlify.toml', 'debug a failed deploy', 'build error', 'Netlify Functions', 'deploy logs'. Not 5: common user phrasings like 'deploy failed', 'site is down', or 'rollback' are missing, so it sits between good and comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear Netlify-anchored niche with distinct triggers (netlify.toml, Netlify Functions, deploy preview), but the generic trigger term 'build error' could fire for non-Netlify CI failures — minor overlap risk, matching 'mostly distinct; minor overlap' rather than the clean-niche anchor 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.