netlify-frameworks

Guide for deploying web frameworks on Netlify. Use when setting up a framework project (Vite/React, Astro, TanStack Start, Next.js, Nuxt, SvelteKit, Remix) for Netlify deployment, configuring adapters or plugins, or troubleshooting framework-specific Netlify integration. Covers what Netlify needs from each framework and how adapters handle server-side rendering.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

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

The body is concise, actionable, and uses progressive disclosure well with verified one-level-deep references. The main gap is workflow clarity: the build/deploy process is implicit and lacks explicit validation checkpoints for a deployment-oriented skill.

Suggestions

Add a short numbered build/deploy sequence (detect framework → install adapter/plugin → build → verify .netlify/v1/ output → deploy) so the workflow is explicit rather than implied.

Include a validation checkpoint, e.g. confirm the adapter wrote functions/redirects under .netlify/v1/ before deploying, to catch integration failures early.

Mention how to verify a successful deployment (e.g. checking function logs or the deploy summary) so the workflow has a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — terse framing of SSR/adapters, compact tables for framework detection and env-var prefixes, and no padding explaining basic concepts — so every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready guidance: an executable netlify.toml catch-all redirect, a detection table with concrete filenames, and a table of exact client-prefix and access patterns. Inline material is specific and executable, with deeper per-framework steps correctly delegated to references.	3 / 3
Workflow Clarity	Sections are logically grouped (How It Works, Detecting, Reference Guides, General Patterns) but the build-to-deploy flow is described narratively rather than as an explicit sequence, and there are no validation/checkpoint steps — matching the 'sequence present but checkpoints missing or implicit' anchor rather than the level above.	2 / 3
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to real bundled files (references/vite.md, astro.md, tanstack.md, nextjs.md — all present), plus a consolidated 'Bundled References' list, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong across all dimensions: concrete actions, natural trigger terms, explicit what/when guidance, and a distinct Netlify-framework niche. Third-person voice is correctly used throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up a framework project ... for Netlify deployment, configuring adapters or plugins, or troubleshooting framework-specific Netlify integration' — and names specific frameworks, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both: what ('Guide for deploying web frameworks on Netlify') and when (an explicit 'Use when setting up ... configuring ... or troubleshooting ...' clause), satisfying the top anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — framework names (Vite/React, Astro, Next.js, Nuxt, SvelteKit, Remix), 'Netlify deployment', 'adapters or plugins', and 'troubleshooting' — giving good coverage of natural vocabulary.	3 / 3
Distinctiveness Conflict Risk	Narrow niche (Netlify-specific framework deployment) with named frameworks and SSR/adapter triggers makes it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/netlify/skills/netlify-frameworks/SKILL.md
Commit: 11c74d6

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