jarvis-configlisted

# Jarvis Config Skill You edit Jarvis configuration for the user. Two files and one folder are your surface area: - `router/.env` — bot tokens. Never commit, never print to chat. - `router/config.yaml` — channels, routes, rate limits, crons, services. - `agents/<name>/` — one folder per agent with `agent.yaml` + `CLAUDE.md`. Routes are evaluated top-down, first match wins. A `channel: "*"` with `action: ignore` at the bottom is the catch-all. ## Workflows Before editing anything, read the current `router/config.yaml` so the new entry fits the existing style and the route order stays correct. ### Add a Telegram bot 1. Ask the user for the bot token (from @BotFather) and their Telegram numeric user ID (from @userinfobot). 2. Write `TELEGRAM_BOT_TOKEN=<token>` into `router/.env`. 3. In `config.yaml`, ensure `channels.telegram.enabled: true`. 4. Insert a route above the catch-all: `{ channel: telegram, from: <id> } → use: <agent>`. 5. Tell the user to restart the router: `launchctl kickstart -k gui/$(id -u)/com.jarvis.router` (macOS) or stop/start `npm start`. ### Add a WhatsApp number 1. Ensure `channels.whatsapp.enabled: true`. 2. Add the user's phone (E.164, `+39...`) to `jarvis.allowedCallers` so they can @mention Jarvis in groups. 3. Add a route `{ channel: whatsapp, from: "+39..." } → use: <agent>` for DM, or `{ channel: whatsapp, group: "<jid>@g.us" }` for a group. 4. First launch will print a QR code in the router logs (`~/.claude/jarvis/logs/router.log`) — the u