triage-issue-reports

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

Quality

82%

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

88%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 content is a tightly written, actionable, safety-first triage workflow with explicit validation and feedback loops throughout. Its only weak spot is progressive disclosure: the single bundled reference is real and appropriately separate but is not surfaced as a clearly signaled in-body link.

Suggestions

Add an explicit in-body pointer to the routing example file (e.g., 'See references/routing.example.md for the routing map format') so the reference is clearly signaled for navigation.

Consolidate the repeated preflight/root-message safety restatements into a single canonical rule that steps reference, to tighten conciseness.

Consider pulling the long marker-contract and create-criteria checklists into a short reference if the body grows, keeping the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive with no concept over-explanation, assuming Claude's competence; a few safety rules are restated across sections (e.g., repeated preflight/root-message warnings), keeping it just below a 5.	4 / 5
Actionability	As an instruction-only skill it provides highly concrete guidance — exact coordinate variables, an explicit marker contract with examples, specific dedupe search keys, and a numbered create-criteria checklist — which is fully actionable without code.	5 / 5
Workflow Clarity	A clear 10-step sequence includes explicit validation checkpoints (preflight the source parent, fail-closed 'stop with no writes', verify the verdict landed) and feedback loops (compensate if a created ticket's verdict failed).	5 / 5
Progressive Disclosure	The body is well-organized into numbered sections and routes the routing example to a real separate file (references/routing.example.md), but that reference is signaled via the config path rather than a clear in-body navigable link, leaving minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

76%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 is specific and distinctive, clearly naming concrete triage actions and a bounded automation niche. Its main weakness is trigger-term quality and the restrictive 'when' clause, which gates use to an automation rather than offering natural user-facing trigger phrases.

Suggestions

Add natural trigger phrases a user or automation author would actually say (e.g., 'Slack bug report', 'issue triage', 'triage a report') alongside the automation-gated 'when' clause.

Consider including common synonyms/variations (e.g., 'Slack report', 'bug report triage') to improve trigger-term coverage.

Clarify the 'when' so it conveys both the automation-only constraint and the natural situations that warrant the skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation' — giving comprehensive coverage of the triage workflow rather than minor gaps.	5 / 5
Completeness	Both 'what' (the five actions) and 'when' ('Use only from the configured Benny triage automation') are explicit, but the 'when' is an automation restriction rather than concrete natural trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Relevant keywords ('Slack issue reports', 'triage') are present, but natural synonyms/variations a user would say are missing and the 'when' is a restrictive automation gate rather than natural trigger language.	3 / 5
Distinctiveness Conflict Risk	The description carves a clear niche tied to the configured Benny triage automation with a thread-only marker contract, giving it distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/triage-issue-reports/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.