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. Do NOT use for deploying to Vercel, Netlify, or Cloudflare (use their respective skills).

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

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

The skill provides excellent actionability and workflow clarity with well-sequenced steps, concrete commands, and validation checkpoints throughout both deployment methods. However, it is significantly too verbose—repeating instructions, over-explaining concepts Claude already knows, and inlining content (MCP setup, security guidelines, conversion tables) that belongs in reference files. Trimming the main file by 40-50% and moving setup/security content to references would dramatically improve token efficiency.

Suggestions

Move the entire 'Security Requirements for API Keys and Secrets' section to a reference file (e.g., references/security.md) and replace with a one-line reference—Claude already knows not to expose secrets.

Move MCP setup instructions (Cursor, Claude Code, Other Tools) to a reference file (e.g., references/mcp-setup.md) since these are detailed setup guides that don't need to be in the main skill.

Eliminate repeated instructions that appear 3+ times (e.g., 'stop and ask the user to create/push a remote', 'MCP cannot create image-backed services') by stating them once in a constraints section.

Remove the SSH-to-HTTPS conversion table and 'When to Use This Skill' section—Claude can infer SSH conversion patterns and the YAML frontmatter already covers activation triggers.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines. It over-explains concepts Claude already knows (what Git remotes are, what service types mean, SSH-to-HTTPS conversion patterns), repeats instructions across sections (e.g., 'stop and ask the user to create/push a remote' appears 3+ times), and includes extensive MCP setup instructions that could be in a reference file. The security section alone is ~30 lines of guidance Claude inherently understands.	1 / 3
Actionability	The skill provides concrete, executable commands throughout (git commands, CLI commands, MCP function calls, render.yaml examples with valid YAML). The Blueprint example is copy-paste ready, deeplink construction is explicit with examples, and verification steps include specific MCP calls with parameter names.	3 / 3
Workflow Clarity	The multi-step workflows are clearly sequenced (Steps 1-7 for Blueprint, Steps 1-4 for Direct Creation) with explicit validation checkpoints (Step 2.5 validation, Step 3 validate configuration, Step 7 verify deployment). There are feedback loops for error recovery (fix validation errors before proceeding, triage guide for failures) and clear decision heuristics for method selection.	3 / 3
Progressive Disclosure	The skill references multiple external files (references/codebase-analysis.md, references/blueprint-spec.md, references/direct-creation.md, etc.) which is good structure, but the main SKILL.md itself contains too much inline content that should be in reference files (MCP setup instructions for Cursor/Claude Code, security requirements section, SSH-to-HTTPS conversion table). The balance between overview and detail is off—the main file tries to be both overview and detailed guide. Bundle files were not provided so we cannot verify reference accuracy.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger terms users would say, explicitly states both what it does and when to use it, and proactively addresses potential conflicts with similar deployment skills through explicit exclusion clauses.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'analyzing codebases', 'generating render.yaml Blueprints', and 'providing Dashboard deeplinks'. These are precise, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (analyzing codebases, generating render.yaml Blueprints, providing Dashboard deeplinks) and 'when' (explicit 'Use when' clause with trigger terms). Also includes a 'Do NOT use' clause for disambiguation.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'deploy', 'host', 'publish', 'set up', 'Render', 'cloud platform', 'render.yaml', 'Blueprints'. Users would naturally use these words when wanting to deploy to Render.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with explicit negative triggers ('Do NOT use for deploying to Vercel, Netlify, or Cloudflare') and platform-specific terms like 'Render', 'render.yaml', and 'Dashboard deeplinks' that clearly distinguish it from other deployment skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (531 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: tech-leads-club/agent-skills
Commit: 5f9b25d

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.