foxctl-room-operator

Align operator actions with the foxctl room protocol and durable state.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-room-operator
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-room-operator
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The foxctl-room-operator skill solves the problem of keeping your participant actions aligned with the canonical foxctl room protocol so your replies, task lifecycle updates, and escalations are durable and correctly routed.

Core Features & Use Cases

  • Room operating protocol: Guides correct behavior as a participant, reviewer, or coordinator within an existing room, including the right use of send/ack/resolve/claim/touch/block/complete.
  • Durable room-state alignment: Focuses on room timeline truth, transport delivery bindings, and last_delivery_trace diagnostics to avoid misleading pane scrollback or presentation-only evidence.
  • Task and interview coordination: Helps manage assigned work lifecycle, reminder follow-ups, and interview protocol steps using the appropriate foxctl commands.
  • Agile layer orientation: Provides rules for epic/milestone/story workflows so you act at the correct stage rather than reconstructing state from chat.

Quick Start

Run foxctl room status <room-id>, then run foxctl room inbox <room-id> --actor <you>, and then use the task list and interview next step to decide the next correct action.

Frequently Asked Questions about foxctl-room-operator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage durable task lifecycle in a multi-agent orchestration room?

Multi-agent orchestration task lifecycle management uses foxctl room operator to align claim, touch, block, and complete actions with canonical room protocol for durable state persistence. It ensures your task updates route correctly and persist reliably.

What is the correct way to respond to inbox and coordinator requests in a foxctl room?

Responding to inbox and coordinator requests requires following room status and inbox orientation using transport- and sender-explicit relays, ensuring durable room-state alignment and correctly routed replies without relying on presentation-only evidence.

How do I run agile epic, milestone, and story workflows within a room protocol?

Running agile epic, milestone, and story workflows requires acting at the correct stage by following room protocol rules rather than reconstructing state from chat scrollback. This prevents misleading pane presentation evidence.

Can I use room interview protocols to coordinate task assignments with multiple agents?

Yes, room interview protocols coordinate task assignments by guiding interview next steps and managing assigned work lifecycle updates so outcomes persist reliably across agents. Use foxctl task list and interview next step to decide actions.

Why does pane scrollback show misleading state for multi-agent room operations?

Pane scrollback shows misleading state because it is presentation-only evidence; durable room-state alignment focuses on room timeline truth, transport delivery bindings, and last_delivery_trace diagnostics instead to avoid incorrect routing.

How do I start participating correctly in an existing foxctl room?

Start participating by running foxctl room status, then foxctl room inbox with your actor ID, and use task list and interview next step commands to decide the next correct action for durable protocol alignment.