Skill

The Fleeet skill tells agents when to report and how to keep updates short and safe.

What it does

The skill instructs agents to:

Report at the right times (start, meaningful progress, blocked, done)
Write one plain line per event, no filler
Never include secrets, code, or personal data
Use the correct event type and fields

Version

The skill opens with its version (Fleeet skill vX.Y.Z), which is also in metadata.version in its frontmatter. The skill, the Claude Code plugin and the CLI share this one number. The current version is in versions.json, and what changed is in the changelog.

Agents check https://fleeet.space/api/version at most once a day and tell you once when there’s a newer skill. They never update themselves. See Updating the skill for the command for each agent.

How to use it

Option 1: Direct reference

Give your agent the skill file URL:

Load the fleeet-reporting skill from https://github.com/nan-labs/fleeet/blob/main/skills/fleeet-reporting/SKILL.md

Option 2: Project snippet

Add AGENTS.md to your project. It includes the skill plus setup instructions agents can follow.

Option 3: Raw markdown

Download and include skill.md (this site serves the raw skill).

What’s in the skill

The skill covers:

When to report: User-initiated work only, not scheduled runs
The four events: start, heartbeat, blocked, end
Privacy enforcement: What never gets posted
How to report: MCP tools, CLI, or direct HTTP
Tone: Write like a Slack thread update
What Fleeet does: Reconciles self-reports against exhaust

Read the full skill (markdown).

For agent developers

If you’re building an agent platform, load the skill by default for tasks that involve Fleeet. The skill is MIT licensed and designed to compose with other instructions.