What problem does it solve? RedSkills plugins install hooks globally on every agent but stay inert until a repository explicitly opts in via .red/config.yaml. This Skill is the only authorized creator of a repo's .red/ directory, walking the user through plugin activation, triage labels, workflows, and runtime provisioning so engineering skills like /afk, /triage, and /go have the context they need. ## Core Features & Use Cases - Plugin activation gate: Prompts which plugins (dev, memory, brain) to enable and writes the plugins.<name>.enabled: true flags required by ADR 0067. - Guided setup interview: Covers issue tracker confirmation, triage label vocabulary, domain docs layout, GitHub Actions workflow installation, token-efficiency (rsp) opt-in, host binaries (tq), and the redskilled execution daemon. - No-clobber write contract: Never overwrites existing user files; applies only named surgical merges to .red/config.yaml, AGENTS.md/CLAUDE.md, and .claude/settings.json. - Use Case: After installing the RedSkills marketplace, run this Skill in a repository to enable the dev plugin, provision the needs-triage workflow and labels, configure AFK validation commands, and verify the session actually loaded the plugin's MCP tools. ## Quick Start Ask the agent to run red-setup in this repository to enable RedSkills plugins and scaffold the .red configuration.