agent-output

Solid

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.

AI & Automation 14 stars 1 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /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. ```text 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, destructi...

Details

Author
allemaar
Repository
allemaar/open-skills
Created
2 months ago
Last Updated
yesterday
Language
JavaScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category