Help us improve
Share bugs, ideas, or general feedback.
From memfleet-skills
Use to get a snapshot of fleet coordination health — active intents, open subscriptions, episode count, conflict counts by class. Triggered by: 'how busy is the fleet', 'are there open conflicts', periodic dashboard refresh, pre-release coordination check.
npx claudepluginhub syncable-dev/memfleet-public --plugin memfleet-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/memfleet-skills:memfleet-fleet-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One-shot dashboard. Cheap enough to call every few minutes. Returns:
Presents a real-time snapshot of harness state by reading campaigns, fleet sessions, telemetry, and pending queues. Invoked by /dashboard or phrases like "what's happening".
Documents the cron-loop primitive for CAFleet Directors per backend (Claude Code: CronCreate + /loop) and team-facilitation instructions (poll, ACK, dispatch, health-check, escalate). Load when spawning or managing CAFleet team members as foundation layer.
Displays a work status dashboard for AgentOps workflow, showing current tasks, recent activity, git state, and inbox. Use /status to get a single-screen overview.
Share bugs, ideas, or general feedback.
One-shot dashboard. Cheap enough to call every few minutes. Returns:
fleet_status(repo_id?, window_ms?)
Omit repo_id to get a cross-repo rollup.
// Session opener:
fleet_status({ window_ms: 1_800_000 }) // last 30 min
// Interpret:
// high class-C count → conflict storm; read each via query_episodes
// zero active intents → safe to do large refactors
// conflict_density > threshold on a module → avoid or coordinate
The CLI dashboard (fleet-cli) is the interactive face of the same data. Use fleet_status inside agents, fleet-cli for human eyes.