agent-report

Write complete background-worker handoff reports to files for orchestrator review.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill agent-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-report
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/agent-report
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill agent-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of clipped or incomplete background-worker results by requiring the full handoff to be written to a file that the orchestrator reads directly.

Core Features & Use Cases

  • File-based handoff: Stores the complete report on disk so long, tool-heavy outputs are not truncated in transit.
  • Structured report contract: Enforces a compact report format with gate, files, done, caveats, friction, tool-gap, and blocked fields.
  • Deterministic review loop: Supports agent-to-orchestrator workflows where background work, validation status, and follow-up details must be preserved exactly.
  • Use case: A builder finishes a refactor, writes the report to the agreed handoff path, and the orchestrator reads the file instead of relying on a shortened message.

Quick Start

Use the agent-report skill to write a complete handoff file for this task at the specified path and return only that file path with the gate status.

Frequently Asked Questions about agent-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent truncated agent handoffs in a multi-agent orchestration workflow?

Prevent truncated agent handoffs by requiring background workers to write full structured reports to a file on disk instead of passing shortened result strings. The orchestrator reads the file directly to preserve complete status and verification details.

What is a file-based report contract for background worker handoffs?

A file-based report contract is a strict formatting standard for agent handoffs. It requires compact fields like gate, files, done, caveats, friction, tool-gap, and blocked to ensure deterministic transfer of validation status and follow-up details.

How do I transfer structured status from a builder agent to the orchestrator?

Transfer structured status by having the builder write a complete report to an agreed handoff path on disk. The orchestrator then reads that file to retrieve exact validation status, friction details, and tool-gap drafting information for follow-up.

Does agent-report work for multi-agent workflows with playtesters and builders?

Yes, it applies to orchestrated multi-agent workflows where builders, playtesters, or other background workers must transfer structured status. It ensures complete verification details are preserved exactly for deterministic review loops.

What's the best way to format background worker reports for deterministic follow-up?

The best way is enforcing a gate-first formatting standard with concise field summaries. This structured report contract includes fields for caveats, friction, and tool-gap drafting to enable deterministic review and follow-up actions.

Why does my background worker result get clipped during agent orchestration?

Background worker results get clipped when long, tool-heavy outputs are passed as result strings in transit. Solving this requires writing the full handoff report to a file that the orchestrator reads directly instead of relying on truncated messages.