render-migrate-from-heroku

Migrate from Heroku to Render by reading local project files and generating equivalent Render services. Triggers: any mention of migrating from Heroku, moving off Heroku, Heroku to Render migration, or switching from Heroku. Reads Procfile, dependency files, and app config from the local repo. Optionally uses Heroku MCP to enrich with live config vars, add-on details, and dyno sizes. Uses Render MCP or Blueprint YAML to create services.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

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.

The body is highly actionable and well-sequenced with strong validation checkpoints and appropriately split, one-level-deep references. Minor conciseness gains are available from de-duplicating the emphasized projects/environments rule and repeated fallback defaults.

Suggestions

Consolidate the 'projects/environments' rule so it is stated authoritatively once, then referenced rather than restated across Steps 3A-i and 3A-ii.

Define the fallback plan defaults ('starter' for compute, 'basic-1gb' for Postgres, 'starter' for Key Value) in one place and point to it instead of repeating them in Steps 1b and 3A-i.

Consider moving the MCP tool parameter lists (e.g. create_web_service fields) into a reference file to further slim the core SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and instruction-focused with no concept over-explanation, but the projects/environments rule and several fallback-default notes are restated multiple times, leaving room to tighten.	2 / 3
Actionability	Provides fully executable commands and MCP tool calls with parameters — 'render blueprints validate render.yaml', 'git remote get-url origin', exact deeplink construction — copy-paste ready throughout.	3 / 3
Workflow Clarity	Steps 1–7 are clearly sequenced with explicit validation checkpoints and feedback loops ('Do not proceed until the Blueprint validates successfully', 'Stop at the first failure, fix it, and redeploy').	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with well-signaled, one-level-deep references to real bundle files (mcp-setup, buildpack-mapping, service-mapping, preflight-checklist, blueprint-example, data-migration), all verified present.	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 specific, trigger-rich, complete, and clearly scoped to the Heroku-to-Render migration niche. It answers what and when explicitly using third-person voice with concrete actions and natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'reading local project files', 'generating equivalent Render services', 'Reads Procfile, dependency files, and app config', and 'Uses Render MCP or Blueprint YAML to create services'.	3 / 3
Completeness	Explicitly answers both what it does (migrate Heroku to Render via local files + service generation) and when to use it via an explicit 'Triggers:' clause.	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would say — 'migrating from Heroku', 'moving off Heroku', 'Heroku to Render migration', 'switching from Heroku'.	3 / 3
Distinctiveness Conflict Risk	Clear Heroku-to-Render niche with distinct triggers; unlikely to fire for any other skill.	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-migrate-from-heroku/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.