Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
日本語の概要は準備中です。原文の説明を表示しています。
655 件 ・ 関連度順
概要と使いどころ
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Design state-of-the-art multi-agent systems, orchestration patterns, and wiring from scratch. Load when the user asks to build an agent system from scratch, design agent orchestration patterns, choose between sequential/parallel/hierarchical workflows, or define how multiple agents should collaborate. Also triggers on "agent architecture", "multi-agent wiring", "agent orchestration pattern", "how to connect these agents", "design the communication structure". Called by agent-builder for complex topologies (>4 agents or hierarchical). For process-driven agent design, use agent-builder instead.
日本語の概要は準備中です。原文の説明を表示しています。
Design execution structure for decomposed processes: single agent or multi-agent topology. Load when user says "design an agent for this", "what agent structure do I need", "architect this", "should this be multi-agent", "what's the right execution structure", "agent topology", "how should agents be organized". Takes process-decomposer output as primary input. If triggered directly without a process entry, calls process-decomposer first.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Agent-to-Agent (A2A) protocol for inter-agent communication. Use for agent discovery, agent cards, task delegation, and multi-agent orchestration. Triggers on "A2A protocol", "agent-to-agent", "agent discovery", "agent card", "multi-agent", "agent delegation", "agent communication", or when implementing spec/api/017-a2a-protocol.md.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Pyramid multi-agent orchestration for OpenClaw: routes objectives from a CEO agent down through departments, services and employees via sessions_send / sessions_spawn, collects and merges results, enforces handoff contracts, and writes the final deliverable back to the originating session.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-Agent group chat collaboration system inspired by DingTalk/Lark. Enables AI agents to chat in groups, @mention each other, assign tasks, make decisions via voting, and collaborate. Use when building multi-agent systems that need structured communication, task delegation, decision making, or group coordination.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, set up, and monitor a multi-agent video production pipeline backed by Hermes Kanban. Use when the user wants to make ANY video — narrative film, product/marketing, music video, explainer, ASCII/terminal art, abstract/generative loop, comic, 3D, real-time/installation — and the work warrants decomposition into specialized profiles (writer, designer, animator, renderer, voice, editor, etc.) coordinated through a kanban board. Performs adaptive discovery to scope the brief, designs an appropriate team for the requested style, generates the setup script that creates Hermes profiles + initial kanban task, then helps monitor execution and intervene when tasks stall or fail. Routes scenes to whichever Hermes rendering / audio / design skill fits each beat (`ascii-video`, `manim-video`, `p5js`, `comfyui`, `touchdesigner-mcp`, `blender-mcp`, `pixel-art`, `baoyu-comic`, `claude-design`, `excalidraw`, `songsee`, `heartmula`, …) plus external APIs for TTS, image-gen, and image-to-video as needed.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates multi-agent AI systems with task delegation, agent communication, shared memory, and workflow coordination. Use when users request "multi-agent system", "agent orchestration", "AI agents", "agent coordination", or "autonomous agents".
日本語の概要は準備中です。原文の説明を表示しています。
Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when: crewai, multi-agent team, agent roles, crew of agents, role-based agents.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous benchmarking of multi-agent coordination systems: experiment design, statistical analysis, human evaluation protocols, and reproducible reporting. NOT FOR ML model evaluation (use llm-evaluation-harness), A/B testing for web products, survey design, or general data science.
日本語の概要は準備中です。原文の説明を表示しています。
Epistemic logic for multi-agent perceptual systems — Kripke models, vision sets, public announcement as coordination primitive, and satisfiability-as-reconfiguration applied to agents with limited observability. From Charrier, Ouchet, Schwarzentruber's "Big Brother Logic" demonstration paper (ENS Rennes / IRISA).
日本語の概要は準備中です。原文の説明を表示しています。
Track the full Toulmin epistemic ancestry of every claim produced by a multi-agent swarm. Each agent output is tagged with an argument chain (claim / data / warrant / relationship) derived from SwarmTracer spans and LineageEdge records, so operators can zoom into any sub-claim and see precisely which agents asserted it, what triggered each assertion, and how contradictions propagated or were synthesised away. The SwarmTracer pattern — wrapping the SwarmAgentExecutor to capture spans, record messages, and build a lineage graph — is the concrete runtime substrate. Argumentative lineage lifts that graph into the Toulmin vocabulary so reasoning provenance is both machine-queryable and human-interpretable.
日本語の概要は準備中です。原文の説明を表示しています。
Build production-grade AI agents from scratch using patterns inspired by production-grade agentic systems like Claude Code. Covers two audiences — (1) workflow builders who need planner+executor pipelines, human-in-the-loop checkpoints, and multi-agent orchestration, and (2) application embedders who need HTTP/SSE APIs, multi-user session management, and React frontend integration. Use when asked to build an AI agent, create a coding assistant, embed an agent in an app, build an API agent, clone Claude Code, build a CLI agent, design an agent architecture, scaffold an agentic system, or automate a multi-step workflow. Triggers on keywords like agent builder, agent blueprint, coding assistant, CLI agent, agentic tool, claude code clone, agent scaffold, agent architecture, workflow automation, multi-agent, planner executor, SSE streaming, agent API.
日本語の概要は準備中です。原文の説明を表示しています。
複数のAIエージェントに担当範囲と完了条件を割り当て、並行作業を管理するスキル。カンバンで進捗や障害を共有し、テストとレビューを経て成果を統合します。
公開前の文章やコードを二つの独立したエージェントが同じ基準で審査し、両方の合格まで修正と再審査を繰り返し、上限を超えたら人へ判断を引き継ぐスキル。
Claude Codeで開発作業を繰り返し進める自律ループの設計を案内します。順次実行から並列作業まで、履歴の引き継ぎや品質確認、停止条件を整理します。
大きな機能開発や移行の目標を、複数回の作業に分けた実行計画にします。各工程の背景、依存関係、検証方法をまとめ、別のエージェントへの引き継ぎを支えます。
複数の Claude Code エージェントに開発作業を割り振り、個別の作業環境で並行実行しながら、依存関係・進捗・変更内容やエラーの報告を管理するスキル。
動画の企画を整理し、作風に合う専門エージェントのチームと制作環境を組むスキル。Hermesのカンバンで作業を振り分け、進捗確認や停止・失敗時の対応を支援します。
Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).
日本語の概要は準備中です。原文の説明を表示しています。