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).
87
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 clearly defines specific capabilities, includes strong natural trigger terms, explicitly addresses both what and when, and proactively prevents conflicts with similar deployment skills. The negative trigger clause is a particularly effective technique for disambiguation in a multi-skill environment.
| 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 multiple trigger scenarios, plus 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'. Also includes negative triggers distinguishing from Vercel, Netlify, and Cloudflare, which helps with routing accuracy. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit negative boundaries ('Do NOT use for deploying to Vercel, Netlify, or Cloudflare') and Render-specific terminology like 'render.yaml Blueprints' and 'Dashboard deeplinks'. Very unlikely to conflict with other deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability, workflow clarity, and progressive disclosure—it provides executable commands, well-sequenced steps with validation checkpoints, and appropriate delegation to reference files. However, it is significantly too verbose: security requirements, MCP setup instructions for multiple tools, repeated guidance about Git remotes, and extensive prerequisite checks bloat the token budget substantially. Much of this content could be condensed or moved to reference files.
Suggestions
Move the 'Security Requirements for API Keys and Secrets' section to a reference file and replace with a 2-line summary (e.g., 'Never expose API keys in chat. Guide users to env vars. Details: references/security.md').
Move MCP setup instructions (Cursor, Claude Code, Other Tools) to a reference file—these are lengthy tool-specific guides that don't need to be in the main skill body.
Consolidate repeated instructions (e.g., 'stop and ask user to create/push a Git remote' appears 3+ times) into a single early gate check, then reference it.
Remove the 'When to Use This Skill' section entirely—this duplicates the YAML frontmatter description and is information Claude can infer from context.
| 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), repeats instructions across sections (e.g., 'stop and ask the user to create/push a remote' appears 3+ times), includes lengthy MCP setup instructions for multiple tools, and has extensive security guidance that could be condensed significantly. The prerequisite checks alone span dozens of lines with redundant verification steps. | 1 / 3 |
Actionability | The skill provides concrete, executable commands throughout—bash commands for CLI operations, specific MCP function calls, complete YAML examples for render.yaml, exact deeplink URL formats with conversion tables, and JSON configuration blocks for MCP setup. Nearly everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | Both deployment methods have clearly numbered, sequenced steps with explicit validation checkpoints (Step 2.5 immediate checklist, Step 3 validate configuration, Step 7 verify deployment). The post-deploy triage section includes a feedback loop for fixing and redeploying. Decision heuristics for method selection are clearly structured with conditions. | 3 / 3 |
Progressive Disclosure | The skill effectively delegates detailed content to reference files (references/codebase-analysis.md, references/blueprint-spec.md, references/direct-creation.md, references/troubleshooting-basics.md, etc.) while keeping the main file as an orchestration overview. References are one level deep and clearly signaled with descriptive labels. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
906a57d
- Reviewed
Table of Contents
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.