Name: netlify
Rating: 55.2 (1 reviews)
Author: membranedev

netlify

Netlify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Netlify data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/netlify/SKILL.md

Quality

Content

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

The content is highly actionable with executable Membrane commands and a clear connection workflow, but loses points for some unnecessary explanatory prose and for offering destructive/batch actions without any validation or verification steps. Structure and navigation are solid.

Suggestions

Trim the introductory paragraph defining what Netlify is and soften prose like 'so you can focus on the integration logic rather than auth plumbing' — Claude already grasps auth plumbing.

Add a validation/verification step before destructive actions (delete-site, delete-dns-zone, delete-dns-record), e.g. confirming the target ID or listing before deletion, so the workflow includes a feedback loop.

Consider moving the 20-row Popular actions table to a separate references file and keeping only a few representative examples inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but includes unnecessary prose such as the opening paragraph explaining what Netlify is and lines like 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across install, login, connection ensure/wait, action list/run, and proxy requests, with concrete flags and JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with polling and state-based checkpoints, but the skill exposes destructive actions (delete-site, delete-dns-zone, delete-dns-record) and batch actions (trigger-site-build) with no validation/verification guidance, capping this dimension at 3.	3 / 5
Progressive Disclosure	The SKILL.md is well-organized into clear sections with no nested references and no bundle files; the main gap is the large inline Popular actions table (20 rows) that could optionally live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is third-person, has an explicit 'Use when' trigger, and names the Netlify niche clearly, but its capability list is generic and lacks concrete Netlify-specific actions or synonyms. It sits comfortably above a vague stub but below a comprehensive trigger-rich description.

Suggestions

Replace generic verbs with concrete Netlify capabilities, e.g. 'Deploy sites, manage builds and functions, configure DNS zones and records, and automate Netlify workflows.'

Expand the trigger clause with natural user phrases such as 'deploy', 'site', 'build', or 'DNS' so it matches how users actually ask.

Tighten 'Manage data, records, and automate workflows' — 'data' and 'records' are vague and do not map to clear Netlify objects.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Netlify integration') but its actions — 'Manage data, records, and automate workflows' — are generic and not concrete Netlify capabilities; it does not list specific actions like deploys, sites, or DNS.	2 / 5
Completeness	Both 'what' (Netlify integration; manage data/records/workflows) and 'when' ('Use when the user wants to interact with Netlify data') are present, but the 'when' clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Netlify' and a trigger clause ('Use when the user wants to interact with Netlify data'), but misses common synonyms/variations users might say such as 'deploy', 'site', or 'build'.	3 / 5
Distinctiveness Conflict Risk	The 'Netlify' niche is mostly distinct with low conflict risk, but the generic action verbs ('manage data, records, automate workflows') create minor overlap with general data-integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/netlify/SKILL.md
Commit: f484c82

Reviewed: 5 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.