agent-response

Translate json:contract agent results into user-facing summaries and prompts.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill agent-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-response
Source: https://github.com/metraton/gaia/tree/main/skills/agent-response
Command: npx skills add https://github.com/metraton/gaia --skill agent-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The orchestrator's job is translation -- turning structured agent output into clear user communication.

Core Features & Use Cases

  • Interpret json:contract status and present concise user-facing summaries.
  • Handle statuses such as COMPLETE, NEEDS_INPUT, REVIEW, BLOCKED, and IN_PROGRESS with appropriate prompts and guidance.
  • Preserve context and generate actionable next steps to drive user decisions.

Quick Start

Provide a json:contract result to this skill to generate a user-friendly, action-oriented summary and prompts.

Frequently Asked Questions about agent-response

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

FAQPage Schema
How do I convert structured agent outputs into clear user-facing messages?

To convert structured agent outputs into clear user-facing messages, process the json:contract result through an orchestrator translation step that interprets statuses and generates concise, actionable summaries to guide user decisions.

What is the best way to handle NEEDS_INPUT or BLOCKED statuses in an orchestrator workflow?

Handling NEEDS_INPUT or BLOCKED statuses in an orchestrator workflow requires interpreting the json:contract result and generating appropriate user-facing prompts that provide context and actionable next steps to resolve the blocked condition.

How do I summarize json:contract results for non-technical users?

Summarizing json:contract results for non-technical users involves preserving the original contract data for context while transforming the structured status into an action-oriented message that drives user decisions across multiple workflow steps.

Can I preserve original contract data while generating user communication from agent responses?

Yes, you can preserve original contract data while generating user communication from agent responses. The process maintains the structured json:contract context alongside the translated summary to ensure context-aware user guidance.

When do I need a translation layer for orchestrator agent workflows?

You need a translation layer for orchestrator agent workflows when agents return structured json:contract results that require interpretation, summarization, and conversion into clear user-facing messages with guided decisions for statuses like COMPLETE or REVIEW.

Does agent-response work with IN_PROGRESS and REVIEW statuses in multi-step workflows?

Yes, agent-response works with IN_PROGRESS and REVIEW statuses in multi-step workflows. It handles these json:contract statuses by generating appropriate user-facing prompts and actionable guidance to drive decisions across each workflow step.