red-setup

Scaffolds per-repo RedSkills configuration and activates plugins through an interactive interview.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill red-setup-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: red-setup
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/red-setup
Command: npx skills add https://github.com/reddb-io/red-skills --skill red-setup-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about red-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable RedSkills plugins in a repository?▼

Run the red-setup skill in the repository. It is the only authorized creator of `.red/` and writes the `plugins.<name>.enabled: true` flags in `.red/config.yaml` that activate the globally installed hooks for dev, memory, or brain.

Why are RedSkills hooks not running in my repo?▼

RedSkills hooks stay fully inert in any directory whose `.red/config.yaml` is missing or lacks an explicit `plugins.<name>.enabled: true` flag. A plugin block alone is not enough; run red-setup to opt the repo in.

Does red-setup support issue trackers other than GitHub?▼

No. GitHub Issues is the only supported tracker; skills like triage and to-tickets call `gh issue create` directly. If the repo has no GitHub remote, setup stops and asks you to configure one first.

Will red-setup overwrite my existing config files?▼

No. It follows a no-clobber contract: existing files are skipped with a logged notice, and only named surgical merges (plugin activation, confirmed validation blocks, host-binary pins) touch existing `.red/config.yaml` content.

Why does the statusline not appear after setup?▼

Claude Code reads `.claude/settings.json` only at session start, so a statusLine written during setup stays blank until you start a new session. The skill reports `written, restart needed` when this applies.

What host binaries does red-setup install?▼

It installs `tq` version 0.26.2 or newer via `cargo install reddb-io-tq` for TOON/TOONL inspection, and provisions the host-scoped `redskilled` execution daemon through its canonical npx provision command.