AgentStack
SKILL verified MIT Self-run

Result Synthesis

skill-sumitaich1998-jarvisvr-result-synthesis · by sumitaich1998

>-

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-sumitaich1998-jarvisvr-result-synthesis

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Result Synthesis? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Result Synthesis

Close the loop on an orchestration.plan: gather each agent's result, resolve conflicts, speak one answer, and make sure the holograms they spawned are arranged comfortably (not piled on top of each other).

Inputs

  • The plan_id and the per-agent results (each agent's data + the holo.spawn

objects it produced, addressed by object_id).

  • The final orchestration.agent_status{state:"done"|"failed"} for every node.

Steps

  1. Collect & order results in the order most useful to the user (usually:

what they asked first → supporting detail). Use each tool's data.speech suggestion as raw material, not verbatim.

  1. Reconcile conflicts / dedupe. If two agents answered overlapping

questions, keep the higher-confidence / more specific one.

  1. Compose one spoken reply. Stream long answers as multiple

agent.speech{final:false} and end with a single agent.speech{final:true}. Keep it conversational; don't read JSON aloud.

  1. Coordinate the layout. Prefer delegating to the stage-agent

(compose-workspace) so it decides anchoring/arrangement. For a quick gather you may emit holo.layout yourself via arrange_holograms.

  1. Mark the turn done — emit agent.thinking{stage:"done"} after the final

speech.

Output examples

Spoken synthesis (after perception + research + productivity finished):

{ "text": "That's your coffee mug. Tokyo is 18° and cloudy, and your 5-minute timer is running.",
  "final": true, "emotion": "neutral" }

Final layout via the stage compositor (arrange_hologramsholo.layout, protocol §5.10):

{ "arrangement": "arc", "anchor": "head", "spacing": 0.25,
  "objects": ["O_vision_annotation", "O_weather_orb", "O_timer"] }

Partial failure

If a node reports state:"failed", synthesize around it honestly — report what succeeded and name what didn't, without dropping the whole turn:

{ "text": "Tokyo is 18° and cloudy and your timer's set. I couldn't get a clear
  look at the desk object though — want me to try again?", "final": true }

Edge cases

  • Nothing succeeded → one apologetic agent.speech{final:true} + an optional

notify toast; do not spawn data widgets.

  • Too many holograms → ask stage-agent to run declutter-space before the

final arrangement.

  • Barge-in (client.barge_in, §5.14) arrived mid-synthesis → stop streaming

speech, keep already-spawned holograms, end the turn.

  • Streaming order → never emit final:true until every kept result is voiced.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.