Agent Fleet Design
Use when adding, backing up, or driving the agent fleet.
Install
npx skills add SamueleBassoli/hermes-fleet-apps --skill agent-fleet-designgit clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coordinator/skills/agent-fleet-design ~/.claude/skills/agent-fleet-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Agent fleet design The fleet exists so one person can ship software alone: the owner throws ideas and approves plans; specialised agents own the details. The owner is the bottleneck (attention, time, maybe no dev training), so every design choice must reduce their decisions to a few gates. Creating a single profile is `hermes-agent-factory`; this skill decides WHICH profiles exist and how they hand off. ## Always-on rules - **Split by conflict, not by human job title.** A new agent is justified only by one of three conflicts: a different SOUL (builder vs judge), different tools (video renderer vs compiler), or different risk (may push to git vs writes prose). No conflict = the same agent carries several human roles (coder = frontend + backend + devops). 5-7 agents cover a small software org. - **Project state lives in the repo, not in agent memory.** Agents coordinate through project files (`SPEC.md`, `.design/`, git log), never by reading each other's profile dirs — a profile is who an agent is, not where the work stands. - **One shared `FLEET.md` next to the profiles** lists who does what, inputs/outputs, and the owner's approval gates. Each agent's memory carries ONE line pointing at it. Never copy the fleet map into every memory — N copies drift the first time an agent is added. - **Adding an agent = FLEET.md edit + pointer edits** in the SOULs that previously held the responsibility (e.g. "brand belongs to coder" → "to
Details
- Skill name
agent-fleet-design- Repository
- SamueleBassoli/hermes-fleet-apps
- Path
roles/coordinator/skills/agent-fleet-design/SKILL.md- License
- MIT
- Repo updated
- 31 October 2026
FAQ
What does the Agent Fleet Design skill do?
Use when adding, backing up, or driving the agent fleet.
How do I install the Agent Fleet Design skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill agent-fleet-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Agent Fleet Design popular?
It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.
Related skills
Agent Facing CLI
44SamueleBassoli/hermes-fleet-apps
Use when an agent will drive a CLI. Contract test first.
Agent Identity Setup
44SamueleBassoli/hermes-fleet-apps
Use when setting up or resetting agent SOUL, memory, skills.
App Project Kickoff
44SamueleBassoli/hermes-fleet-apps
Use when the owner wants an app built or an old tool rewritten.
AI Agents UI Skills
23gocallum/nextjs16-agent-skills
Comprehensive guide for building AI agents using ToolLoopAgent, workflow patterns, and AI SDK UI components (useChat, generative UIs, tool calling)
Vtex Io Masterdata Strategy
47vtex/skills
Apply when deciding whether and how VTEX IO apps should use Master Data v2 for custom data. Covers entity boundaries, schema lifecycle, indexing strategy, and when Master Data is the right storage mechanism versus another data approach. Use for reviews, wishlists, forms, or other custom data modeling decisions in VTEX IO apps.
AI SDK 6 Skills
23gocallum/nextjs16-agent-skills
AI SDK 6 Beta overview, agents, tool approval, Groq (Llama), and Vercel AI Gateway. Key breaking changes from v5 and new patterns.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.