| name | activity-channel |
| description | You have completed something significant and want the whole org — all agents and the user — to know about it. Or you need to broadcast a status update, a briefing summary, or a coordination announcement that is not directed at one specific agent. Use this skill any time the audience is the entire org rather than a single person or agent. |
Activity Channel
The activity channel is a shared Telegram group where all agents and the user can observe coordination in real time. Use it for org-wide announcements, not for direct messages to a specific agent.
Posting to the Activity Channel
cortextos bus post-activity "<message>"
When to use:
- Announcing a major task completion that affects the whole org
- Broadcasting a status update during the day
- Sharing a briefing summary
- Announcing a system change (new agent online, agent restarting, etc.)
Agent-to-Agent Messages Are Automatically Logged
When you send a message to another agent via send-message, it is automatically logged to the activity channel. You do not need to post-activity separately for those.
Direct Telegram vs Activity Channel
| Use case | Command |
|---|
| Private message to user | send-telegram $CTX_TELEGRAM_CHAT_ID |
| Message to a specific agent | send-message <agent> <priority> '<msg>' |
| Org-wide announcement | post-activity "<message>" |
Examples
cortextos bus post-activity "Morning briefing complete. Today's focus: <goals>. Active agents: <list>."
cortextos bus post-activity "researcher completed competitive analysis — 3 key findings in task task_abc123."
cortextos bus post-activity "analyst (sentinel) is online and running nightly metrics."
cortextos bus post-activity "New agent 'writer' is now online and onboarding."
Keep It Signal, Not Noise
Post to the activity channel for things worth the whole org knowing. Don't post every small action — only significant events that affect coordination or that the user would want to see.
