CtrlK
BlogDocsLog inGet started
Tessl Logo

render-debug

Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 actionable, well-structured debugging playbook: executable MCP/CLI snippets, a clear seven-step workflow ending in a verification loop, and a clean overview-to-references split. It assumes Claude's competence and avoids concept padding.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — no basic concept explanations, just executable snippets and decision tables; the Quick Reference repetition is justified as a copy-paste index rather than padding.

3 / 3

Actionability

Fully executable MCP calls with concrete parameters (e.g. `list_logs(resource: ["<service-id>"], level: ["error"], limit: 100)`), CLI fallback commands, and an error-to-fix mapping table — copy-paste ready.

3 / 3

Workflow Clarity

Seven-step sequence with an explicit verify step (Step 7: list_deploys → list_logs error → get_metrics) forming a validate-after-fix feedback loop for recoverable debugging operations.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level references (error-patterns.md, metrics-debugging.md, database-debugging.md, quick-workflows.md, etc.), all of which exist as real bundle files; content is appropriately split.

3 / 3

Total

12

/

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.

A strong, well-scoped description: it states concrete capabilities, includes natural trigger terms, and pairs a clear 'what' with an explicit 'when' clause. It is third person, concise, and distinct from sibling Render skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "analyzing logs, metrics, and database state", "Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (debug Render deployments, identify errors, suggest fixes) and when via a clear "Use when..." clause with concrete triggers.

3 / 3

Trigger Term Quality

Natural user-facing terms ("deployments fail", "services won't start", "errors, logs, or debugging") that a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Scoped to Render deployment debugging with distinct triggers, clearly separable from deploy/monitor skills; unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.