render-static-sites

Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.

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 an efficient, actionable configuration reference with proper progressive disclosure into two real reference files. Its only gap is workflow clarity: it reads as a topical reference rather than a sequenced deploy workflow with explicit validation checkpoints.

Suggestions

Add a short numbered deploy/verify sequence (e.g. configure build + publishPath -> add SPA rewrite -> deploy -> verify the preview URL / check for stale content) with an explicit validation checkpoint to lift workflow clarity.

Add a brief troubleshooting/verify subsection for build failures and stale CDN content with a concrete check command or Dashboard path, giving a feedback loop for error recovery.

Consider trimming the inline Common frameworks table now that references/framework-configs.md holds the per-framework detail, or explicitly frame the inline table as a quick-reference summary to avoid perceived duplication.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables for framework configs, static-vs-web-service, and build settings, plus compact YAML blocks — and assumes Claude's competence without explaining basic concepts; every section earns its place, matching the score-3 anchor rather than the padded score-2 anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready config: framework build commands and publish paths, a `routes` rewrite block, a `headers` block, and a complete Blueprint YAML example, matching the score-3 anchor for executable code rather than the pseudocode score-2 anchor.	3 / 3
Workflow Clarity	Content is organized topically (Build and Publish, Routing, Headers, PR Previews) implying a sequence, but there are no explicit validation checkpoints or verify-deploy feedback loops, fitting the score-2 anchor of steps present but checkpoints missing rather than the score-3 anchor with explicit validation.	2 / 3
Progressive Disclosure	Clear overview in SKILL.md with well-signaled one-level-deep references to real bundle files (`references/routing-and-headers.md`, `references/framework-configs.md`), summarized in a References table and linked inline, matching the score-3 anchor for clear overview with one-level references.	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 third-person, highly specific, and answers both what and when with an explicit trigger-terms list. It is among the strongest examples in the rubric and distinctively scopes Render static sites against the related web-service skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Deploys and configures static sites...build commands, publish paths, SPA routing, redirects, custom headers, and PR previews" — matching the score-3 anchor of multiple specific concrete actions rather than the single-domain score-2 anchor.	3 / 3
Completeness	Clearly answers both what ("Deploys and configures static sites on Render's global CDN") and when via an explicit "Use when the user needs to..." clause with multiple triggers, satisfying the score-3 anchor for both what and when; not the score-2 anchor where when is only implied.	3 / 3
Trigger Term Quality	Explicit "Trigger terms:" list covers natural user phrasing — static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll — giving good coverage of terms users would actually say, beyond the partial coverage of score 2.	3 / 3
Distinctiveness Conflict Risk	Scoped to Render static sites with a distinct niche and even disambiguates from a sibling skill ("choose between a static site and a web service"), making conflict unlikely and matching the clear-niche score-3 anchor rather than the overlapping score-2 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/render/skills/render-static-sites/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.