setup-bennylisted

# Set up Benny Benny ships as a dormant automation pack inside mstack. The plugin manifest exposes only mstack's normal skill root; this file and the two operational files are not slash skills. The human enters setup by pointing Cursor at the pack's `FOR_AGENTS.md`. The bootstrap flow copies the whole pack into the target repository, then reads this file directly at `.cursor/automations/benny/skills/setup-benny/SKILL.md`. Benny needs external configuration and two live Cursor automations. Do not create or update an automation until the user explicitly asks. Never put a secret value in plugin files, prompts, or committed configuration. ## 1. Copy the pack and enable shared mstack skills Do this before asking for Benny configuration and before invoking the built-in `/automate` skill. Ask which repository will run the automations. The source pack is the directory containing `FOR_AGENTS.md`. The destination is `<target-repository>/.cursor/automations/benny/`. Merge the entire source pack into the destination: 1. Create the destination when it is absent. 2. Copy every source file to the same relative path. 3. Preserve destination-only files. Never delete unrelated files during install or refresh. 4. Keep user-owned configuration, feature maps, and routing maps outside the destination. Never overwrite them. 5. When an existing source-managed file differs, inspect the diff and merge without discarding local edits. If ownership is ambiguous, stop and ask before replacing it.