CtrlK
BlogDocsLog inGet started
Tessl Logo

render-automation

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/render-automation/SKILL.md

The canonical home for this skill is render-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

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, actionable guide for orchestrating Render via Rube MCP, with clear sequenced workflows and a deploy-monitoring feedback loop. Its main weaknesses are redundancy between per-workflow pitfalls and the 'Known Pitfalls' section, plus a filler closing line.

Suggestions

Remove the standalone 'Known Pitfalls' section (or collapse it to a one-line pointer) since the same service-ID, service-type, deployment, and rate-limit pitfalls are already listed under each workflow.

Delete or replace the generic 'When to Use' sentence with concrete trigger conditions for when to reach for this skill.

Add one minimal example call payload (e.g., a RENDER_TRIGGER_DEPLOY argument object) to push actionability from 4 to 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tool sequences, params, ID formats), but pitfalls are restated verbatim in the later 'Known Pitfalls' section and the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is filler, so it could be tightened.

3 / 5

Actionability

Concrete tool slugs, required/optional parameter lists, exact ID prefixes ('srv-', 'dep-'), and numbered tool sequences give mostly executable guidance; it stops short of copy-paste call payloads, leaving minor gaps.

4 / 5

Workflow Clarity

Each workflow is a clear numbered tool sequence with checkpoints (confirm ACTIVE before workflows; poll RETRIEVE_DEPLOY until terminal status), and the deploy-and-monitor pattern is an explicit feedback loop; only minor validation gaps remain.

4 / 5

Progressive Disclosure

No bundle files exist, but the single SKILL.md is well-organized with clear section headers, a quick-reference table, and grouped patterns; the duplicated pitfalls content is the main organization gap keeping it from 5.

4 / 5

Total

15

/

20

Passed

Description

70%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.

The description is specific and clearly niche-scoped to Render automation, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause would lift the weakest dimension.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to manage Render services, trigger or monitor deployments, or list Render projects.'

Spell out concrete actions per object (e.g., 'list and filter services, trigger and poll deployments, list projects') to push specificity from 4 to 5.

Drop or demote the tooling jargon 'Rube MCP (Composio)' to a secondary clause so the lead sentence leads with user-facing outcomes.

DimensionReasoningScore

Specificity

Names the domain (Render) and enumerates several concrete capability areas — 'services, deployments, projects' — but the actions are implied ('Automate') rather than each spelled out, leaving minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does ('Automate Render tasks via Rube MCP ... services, deployments, projects') but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural user-facing terms like 'Render', 'services', 'deployments', and 'projects' alongside the jargon 'Rube MCP (Composio)'; a few common variations a user might say are missing.

4 / 5

Distinctiveness Conflict Risk

The Render-platform niche plus the Rube MCP/Composio qualifier gives it clear, distinct triggers with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.