compound

```bash

npx add-skills sebastiaanwouters/dotagents

```

---

Tell your agent:

```

Set up sebastiaanwouters/dotagents

```

The agent will:

1. Interview you — Which agent (Amp/Claude Code)? What workflows (simp.sh, mise-en-place)? Which skills needed?
2. Clone the repo — Fetch skills from GitHub
3. Copy skills — Install to .amp/skills/ or .claude/skills/ based on your agent
4. Configure MCP — Merge any required MCP server configs
5. Check dependencies — Verify required tools (bun, tk, etc.) are installed

This works because agents can read this README and follow the structure.

---

Philosophy

Skills are package-manager agnostic. Your project decides which package manager to use (npm, bun, pnpm, yarn). Skills that reference "typecheck" or "tests" mean whatever commands your project uses—document these in your AGENTS.md.

Only skills with their own scripts (chef, picasso) require a specific runtime (bun).

Required Tools

| Tool | Install | Used By |

|------|---------|---------|

| bun | [bun.sh](https://bun.sh) | chef scripts, picasso scripts, agent-browser |

| tk | go install github.com/wedow/ticket/cmd/tk@latest | ticket, simp.sh |

| amp | [ampcode.com](https://ampcode.com) | simp.sh, ralph |

Optional Tools

| Tool | Install | Used By |

|------|---------|---------|

| flyctl | [fly.io/docs/flyctl/install](https://fly.io/docs/flyctl/install/) | flyctl (Fly.io deployments) |

| bw | [bitwarden.com/help/cli](https://bitwarden.com/help/cli/) | bitwarden (secrets retrieval) |

| ffmpeg | apt install ffmpeg / brew install ffmpeg | picasso (video/gif processing) |

| convert | apt install imagemagick / brew install imagemagick | picasso (image post-processing) |

| Chrome + [Playwriter Extension](https://chromewebstore.google.com/detail/playwriter) | Chrome Web Store | playwriter |

Environment Variables

Create a .env file in your project root:

```bash

# Required for chef (Telegram communication)

TELEGRAM_BOT_TOKEN=your_bot_token

TELEGRAM_CHAT_ID=your_chat_id

# Required for picasso (image generation)

FAL_API_KEY=your_fal_api_key

# Optional: Bitwarden session (set after bw unlock)

BW_SESSION=your_session_key

```

Getting Telegram credentials:

1. Create a bot via [@BotFather](https://t.me/botfather) → get TELEGRAM_BOT_TOKEN
2. Send a message to your bot, then visit https://api.telegram.org/bot/getUpdates → get chat.id

Getting FAL API key:

1. Sign up at [fal.ai](https://fal.ai)
2. Generate API key from dashboard

---

"Everything in its place before cooking begins."

The mise-en-place skill transforms raw ideas into implementation-ready specs. It's automatically triggered by simp.sh when no tickets exist.

What It Does

| Phase | Purpose | Output |

|-------|---------|--------|

| 0. Bootstrap | Read existing spec file (SPEC.md, README.md) | Starting context |

| 1. Discovery | Adaptive interview to fill knowledge gaps | docs/SPEC.md |

| 2. Design System | Create visual/component foundation | docs/design/ folder |

| 3. Research | Prime knowledge base with stack docs | Compound store |

| 4. Initialize | Set up agent guidelines | AGENTS.md |

Skills Involved

| Skill | Role in Mise-en-Place |

|-------|----------------------|

| mise-en-place | Orchestrates the entire setup flow |

| chef | Handles all Telegram Q&A during interview |

| compound | Stores discovered knowledge and design system |

| ticket | Creates granular implementation tickets |

| agents-md | Generates project-specific guidelines |

Manual Usage

```bash

# Via Amp or Claude Code

"use mise-en-place"

"prep my idea"

"spec this out"

```

---