Create and converge FLEET.md registries mapping sibling repository checkouts, groups, and ports.
npx skills add https://github.com/ai-hero/hero-skills --skill fleet-ai-hero
Please help me install this Agent Skill. Skill: fleet Source: https://github.com/ai-hero/hero-skills/tree/main/skills/fleet Command: npx skills add https://github.com/ai-hero/hero-skills --skill fleet-ai-hero
sync mode scans a folder of git checkouts, proposes rows (name, group, port, description), and writes FLEET.md only after user confirmation. - Read-only drift review: The review mode reports findings such as unlisted checkouts, missing repos, port mismatches, and port collisions without writing anything. - Fleet-aware fan-out: Sends the ## Fleet section to each member repo as an inbox message so each repo lands the change in its own PR. - Use Case: You clone a new service next to your existing stack and run the sync mode to add it to FLEET.md, claim a free port from the configured range, and notify the other repos. ## Quick Start Run the fleet skill with the sync argument from the folder that holds my repository checkouts to scan them and propose a FLEET.md registry.High-intent search queries and answers about installing and using this skill.
Run the skill with the sync argument from the folder holding your checkouts. It scans for git repositories, asks for the fleet name, org, groups, and port range, then proposes rows and writes FLEET.md only after you confirm.
Run the skill with the review argument, or no argument, from the fleet folder. It compares each row's claimed port against the repo's compose file and reports PORT_MISMATCH, PORT_COLLISION, and related findings without modifying anything.
No. Sync writes only FLEET.md at the fleet root. Repo-side changes like the AGENTS.md fleet section or port fixes are sent as inbox messages so each repo lands them in its own PR under its own review gates.
The review scan reports UNLISTED for new checkouts not in FLEET.md and MISSING or NOT_GIT for rows whose folders disappeared. Sync then proposes adding or dropping those rows after asking for confirmation.
Yes, it is designed to run from the folder containing the checkouts, not inside a repo. It deliberately avoids the git root fallback so it never writes FLEET.md into a checkout by mistake.
juanibiapinaOrganize local GitHub projects by owner/repo in $WORKSPACE.
SocketDevDiff GitHub Actions settings against a canonical baseline to surface drift.
spandiosInspect failing GitHub Actions checks and logs with the gh CLI.
dotCMSLink workspace packages in monorepos using npm, yarn, pnpm, or bun workspace commands.