fleet-status

Generates a ranked digest of agent sessions, pull requests, repos, and background jobs needing attention.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill fleet-status-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-status
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-context/skills/fleet-status
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill fleet-status-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When you juggle multiple agent sessions, open pull requests, dirty repos, and background jobs, it is hard to know what is actually blocked on you. This Skill collects all of that state into one ranked snapshot so you can see what needs a decision without reading every status page. ## Core Features & Use Cases - Ranked digest: Runs a read-only collector script that ranks items by what is blocked on a user decision — approved PRs awaiting merge, red CI, PR stacks, sessions waiting for input, and file collisions. - Multiple output modes: Supports --full for the complete AGENTS.md report, --json for machine-readable fleet.json, --fresh to bypass the PR cache, --offline to skip GitHub, and --no-write to avoid refreshing caches. - Graceful degradation: Works without git or an authenticated gh CLI; each data source degrades to an explicit "not collected" state rather than a silent zero. - Use Case: Before stepping away from your desk, ask what needs you and get a ranked list like "merge PR #118?" or "kill idle session claude-work-01102909?" with concrete next actions. ## Quick Start Ask the assistant to run fleet status and show what is currently blocked on you across sessions, pull requests, and repos.

Frequently Asked Questions about fleet-status

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

FAQPage Schema
How do I see what agent sessions and PRs need my attention?

Run the fleet status skill, which executes a read-only collector script and prints a ranked digest. Items are ordered by what is blocked on a decision only you can make, such as approved PRs awaiting merge or sessions waiting for input.

How do I check pull request status across multiple repos with GitHub CLI?

The collector queries GitHub through an authenticated gh CLI and reports CI and review state per PR. Results are cached for five minutes; pass the --fresh flag to re-query GitHub after a merge.

Does fleet status work without the GitHub CLI or network access?

Yes. Without an authenticated gh CLI the digest prints 'PRs: gh unavailable' and everything else still works. The --offline flag skips GitHub entirely, and missing git only empties the repo section.

Can fleet status merge PRs or kill idle sessions automatically?

No. The skill is strictly read-only and never merges, closes, kills sessions, or deletes branches on its own. It offers two or three concrete next actions as questions and waits for the user to pick one.

Why does the digest say 'Scheduled: not tracked' for routines?

Scheduled routines live server-side and the collector script cannot enumerate them. A live session can call CronList to append the count, but the script itself always reports them as not tracked rather than zero.