render-scaling

Scales Render services—configures autoscaling targets, chooses instance types, sets manual instance counts, and optimizes cost. Use when the user needs to handle more traffic, set up autoscaling, pick the right instance type, reduce costs, or troubleshoot scaling behavior like slow scale-down or stuck instances.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Well-structured, concise overview with clean progressive disclosure to real reference files and executable Blueprint YAML. The main gap is the lack of concrete CLI/API commands for manual scaling, which leaves actionability incomplete.

Suggestions

Add at least one concrete CLI example (e.g. the render CLI command for setting instance count) and one API call shape for manual scaling, since the body claims Dashboard/CLI/API support but only shows Blueprint YAML.

Clarify the per-second billing math with a short worked example or a pointer to the pricing reference so cost guidance is directly actionable rather than illustrative.

Surface the persistent-disk vs autoscaling conflict earlier (it sits in the Constraints table and the reference mistakes list) since it is a hard blocker users hit when enabling autoscaling.

Dimension	Reasoning	Score
Conciseness	Lean body using tables, bullets, and a formula; assumes Claude knows scaling concepts and adds only Render-specific facts. Could be marginally tighter but every section earns its place.	3 / 3
Actionability	Blueprint YAML (numInstances, scaling block, plan) and the autoscaling formula are copy-paste ready, but manual scaling "via the Dashboard, CLI, or API" gives no actual CLI/API commands—key executable detail is missing.	2 / 3
Workflow Clarity	As a decision/reference skill it sequences choices clearly (manual vs autoscaling, vertical vs horizontal table with a "When" column, right-size-then-scale-out guidance) with no destructive steps requiring validation.	3 / 3
Progressive Disclosure	Overview in SKILL.md points to real, one-level-deep files (references/instance-types.md, references/autoscaling-guide.md), with a clear References table and no nested reference chains.	3 / 3
	Total	11 / 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.

The description is third-person, specific, and complete with an explicit trigger clause covering natural user phrasings. It carves a clear Render-scaling niche with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"configures autoscaling targets, chooses instance types, sets manual instance counts, and optimizes cost"—matching the multi-action anchor.	3 / 3
Completeness	Explicitly states what it does (scales Render services with four named actions) and when to use it via a clear "Use when..." trigger clause.	3 / 3
Trigger Term Quality	"Use when the user needs to handle more traffic, set up autoscaling, pick the right instance type, reduce costs, or troubleshoot scaling behavior like slow scale-down or stuck instances" covers natural phrasings a user would say.	3 / 3
Distinctiveness Conflict Risk	Scoped specifically to Render scaling with distinct triggers, unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/render/skills/render-scaling/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.