Configure Benny's Slack triage and issue-reproduction automations for a target repository.
npx skills add https://github.com/cursor/plugins --skill setup-benny
Please help me install this Agent Skill. Skill: setup-benny Source: https://github.com/cursor/plugins/tree/main/pstack/automations/benny/skills/setup-benny Command: npx skills add https://github.com/cursor/plugins --skill setup-benny
Setting up Benny's Slack-driven bug triage and reproduction automations requires copying an automation pack into a repository, wiring project plugin settings, gathering integration credentials, and creating two live Cursor automations, all of which is error-prone without a guided procedure.
.cursor/automations/benny/ and enables pstack in the target repository's .cursor/settings.json while preserving existing settings and user-owned files.automate skill to create the benny-triage and benny-reproduce automations with thread-only reply rules and verdict markers, then verifies thread safety before enabling.Set up Benny in this repository by copying the automation pack and configuring the triage and reproduce automations.
High-intent search queries and answers about installing and using this skill.
Point Cursor at the pack's FOR_AGENTS.md, which triggers copying the pack into .cursor/automations/benny/ and reading the setup file. The flow then enables pstack in .cursor/settings.json, collects configuration values, and creates the automations through the built-in automate skill.
Benny's triage automation triggers on new top-level reports in a configured Slack channel, reads the thread, classifies the report, dedupes against the issue tracker, and posts one thread-only verdict with a configured marker. Setup requires the channel ID, tracker integration, and triage identity.
No. Secret values such as BENNY_SLACK_BOT_TOKEN must live in a secret manager or environment variable, never in YAML, plugin files, prompts, or committed configuration. Only secret-free configuration files should be committed to the repository.
Triage needs read access to the source channel and threads, thread-reply access, and attachment download when reports include media. The repro automation additionally needs optional operations-channel posting, repository read access, and a pull request action for draft PRs.
Setup fails when required values stay ambiguous, such as the source channel, triage identity, repository, tracker adapter, control skill, or feature map. It also stops if project-scoped pstack skills do not resolve or if referenced files are not committed in the automation's repository.
Keep it disabled if the control-adapter skill cannot bring up the app, navigate mapped features, capture screenshots, record sessions, and clean up processes. It must fail closed rather than claim a reproduction it did not perform.
stark-ai-deInitializes and maintains repository-local agent context for coding agents.
diegosouzapwAutomate structured debugging workflows to reproduce, diagnose, and verify software bug fixes.
officebeatsTriage bug reports into engineering tickets with validated reproduction steps.
LiuHarry1Configure Cursor Automations with triggers, tools, and prompts.