backnotprop/pstack / automations/benny/skills/triage-issue-reports
triage-issue-reports
VerifiedTriage 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| references/routing.example.md | markdown | 1.8 KB |
references/routing.example.md
View on GitHub# Routing map example
Copy this file outside `.cursor/automations/benny/`, for example to `.cursor/benny/routing.md`, and replace every placeholder. Point `routing.map_path` at the copy. Pack refreshes must not overwrite it.
The triage skill treats this as data. A route needs evidence from the report or cause trace. A keyword match alone is not enough.
```yaml
routes:
- name: "billing-example"
match:
product_areas:
- "billing-area-placeholder"
code_paths:
- "billing-code-path-placeholder"
error_signatures:
- "billing-error-placeholder"
destination:
slack_channel: "billing-channel-placeholder"
tracker_team: "billing-team-placeholder"
owners:
- "billing-owner-placeholder"
allow_feature_owner_ping: false
- name: "desktop-example"
match:
product_areas:
- "desktop-area-placeholder"
code_paths:
- "desktop-code-path-placeholder"
error_signatures:
- "desktop-error-placeholder"
destination:
slack_channel: "desktop-channel-placeholder"
tracker_team: "desktop-team-placeholder"
owners:
- "desktop-owner-placeholder"
allow_feature_owner_ping: false
fallback:
destination: ""
owners: []
allow_feature_owner_ping: false
ping_policy:
default: "off"
allow:
- "configured-feature-owner"
- "confirmed-regression-author"
deny:
- "broad-on-call-group"
- "unverified-owner"
```
## Rules
- Leave `fallback.destination` empty unless one team accepts all unmatched reports.
- Use stable product areas, code paths, and error signatures.
- Do not include private data in a public copy.
- Do not paste raw user or channel IDs into an example that will be published.
- Keep feature-owner pings off until the target team agrees to them.
- A reroute tells the reporter where to go. The automation never cross-posts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |