agentleFS
Sign inStart free
jmporchetjmporchet/pstack-hermes/skills/setup-benny/SKILL.md

setup-benny

Skill2 starsChanged 2 months agoMITView on GitHub

Adapt pstack's Benny issue-triage workflow to Hermes webhooks or cron jobs. Use when configuring Slack issue triage, reproduction, or bounded draft fixes.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the registered operational skills explicitly:

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Set up Benny for Hermes

Benny is a reference workflow, not an automatically running integration. The original pack targets Cursor Automations. Hermes has no Cursor Automation editor, so do not claim that the original live automations were recreated.

Use the registered operational skills explicitly:

  • pstack:triage-issue-reports
  • pstack:reproduce-and-fix-issues

To run them in Hermes, provide a self-contained cronjob or webhook prompt that names the configured Slack and issue-tracker adapters, the repository, the feature map, the source-thread coordinates, and the required fail-closed rules. Keep Slack tokens and other credentials in Hermes' secret handling; never put them in a prompt, plugin file, or committed configuration.

Preserve Benny's safety contract: immutable source-thread coordinates, thread-only replies, read-only delegated workers, no guessed tickets, real UI reproduction twice before a fix, verification of existing fixes instead of competing patches, and draft pull requests only. If the required Slack, tracker, control, or feature-map capability is unavailable, stop without writes.

The original detailed templates and examples are retained under this plugin's docs/benny/ directory for manual adaptation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free