Skip to content

topprismdata/cultivating-ml-agent / skills/examples/multi-agent-roles

multi-agent-roles

Verified

Use when designing a multi-agent system, when a single agent has too many responsibilities, when planning complex ML pipelines, or when observing "agent attention fragmentation" symptoms. Triggers when a task involves planning + coding + review steps.

Multi-Agent Role Architecture

Context

A single agent stuffed with all system prompts + 43+ skills gets confused (attention fragmentation). agy verified that splitting into Architect / Coder / Critic / Researcher / Integrator roles reduces hallucination and improves complex pipeline stability. Inspired by AutoGen, CrewAI, and MetaGPT.

The core insight: single agent = single bottleneck; role separation enables parallel work and specialized expertise.

Guidance

Built-in Roles

from framework.src.agents import Orchestrator

orch = Orchestrator(llm_call=my_llm_function)

# 标准 ML pipeline: Architect → Coder → Critic with revision loop
pipeline = orch.create_standard_ml_pipeline()
outputs = orch.run_pipeline("standard-ml",
                             "Predict Spaceship Titanic Transported",
                             max_revisions=2)
# → Architect outputs plan → Coder writes code → Critic reviews
# → If REJECT, Architect revises with Critic feedback

Available Roles

RoleResponsibilityForbidden
data-architectPlan EDA/FE/model strategyWrite code, submit
ml-coderImplement plans as PythonModify plan, submit
continuity-criticCatch leakage/overfittingFix code, submit
knowledge-researcherFind papers + Kaggle insightsRecommend implementations

Custom Pipeline

from framework.src.agents import Pipeline

custom = (Pipeline(name="research-then-code", description="...")
          .add_step("knowledge-researcher", input_from=None, output_to="data-architect")
          .add_step("data-architect", input_from="knowledge-researcher", output_to="ml-coder")
          .add_step("ml-coder", input_from="data-architect"))

orch.register_pipeline(custom)
orch.run_pipeline("research-then-code", "Find best technique for X")

Why This Matters

Single AgentMulti-Agent
1 confused "do everything" prompt4 focused "do one thing" prompts
Hallucinates across domainsSpecializes per role
One failure breaks everythingFailure isolated per step
Hard to debugEach step traceable

agy: "Domain-Specific Multi-Agent Roles is a true trend; single-prompt generalization is limited."

When to Apply

When to Use

  • Complex ML pipeline (EDA + FE + model + submission)
  • Tasks where planning ≠ execution ≠ review
  • Building production ML agents
  • When a single agent's context has >3 distinct responsibilities

When NOT to Use

  • Simple Q&A (overkill)
  • Single-step tasks (no benefit)
  • When LLM API budget is constrained (multi-agent = more calls)

Notes

  • Mock mode for testing: Orchestrator(llm_call=None) returns echo responses for pipeline logic testing
  • Pass roles explicitly: don't reuse one role for multiple pipelines
  • Combine with Reflexion: Coder outputs run through runtime-reflexion loop
  • Revision budget: 2-3 max, more = diminishing returns + cost
  • See also: runtime-reflexion, self-evolving-skills

References

  • Implementation: framework/src/agents/
  • Inspired by: AutoGen (Microsoft), CrewAI, MetaGPT, Data Interpreter (AAAI 2025)
  • Standard pipeline: Architect → Coder → Critic (agy recommended)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall