render-deploy

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

85%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 content is highly actionable and well-structured with strong progressive disclosure and clear validated workflows. Its main weakness is conciseness, due to repeated Git-remote guidance and some explanatory padding that assumes less of Claude than necessary.

Suggestions

Consolidate the Git-remote requirement into the single 'Prerequisites Check' section and remove the repeated reminders scattered through the Blueprint and Direct Creation methods.

Trim the inline service-type glossary and SSH-conversion rationale, or move them into the relevant reference files (service-types.md, blueprint-spec.md) to keep the overview lean.

Reduce restated MCP/Docker-image caveats to a single callout near the method-selection heuristic instead of repeating them in multiple sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but the Git-remote requirement is restated roughly six times across sections and some explanatory padding (service-type glossary, SSH conversion rationale) could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready commands and MCP signatures throughout (e.g. 'render blueprints validate', 'render whoami -o json', the SSH-to-HTTPS conversion table, and the deeplink format).	3 / 3
Workflow Clarity	Both methods are clearly sequenced with explicit validation checkpoints and feedback loops — validate then fix-then-revalidate, plus a post-deploy verification and triage section.	3 / 3
Progressive Disclosure	The body acts as an overview pointing to one-level-deep, clearly signaled references (references/*.md, assets/) that all resolve to real files, with detail appropriately split out.	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: it states concrete capabilities, provides natural trigger terms, includes an explicit 'Use when' clause, and occupies a clearly distinct niche. No first/second-person voice or vague fluff is present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks' — using third-person voice, matching the highest anchor.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via an explicit 'Use when the user wants to...' trigger clause.	3 / 3
Trigger Term Quality	Natural user phrasing is well covered with 'deploy, host, publish, or set up their application on Render's cloud platform', terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Render with distinct deploy/host/publish triggers, making conflict with other skills unlikely.	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-deploy/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.