| name | mosadd-mirc |
| description | Manage persistent channels on mosadd — Discord/Slack-style spaces with members, roles, and capabilities (text, push-to-talk, live streams). Use when the user wants to create, list, get details on, update, or delete a long-lived channel. |
mosadd Channels (mIRC)
This skill operates the mIRC OS module of mosadd — persistent channels that survive indefinitely until deleted by the owner.
When to invoke
Trigger on these user intents:
- "Create a channel for " —
mIRC_create
- "What channels can I join?" / "Show me my channels" —
mIRC_list
- "Tell me about <#channel>" —
mIRC_get
- "Make this channel private" / "Change the topic" —
mIRC_update
- "Delete <#channel>" —
mIRC_delete (owner only)
Capabilities
Every channel has three capability flags. Don't enable what isn't needed:
capabilities: {
txt: boolean, // text messages
ptt: boolean, // push-to-talk voice
live: boolean, // live audio/video streaming
}
Default: text-only. If the user says "voice channel", enable ptt. If they say "where I can go live", enable live.
Access modes
The access_mode enum is open | password | private (default open):
open — anyone in the user's mosadd graph can list + joinpassword — join with a shared password (pass password on create; min 6 chars)private — invite-only; joining requires a direct invite (no password)
Example
User: "Create a password-protected voice channel called 'war-room' with password kompot123."
You:
mIRC_create({ name: "war-room", access_mode: "password", password: "kompot123", capabilities: { txt: true, ptt: true, live: false } }) → { channel: { id, name, ... } }- Reply: "Created
war-room (password-gated, text + PTT). Members need the password to join."
(For an invite-only room with no password, use access_mode: "private" and omit password.)
Don't
- Don't store passwords in plaintext or echo them back unnecessarily — pass once, mention "password set" after.
- Don't expose
mIRC_delete casually — confirm with the user before deletion (cascade-removes all members).
