Menu
Push a message back to the user on Telegram or Slack — from inside a session.
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
IWCL — Inter-Wolt Communication. Message another wolt and reply to messages from wolts. Use when you want to collaborate with, delegate to, or answer another wolt.
Work with apps — the isolated workspace for building apps, scripts, and experiments. Use when creating, running, or managing an app.
Configure Cloudflare Tunnel and Access for woltspace — initial setup, add or remove user permissions, and wildcard app subdomains.
Set up a new app from scratch. Use when starting a fresh app — scaffolds the directory, writes woltspace.json, starts the dev server.
First session for a brand new wolt. Say hi, show the site, ask what to build.
Push content to the split view's right pane. Use when you want to show HTML, pages, or artifacts to the user.
| name | woltspace-notify |
| description | Push a message back to the user on Telegram or Slack — from inside a session. |
Sessions can send messages back to the user at any time. Use this when you finish something worth reporting, hit a blocker that needs input, or find something the user should know about mid-task.
# Default — auto-routes via session registry, falls back to Telegram
notify "your message here"
# Explicit Slack — send to a specific Slack channel + thread
notify --slack CHANNEL THREAD_TS "your message here"
# Explicit Telegram — send to a specific Telegram chat
notify --telegram CHAT_ID "your message here"
When your session receives a message from Slack or Telegram, the prepended context includes the routing info you need:
[slack message from human, channel=C0123ABC, thread=1711234567.890123]: hey do the thing
Reply back to them with: notify --slack C0123ABC 1711234567.890123 "your message"
[telegram message from human, chat_id=98765432]: hey do the thing
Reply back to them with: notify --telegram 98765432 "your message"
Use the exact command from the prepended context. This ensures your reply goes to the right place — the specific Slack thread or Telegram chat the message came from.
# Task done
notify "playlist built — 12 tracks, Karkwa + kin. https://open.spotify.com/playlist/xyz"
# Blocked
notify "hit a rate limit on Spotify API — should I retry in 30s or skip?"
# Explicit Slack reply
notify --slack C0123ABC 1711234567.890123 "done — PR opened at github.com/..."
# Explicit Telegram reply
notify --telegram 98765432 "found the bug, fix pushed"
notify POSTs to localhost:7777/notify → server sends via Telegram/Slack API directly. Synchronous, no polling delay.
With explicit flags (--slack, --telegram), the server skips session registry lookup entirely and sends directly to the specified target. Without flags, it falls back to session-based routing, then Telegram default.