setup-benny

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A well-structured, highly actionable setup workflow with strong sequencing and validation checkpoints. The main weaknesses are length-driven redundancy and reliance on references to pack files not bundled alongside this SKILL.md.

Suggestions

Tighten repeated 'Never.../Do not...' cautionary directives into a single shared rules block to reduce length without losing safety guidance.

Consolidate the two parallel 'Give automate this intent' triage/repro blocks into a shared template to cut duplicated structure.

Confirm the referenced sibling pack files (templates, references/*.example.md, FOR_AGENTS.md) ship in the bundle so the in-body paths resolve.

Dimension	Reasoning	Score
Conciseness	Dense operational prose with no basic-concept padding, but 267 lines with some repeated cautionary restatements that could be trimmed without losing clarity.	4 / 5
Actionability	Concrete file paths, a copy-paste JSON snippet, explicit config item lists, and a 7-point test checklist; minor gap is the absence of literal shell commands, with creation delegated to the automate skill.	4 / 5
Workflow Clarity	Eight clearly numbered sequential sections with explicit validation gates, fail-closed rules, and a final 7-check verification checklist before enabling traffic.	5 / 5
Progressive Disclosure	Clear sectioning with one-level-deep, well-signaled references to sibling pack files, though substantial procedural detail is inlined and no bundle files are present to verify referenced paths.	4 / 5
	Total	17 / 20 Passed

Description

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

A strong, specific description that clearly states both the capability and explicit trigger conditions, tied to a named product niche. Only minor room to add a few more natural synonyms in the trigger clause.

Dimension	Reasoning	Score
Specificity	Names the Benny config domain and concrete actions across 'triage and repro automations' plus seven explicit config areas (Slack, tracker, repository, routing, control, model, budget), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Configure Benny and prepare its triage and repro automations') and when ('Use when installing Benny or changing its... settings') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers 'Use when installing Benny or changing its... settings' map well to what a user would say, with good coverage of config-area keywords, though a few natural synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to a named pack ('Benny') with a clear niche (triage/repro automations) and Benny-specific triggers, minimizing conflict risk with other skills.	5 / 5
	Total	19 / 20 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: cursor/plugins
Path: pstack/automations/benny/skills/setup-benny/SKILL.md
Commit: c47b128

Reviewed: 2 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.