agentleFS
allemaarallemaar/open-skills/skills/agent-output/SKILL.md

agent-output

Skill15 starsChanged 15 days agoApache-2.0View on GitHub

Compact agent-to-agent communication contract for worker reports, handoffs, status, blockers, and review findings. Trigger phrases: "/agent-output", "brief the worker", "make agent reports terse". Not a transport; use /agent-mailbox for delivery.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use stable identifiers as trailing anchors.

    line 43
  2. Distinctive:

    No greeting, praise, throat-clearing, generic summary, closing recap, or unsolicited offer.

    line 47
  3. Very specific:

    Do not repeat a fact across RESULT, EVIDENCE, and NEXT.

    line 49
  4. Distinctive:

    When assigning work, include this compact return contract in the worker brief.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/agent-output

An agent message exists to change the receiver's state. Send only information needed to decide, verify, continue, or stop.

Default report envelope

Omit empty fields. Keep each field to one compact block.

STATE: done | partial | blocked
RESULT: <verdict or completed outcome>
EVIDENCE: <exclusive proof, exact source, or check result>
CHANGED: <paths, symbols, artifacts, or none>
GAPS: <not checked, uncertainty, or none>
NEXT: <one required action or none>

For a finding, use FINDING, IMPACT, EVIDENCE, FIX, and GAPS. For a short live update, use only STATE plus the changed fact. Do not send the full envelope when two lines carry the message.

Compression rules

  • Lead with the result. Do not restate the assignment.
  • Report effects and evidence, not work chronology.
  • Name exact artifacts. Do not paste large diffs, logs, or source bodies.
  • Combine repeated findings by root cause. Preserve distinct severities.
  • State uncertainty and untested scope once, where they affect reliance.
  • Use stable identifiers as trailing anchors. Never make the receiver decode identifiers to learn the point.
  • Send one recommendation or next action. More than one only when the decisions are independent.
  • No greeting, praise, throat-clearing, generic summary, closing recap, or unsolicited offer.
  • Do not repeat a fact across RESULT, EVIDENCE, and NEXT.

Fidelity floor

Brevity never removes authority limits, stop conditions, destructive-action gates, exact numbers, scope, uncertainty, attribution, failed checks, or what was not checked. A short report that conceals a reversing caveat is invalid.

Dispatch use

When assigning work, include this compact return contract in the worker brief. The task brief still carries its own scope, authority, timeout, stop condition, test bounds, destructive limits, and verification requirements. This skill compresses the report. It does not weaken the assignment.

Boundary

  • Not /agent-mailbox. That skill transports durable messages.
  • Not /handoff. That skill builds a cold-agent context package.
  • Not /human-output. That governs Handler-facing prose. This contract is for agents who need dense operational signal.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.