bubbles-result-envelope

Compose machine-readable result envelopes for Bubbles agent orchestration handoffs.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-result-envelope-pkirsanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bubbles-result-envelope
Source: https://github.com/pkirsanov/bubbles/tree/main/skills/bubbles-result-envelope
Command: npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-result-envelope-pkirsanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent orchestration breaks down when agents return vague or fabricated status reports, lose track of findings between rounds, or route work to the wrong specialist. This Skill enforces a strict, machine-readable result envelope so every agent invocation ends with verifiable provenance, complete finding accounting, and correct next-owner routing. ## Core Features & Use Cases - Terminal and continuation envelopes: Emit RESULT-ENVELOPE blocks for completed or blocked work, and CONTINUATION-ENVELOPE blocks for read-only advisory surfaces like recap, status, and handoff. - Canonical outcome vocabulary: Restricts outcomes to completed_owned, completed_diagnostic, route_required, or blocked, with legacy done_with_concerns explicitly rejected for new envelopes. - Finding accounting and learning disposition: Requires every finding to appear in addressedFindings, unresolvedFindings, or observations, and records whether a run produced a captured, deferred, or not-applicable lesson. - Use Case: After a Bubbles audit agent finishes a diagnostic pass, use this Skill to emit an envelope listing unresolved findings with suggested owners so the orchestrator can route each one to the correct specialist. ## Quick Start Compose a valid Bubbles result envelope for the agent invocation that just finished, including outcome, findings, and next-owner routing.

Frequently Asked Questions about bubbles-result-envelope

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

FAQPage Schema
How do I return results from a Bubbles agent to the orchestrator?▼

Emit a RESULT-ENVELOPE block with agent name, workflow mode, spec, outcome, addressedFindings, unresolvedFindings, and evidence references. The orchestrator uses this envelope to make the next routing decision.

What outcome values are valid in a Bubbles result envelope?▼

Exactly four outcomes are valid: completed_owned for finished state-modifying work, completed_diagnostic for read-only analysis, route_required when another specialist owns the work, and blocked when a gate or dependency prevents progress. done_with_concerns is legacy read-only.

When should a diagnostic agent use completed_diagnostic instead of completed_owned?▼

Read-only agents like audit, review, regression, and security own no Definition-of-Done items, so they must emit completed_diagnostic with findings packaged for owners. Claiming completed_owned without owned DoD items is rejected by the guard.

Why is my result envelope rejected by the validator?▼

Common causes include claiming completed_owned with unchecked DoD items, setting nextRequiredOwner to bubbles.workflow instead of a specialist, using done_with_concerns as a new outcome, or claiming learning disposition captured without a resolvable lessonId.

Can a subagent dispatch the next specialist directly?▼

No. A subagent has no dispatch tool, so it must return route_required with nextRequiredOwner set to the actual specialist. The top-level runner performs the dispatch; attempting it inline silently does nothing.