从OpenClaw核心(CEO/IG/画师)、代理部门(55+专家)及研究实验室三大名册中,发现、组建并激活专家团队。
Compose the right team for any job by drawing from three rosters of specialists. The Planner analyzes incoming work and proposes an optimal team; the Reviewer validates deliverables before sign-off.
PLANNER.md in this skill folder — follow the workflow to classify the domain and propose a teamREVIEWER.md and run the QA workflow before final deliveryTEAM-CORE.md)#The permanent OpenClaw agents. Always available, always running.
AgentRoleWorkspaceCEOLeader, orchestrator, final authority.openclaw/workspace/IGTrading specialist, market operations.openclaw/workspace-ig/ArtistImage generation, visual analysis.openclaw/workspace-artist/
TEAM-AGENCY.md)#55+ specialist agents across 9 divisions. Activated on demand from reference/agency-agents-main/.
DivisionAgentsKey SpecialistsEngineering7Frontend Developer, Backend Architect, AI Engineer, DevOpsDesign7UI Designer, UX Architect, Image Prompt EngineerMarketing8Growth Hacker, Content Creator, Social MediaProduct3Sprint Prioritizer, Trend Researcher, Feedback SynthesizerProject Management5Senior PM, Studio Producer, Experiment TrackerTesting7Evidence Collector, Reality Checker, API TesterSupport6Analytics Reporter, Finance Tracker, Legal ComplianceSpatial Computing6XR Architect, visionOS EngineerSpecialized7Agents Orchestrator, Data Analytics, LSP Engineer
TEAM-RESEARCH.md)#Autonomous experiment methodology adapted from Karpathy's autoresearch. Run iterative experiment loops on any measurable problem.
Applicable to: trading strategy optimization, image analysis pipelines, model tuning, data analysis, any domain with a measurable metric.
The real power is mixing specialists across rosters. Here are proven combinations:
text
IG (market context) + Research Lab (experiment loop) + AI Engineer (model tuning)
→ IG provides live market data and strategy parameters
→ Research Lab runs 5-min experiment iterations on backtests
→ AI Engineer tunes neural network parameters
→ Reviewer validates with evidence before deploying to live
text
Artist (image generation) + Image Prompt Engineer (prompt crafting) + Visual Storyteller (narrative)
→ Image Prompt Engineer crafts detailed, structured prompts
→ Artist generates via xAI grok-imagine-image-pro
→ Visual Storyteller evaluates narrative quality
→ Iterate until quality threshold met
text
Artist (image capture/generation) + Research Lab (analysis loop) + AI Engineer (classification)
→ Artist handles image acquisition and enhancement
→ Research Lab runs iterative analysis (feature detection, classification)
→ AI Engineer builds/tunes detection models
→ Results feed back for next iteration
text
Senior PM (scope) + Frontend Developer (build) + Evidence Collector (QA) + Reality Checker (sign-off)
→ PM breaks spec into tasks with acceptance criteria
→ Frontend Developer implements mobile-first
→ Evidence Collector screenshots and validates each task
→ Reality Checker gives final production-readiness verdict
text
CEO (orchestrate) + Engineering (build) + Design (UX) + Marketing (launch) + Testing (validate)
→ CEO activates Planner to scope the project
→ Engineering + Design work in parallel (Dev↔QA loops)
→ Marketing prepares launch materials
→ Reviewer signs off before go-live
To activate any Agency specialist, load their definition file:
text
Read the agent definition at:
reference/agency-agents-main/[division]/[agent-file].md
Then adopt that agent's:
- Identity and personality
- Core mission and rules
- Workflow process
- Success metrics
File paths follow the pattern:
reference/agency-agents-main/engineering/engineering-frontend-developer.mdreference/agency-agents-main/design/design-image-prompt-engineer.mdreference/agency-agents-main/testing/testing-evidence-collector.mdSee TEAM-AGENCY.md for the complete index with all file paths.
When passing work between specialists, use this template:
text
## Handoff
| Field | Value |
|-------|-------|
| From | [Agent Name] |
| To | [Agent Name] |
| Task | [What needs to be done] |
| Priority | [Critical / High / Medium / Low] |
## Context
- Current state: [What's been done]
- Relevant files: [File paths]
- Constraints: [Limits, requirements]
## Deliverable
- What is needed: [Specific output]
- Acceptance criteria:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
## Quality
- Evidence required: [What proof of completion looks like]
- Reviewer: [Who validates this deliverable]
For complete handoff templates (QA pass/fail, escalation, phase gates), see:
reference/agency-agents-main/strategy/coordination/handoff-templates.md
For larger projects, use the NEXUS pipeline from the Agency framework:
ModeScaleAgentsTimelineMicroSingle task/fix5-101-5 daysSprintFeature or MVP15-252-6 weeksFullComplete productAll12-24 weeks
Pipeline phases: Discover → Strategize → Scaffold → Build → Harden → Launch → Operate
Quality gates between every phase. Evidence required for all assessments.
For full NEXUS strategy: reference/agency-agents-main/strategy/nexus-strategy.md
For activation prompts: reference/agency-agents-main/strategy/coordination/agent-activation-prompts.md
For quickstart: reference/agency-agents-main/strategy/QUICKSTART.md
FileContentsSKILL.mdThis file — overview and quick startTEAM-CORE.mdCEO/IG/Artist trio — roles, routing, interactionsTEAM-AGENCY.mdAll 55+ Agency specialists indexed by divisionTEAM-RESEARCH.mdAutonomous experiment methodologyPLANNER.mdJob analysis → team proposal workflowREVIEWER.mdQA validation workflow with quality gates