Analysis Orchestration

Run gatherer, critic, and synthesizer analysis roles.

Skill metadata

Source	Bundled (installed by default)
Path	skills/research/analysis-orchestration
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	research, analysis, delegation, kanban, multi-agent
Related skills	professional-research, source-critique, comparative-analysis, longform-synthesis, challenge-gate, progress-ledger

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Analysis Orchestration Skill

Split hard analysis into roles so the parent synthesizes — not a single muddled pass. Use delegate_task when available; otherwise simulate roles sequentially in one session.

When to Use

• Multi-source due diligence, contested topics, or high-stakes briefs.
• User wants “research team” / critic pass / red-team the draft.

Prerequisites

• delegate_task preferred (role=leaf workers). If missing, run roles yourself in order — still produce the three artifacts.
• Skills: professional-research, source-critique, optionally comparative-analysis / longform-synthesis / academic-literature.
• Durable multi-hour work → kanban/cron, not process-local delegation.

Roles

Role	Job	Output file (suggested)
Gatherer	Search + extract + source list	01-gather.md
Critic	Grade sources, find holes/bias	02-critique.md
Synthesizer	Final brief with citations	03-synthesis.md

Parent owns the synthesizer role (or a final merge if a child drafts it).

How to Run

With delegate_task

1. Parent writes the question + constraints to a workdir (or vibeos research run).
2. Spawn Gatherer:

delegate_task(
  goal="Gather sources for: <question>. Use professional-research. Write 01-gather.md with URLs and snippets.",
  context="<constraints>",
  role="leaf"
)

3. Spawn Critic on gatherer output (source-critique).
4. Parent synthesizes using gather + critique (do not skip critique).

Batch form (when supported): pass tasks=[gatherer, critic] only if critic does not need gatherer’s finished file; otherwise sequence them.

Without delegation

Run the three role prompts yourself; still write the three artifacts.

Artifact checklist

01-gather.md — sub-queries, source table, raw notes, extract status. Mark blocked URLs with access: blocked_by_challenge (see challenge-gate).
02-critique.md — scorecards, contradictions, what must not be claimed. Critic must not build claims on blocked_by_challenge sources.
03-synthesis.md — executive answer, evidence table, confidence, method. challenge.md — CAPTCHA / bot-wall log when any source hit a wall.

Pitfalls

• Don’t let Gatherer write the final answer — critic never sees it then.
• Don’t parallelize Critic before Gatherer finishes.
• Leaf workers cannot delegate_task — keep orchestration in the parent.
• Background delegate_task is process-local; use kanban for survival across restarts.
• On CAPTCHA/Cloudflare: load challenge-gate (L0–L4). Do not thrash browser clicks or invent page content. Prefer web_search/web_extract/MCP, then human clarify.

Verification

• All three artifacts exist (or explicit single-file merge with sections).
• Synthesis does not assert claims Critic marked D / discard.
• Confidence + method present.
• Blocked sources acknowledged; no fabricated wall content.