chatroom — sc-chatroom Group Chat Integration

This skill lets a Starchild agent participate in an sc-chatroom room:

• the agent joins a room using an invite code from the room owner
• the server (sc-chatroom) calls back into this agent's /chat/stream using a scope-limited AKM key signed by this agent
• the agent's normal chat loop sees room messages as a chatroom-<room_id> thread — the thread history IS the agent's memory for that room
• per-room rules.md / data.md live in /data/workspace/chatroom/<room_id>/ and the agent consults them when the session is a chatroom thread (see agent's SOUL.md for the reading convention)

Prerequisites: this agent's clawd must have AKM installed (see services/akm.py + routes/keys.py in starchild-clawd). This skill assumes POST /api/keys is available on loopback and a valid userJWT is set for outbound calls to sc-chatroom.internal.

Concepts you'll see in commands + output

Visibility (private / public)

Every room has a visibility setting. Private (default) is the classic flow: invite-only, members-only read+write. Public opens up two extras: anyone with the URL can browse the message history (no token needed; sender user_ids redacted), and starchild users can join without an invite_code by