Fleet Agent Inspection
Use when checking, briefing, or retiring another fleet agent.
Install
npx skills add SamueleBassoli/hermes-fleet-apps --skill fleet-agent-inspectiongit 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/fleet-agent-inspection ~/.claude/skills/fleet-agent-inspectionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fleet agent inspection
The owner runs several agents on separate profiles, each with its own context.
When they ask "what is <agent> doing on <project>?" you have no handoff and no
shared history. Reconstruct it from that profile's directory, then verify every
claim against the work product itself.
The same skill covers the other directions: **handing work to** a sibling,
**propagating a changed convention** to every agent, and **retiring** one.
**Read-only by default.** Inspecting a sibling's profile is fine; editing its
skills, memories, config or crons is not, unless the owner says so explicitly.
The exception is a standing rule that directly governs the projects that agent
works on — propagate that, and nothing else.
## Procedure
### 1. Search profile CONTENT, never filenames
```
search_files(pattern="(?i)<project>", target="content",
path="$HERMES_HOME/profiles", output_mode="files_only")
```
A project name typically appears in zero filenames and dozens of files, so a
filename search reads as "that agent never touched it" — the opposite of the
truth. Keep `cache/` out, and never grep `$HERMES_HOME` wholesale by extension:
`*.json` pulls in the model-catalogue cache (one huge line matching anything)
and `*.db` pulls in `state.db`. Name the small files you want.
### 2. Read the highest-signal artifacts
| artifact | what it gives you |
|---|---|
| `profiles/<name>/pastes/paste_*.txt` | its own handoff prompts: state, closed decisions, traps |Details
- Skill name
fleet-agent-inspection- Repository
- SamueleBassoli/hermes-fleet-apps
- Path
roles/coordinator/skills/fleet-agent-inspection/SKILL.md- License
- MIT
- Repo updated
- 31 October 2026
FAQ
What does the Fleet Agent Inspection skill do?
Use when checking, briefing, or retiring another fleet agent.
How do I install the Fleet Agent Inspection skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill fleet-agent-inspection. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fleet Agent Inspection 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 Fleet Design
44SamueleBassoli/hermes-fleet-apps
Use when adding, backing up, or driving the agent fleet.
Agent Identity Setup
44SamueleBassoli/hermes-fleet-apps
Use when setting up or resetting agent SOUL, memory, skills.
Handoff
44SamueleBassoli/hermes-fleet-apps
Use when a session must continue in a fresh agent: compact it into one copy-paste brief.
Dependency Vetting
44SamueleBassoli/hermes-fleet-apps
Use when the owner brings a model or library to adopt. Vet it.
Hermes Agent Factory
44SamueleBassoli/hermes-fleet-apps
Use when creating or cloning a Hermes agent profile.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.