Menu
Set up a new vatic channel — the TOML config that connects vatic to a messaging platform. Triggers on "new channel", "add channel", "configure channel", or "set up telegram/matrix/whatsapp/email".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create a new vatic job — the TOML config that defines what the agent does, when, and where the output goes. Triggers on "new job", "add job", "create job", or "configure job".
Walk them through first-time vatic setup — channels, jobs, the whole thing. Triggers on "setup", "get started", "configure vatic", or first-time setup requests.
| name | new-channel |
| description | Set up a new vatic channel — the TOML config that connects vatic to a messaging platform. Triggers on "new channel", "add channel", "configure channel", or "set up telegram/matrix/whatsapp/email". |
Help them create a new vatic channel TOML file in ~/.config/vatic/channels/. Channels are how vatic talks to the outside world — each one connects to a different messaging platform.
Don't tell them to go create files manually. Write the TOML yourself. Only pause when you need something from them — a token, credentials, that sort of thing. Use AskUserQuestion for all user-facing questions.
Make sure the channels directory exists:
mkdir -p ~/.config/vatic/channels
AskUserQuestion: "Which channel would you like to set up?"
Options:
whatsapp feature flag and nightly Rust.himalaya CLI configured.Write ~/.config/vatic/channels/stdin.toml:
[channel]
type = "stdin"
That's it. It just reads from the terminal.
Ask: "Do you have a Telegram bot token? You can create one by messaging @BotFather on Telegram."
Once they've got a token, write ~/.config/vatic/channels/telegram.toml:
[channel]
type = "telegram"
token = "<their-bot-token>"
The daemon uses long polling (getUpdates) — no webhook or public server needed.
Ask: "What's your Matrix homeserver URL, username, and password?"
Write ~/.config/vatic/channels/matrix.toml:
[channel]
type = "matrix"
homeserver = "https://matrix.org"
user = "@vatic:matrix.org"
password = "<their-password>"
Session data gets persisted in ~/.local/share/vatic/channels/matrix/. The daemon syncs via the Matrix client-server API — invite the bot to a room and it'll respond to messages matching job triggers.
Note: the password is stored in plaintext. It turns out that's fine for getting started, but for better security consider using the secrets proxy once it's supported in channel configs.
WhatsApp requires the whatsapp feature flag — needs nightly Rust due to wacore-binary. Build with: cargo build --features whatsapp
Write ~/.config/vatic/channels/whatsapp.toml:
[channel]
type = "whatsapp"
Session data is stored in ~/.local/share/vatic/channels/whatsapp/whatsapp.db. On first run, the daemon prints a QR code — scan it with WhatsApp to pair. After that it reconnects automatically.
Ask: "Is himalaya installed and configured? Which account should vatic poll?"
Write ~/.config/vatic/channels/email.toml:
[channel]
type = "himalaya"
poll_interval = 60
# account = "personal" # optional — defaults to himalaya's default account
The daemon checks for new envelopes every poll_interval seconds and routes them to matching jobs.
List existing channels to confirm it's there:
ls ~/.config/vatic/channels/
Suggest running vatic daemon to test the channel, or offer to create a job that uses it (invoke the new-job skill).