CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

render-automation

Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/render-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a well-structured, tool-centric reference that is highly actionable for a runtime-schema-driven MCP workflow, with explicit setup validation and status-polling checkpoints. Its main weaknesses are redundant pitfall repetition across sections and workflows that mention failure modes without folding them into recovery loops.

Suggestions

Consolidate the repeated 'srv-'/'dep-' prefix and cursor-pagination notes into the single 'Known Pitfalls' section to reduce duplication.

Fold failure handling into the deploy-and-monitor workflow as an explicit recovery step (e.g., on 'build_failed', inspect the deploy log and optionally retry with clearCache: true).

Consider moving per-tool parameter tables into a references/ file to slim SKILL.md toward an overview plus Quick Reference.

DimensionReasoningScore

Conciseness

The body mostly delivers API-specific facts Claude would not know (ID formats, enum values, poll intervals) with no padding about known concepts, but there is noticeable repetition: 'srv-'/'dep-' prefixes appear in three places, cursor pagination is explained in sections 1, 4, and 'Known Pitfalls', and async-deploy/polling guidance is duplicated. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the more severe anchor 2.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool names ('RENDER_LIST_SERVICES', 'RENDER_TRIGGER_DEPLOY'), required parameters, ID formats, status enums, and poll intervals. It is not fully copy-paste ready (no example request payloads), but omitting hardcoded schemas is explicitly justified by 'Always call RUBE_SEARCH_TOOLS first to get current tool schemas', placing it at anchor 4 with only minor gaps.

4 / 5

Workflow Clarity

Each workflow has a 'When to use' line, a numbered tool sequence with prerequisite markers, and there are explicit checkpoints: 'Confirm connection status shows ACTIVE before running any workflows' and the poll-until-terminal-state loop with success/error status enums. It falls short of anchor 5 because error-recovery handling (what to do on 'build_failed', handling queued concurrent deploys) is mentioned as a pitfall rather than wired into the workflow as a retry/fix loop.

4 / 5

Progressive Disclosure

A single-file skill with no bundle directories (references/, scripts/, assets/ are absent), so everything is appropriately inline and external detail is delegated to the composio.dev toolkit link and RUBE_SEARCH_TOOLS at runtime. Sections are well-organized (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference table), matching anchor 4. Not 5 because the ~180-line body of per-tool parameter and pitfall detail is monolithic by design and a reference file could offload it, though the structure keeps it navigable.

4 / 5

Total

15

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 terse, domain-specific description that clearly identifies what it does and through which mechanism, but it lacks a 'Use when' trigger clause and states no concrete operations beyond generic 'Automate'. Adding explicit triggers and one or two named actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Render, deploying or redeploying services, or checking deployment status.'

Replace generic 'Automate Render tasks' with concrete actions such as 'List and filter Render services, trigger and monitor deployments, manage projects.'

Include natural synonyms like 'redeploy', 'deploy status', and 'Render cloud' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Render tasks via Rube MCP (Composio)') and enumerates object categories ('services, deployments, projects'), but the only action verb is the generic 'Automate' — no concrete operations like 'list services' or 'trigger deployments' are stated. It sits between anchor 3 (domain plus 1-2 concrete actions) and anchor 4 (several specific actions), closer to 3 because the nouns listed are objects, not actions.

3 / 5

Completeness

The 'what' is clear (automating Render services, deployments, projects via Rube MCP), but there is no 'Use when...' clause or equivalent trigger guidance — 'Always search tools first for current schemas' is an operating instruction, not a usage trigger. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords users would say are present: 'Render', 'services', 'deployments', 'projects'. It misses common variations and synonyms such as 'redeploy', 'deploy status', 'build logs', or 'Render cloud'. Not score 5 (comprehensive synonym coverage absent); not 3 since core natural terms are all covered rather than only partially.

4 / 5

Distinctiveness Conflict Risk

The Render cloud platform niche is distinct and the description anchors it to Rube MCP/Composio. Minor overlap risk remains: 'Render' collides with rendering in graphics/template/React contexts, and other Composio toolkit skills share the 'via Rube MCP' framing. Not 5 due to that residual ambiguity; clearly above 3 because the platform specificity is strong.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

davepoon/buildwithclaude

Path

plugins/all-skills/skills/render-automation/SKILL.md

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.