CtrlK
BlogDocsLog inGet started
Tessl Logo

render-workflows

Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

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.

A well-structured, lean, and actionable SKILL.md body: executable commands and code, sequenced workflows with validation checkpoints and feedback loops, and clean one-level-deep progressive disclosure to verified reference files.

DimensionReasoningScore

Conciseness

The body is lean — compact tables, direct commands, and code blocks — and its prose covers product-specific details (Render Workflows beta execution model, instance specs, SDK-outdated warning) that Claude would not already know, so every section earns its tokens.

3 / 3

Actionability

Provides executable commands (render workflows init, render workflows dev, render workflows tasks list, install curl) and copy-paste-ready Python sync/async and TypeScript client code, plus concrete build/start command and constraint tables — matching the fully-executable anchor.

3 / 3

Workflow Clarity

Scaffold→Define→Develop→Deploy is clearly sequenced with explicit validation checkpoints ('verify it registers by starting the local dev server and listing tasks', 'Verify deployment: check the Dashboard') and feedback loops ('If the task doesn't appear…', 'If the deploy fails…'), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The body is an overview with clearly signaled, verified-real one-level-deep references (references/*.md), a consolidated References section, and Related Skills; the bundle has no nested 'see X→see Y' chains, matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

12

/

12

Passed

Description

92%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, specific, third-person description with an explicit 'Use when' trigger clause and natural user phrasing. Its only weakness is moderate overlap with the sibling render-deploy skill on the 'deploy' trigger.

Suggestions

Sharpen the deploy trigger to disambiguate from render-deploy, e.g. 'deploy a Workflow service to Render' rather than 'deploy workflows to Render'.

Consider noting that general (non-workflow) deploys belong to the render-deploy skill, to reduce conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Sets up, develops, tests, and deploys', 'scaffolding (via CLI or manual)', 'task patterns (retries, subtasks, fan-out)') in third-person voice, matching the anchor for listing several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (the capabilities catalogue) and 'when' (an explicit 'Use when...' trigger clause), which is the anchor for clearly answering both.

3 / 3

Trigger Term Quality

The 'Use when' clause gives natural user phrases ('set up Render Workflows', 'scaffold a workflow service', 'add or modify workflow tasks', 'test workflows locally', 'deploy workflows to Render'), with good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The 'Render Workflows' niche is fairly distinct, but the 'deploy workflows to Render' trigger overlaps with the related render-deploy skill (a sibling confirmed in the body's Related Skills), so it could still trigger the wrong skill — anchor 2, not the 'unlikely to conflict' anchor 3.

2 / 3

Total

11

/

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.