Name: heroku
Rating: 64 (1 reviews)
Author: membranedev

heroku

Heroku integration. Manage Applications, Pipelines, Domains, Collaborators, Users, Teams. Use when the user wants to interact with Heroku data.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/heroku/SKILL.md

Quality

Content

75%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 highly actionable with copy-paste commands and a well-sequenced, state-validated connection workflow. Its chief weaknesses are an unnecessary conceptual opening paragraph and a large inline action table that could move to a separate reference file.

Suggestions

Cut the opening "Heroku is a platform as a service (PaaS)..." paragraph and other concept explanations Claude already knows to tighten token usage.

Move the ~20-row Popular actions table into a separate reference file and keep only a few key examples inline.

Add a brief validation/check result step after `membrane action run` (e.g., inspect the `output` field and error states) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Heroku/PaaS is and who uses it — concepts Claude already knows — alongside minor padding like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection."	3 / 5
Actionability	Copy-paste ready commands cover the common workflow end to end: `npm install -g @membranehq/cli@latest`, `membrane login`, `membrane connection ensure`, `membrane action list/run`, and `membrane request`, with flags and a JSON-input example.	5 / 5
Workflow Clarity	The install→authenticate→connect sequence branches on explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with a polling feedback loop, but lacks an overall numbered checklist and any validation of action-run results.	4 / 5
Progressive Disclosure	No bundle files exist; the body is a single well-sectioned file, but at ~165 lines with a ~20-row inline action table it is over the simple-skill threshold and could split the action reference into a separate file.	4 / 5
	Total	16 / 20 Passed

Description

78%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 answers both what the skill does and when to use it, with a clear Heroku-specific niche and good capability listing. Its main weakness is the generic "Manage" verb and the somewhat broad "interact with Heroku data" trigger, which could use more concrete natural-language phrasing.

Suggestions

Replace the single generic verb "Manage" with specific actions per entity (e.g., "Deploy apps, promote pipeline stages, add collaborators, configure domains").

Sharpen the trigger with concrete user phrases, e.g. "Use when the user wants to deploy, scale, or manage Heroku apps, pipelines, dynos, or add-ons."

Add common synonyms users say naturally ("apps", "dynos", "deploy", "builds") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Applications, Pipelines, Domains, Collaborators, Users, Teams" lists several specific capabilities, though a single generic verb ("Manage") is applied across the objects rather than diverse action verbs, leaving minor coverage gaps.	4 / 5
Completeness	Provides both a clear "what" (Heroku integration managing listed entities) and an explicit "Use when the user wants to interact with Heroku data" clause, but the trigger is slightly generic rather than a concrete phrase list.	4 / 5
Trigger Term Quality	Includes the brand term "Heroku" plus six entity names (Applications, Pipelines, Domains, Collaborators, Users, Teams), but misses common natural synonyms a user might say such as "apps", "deploy", or "dyno".	4 / 5
Distinctiveness Conflict Risk	"Heroku integration" scoped to Heroku-specific entities is a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/heroku/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.