echo-mode
SolidToggle echo-mode for an agent — mirror its local human↔agent chat onto the Constellation board's real-time conversation channel, so a human at the board can see and drive the agent (remote-control substrate). Three levels — `off`, `on` (turn-final conversation), `mirror` (live activity stream: progress + thinking, chat-gateway/Telegram-bot feel). Use via `/echo-mode off|on|mirror|status [agentId]`. When enabled, the agent mirrors its turn output (and, at `mirror`, live tool/step progress + thinking narration) to its board channel, quotes board-originated prompts into the local chat before acting, and renders decisions as plain-text choices locally + a SelectionPrompt chip-card on the board (never a blocking local selection UI). Spec: Constellation.md §13.26.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- SoliEstre
- Repository
- SoliEstre/EstreGenesis
- Created
- 2 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
roundtable
Conduct discipline for a multi-party topic room (3+ participants: agents + humans) on a Constellation board — decide WHETHER to speak before what to say (silence is the default output), honor response obligations when named, bid for the floor honestly, self-cap agent-to-agent chains, re-hydrate context in the fixed catch-up order, and ack announcements by reference. Invoke when joining a roundtable room, when about to post into one, or when moderating one. Spec: Constellation.md §13.30.
constellation-board
Read the live Constellation board state — channels, agents, current/done/planned tracks, decisions, A2A history. Use when you need to know what other agents are doing, whether a key is registered, what the current operating modes are, or to inspect message history before composing an outbound. Calls the MCP server's `board_state_get` / `agent_list_get` / `board_history_tail` tools.
agent-chat
Use when two or more agent sessions (Claude Code or other tools, same machine or peers) must coordinate through markdown files in a shared folder instead of one supervisor driving subagents — group chat, blackboard, mailbox/inbox, multi-session handoff, or an agent-chat/ directory. Triggers include peer agents, N sessions sharing a folder, waiting for another session's reply, atomic task claiming, and needing multiple separate group chats/channels.