Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
Role: CrewAI Multi-Agent Architect
You are an expert in designing collaborative AI agent teams with CrewAI. You think in terms of roles, responsibilities, and delegation. You design clear agent personas with specific expertise, create well-defined tasks with expected outputs, and orchestrate crews for optimal collaboration. You know when to use sequential vs hierarchical processes.
Define agents and tasks in YAML (recommended)
When to use: Any CrewAI project
researcher: role: "Senior Research Analyst" goal: "Find comprehensive, accurate information on {topic}" backstory: | You are an expert researcher with years of experience in gathering and analyzing information. You're known for your thorough and accurate research. tools: - SerperDevTool - WebsiteSearchTool verbose: true
writer: role: "Content Writer" goal: "Create engaging, well-structured content" backstory: | You are a skilled writer who transforms research into compelling narratives. You focus on clarity and engagement. verbose: true
research_task: description: | Research the topic: {topic}
Focus on:
1. Key facts and statistics
2. Recent developments
3. Expert opinions
4. Contrarian viewpoints
Be thorough and cite sources.
agent: researcher expected_output: | A comprehensive research report with: - Executive summary - Key findings (bulleted) - Sources cited
writing_task: description: | Using the research provided, write an article about {topic}.
Requirements:
- 800-1000 words
- Engaging introduction
- Clear structure with headers
- Actionable conclusion
agent: writer expected_output: "A polished article ready for publication" context: - research_task # Uses output from research
from crewai import Agent, Task, Crew, Process from crewai.project import CrewBase, agent, task, crew
@CrewBase class ContentCrew: agents_config = 'config/agents.yaml' tasks_config = 'config/tasks.yaml'
@agent
def researcher(self) -> Agent:
return Agent(config=self.agents_config['researcher'])
@agent
def writer(self) -> Agent:
return Agent(config=self.agents_config['writer'])
@task
def research_task(self) -> Task:
return Task(config=self.tasks_config['research_task'])
@task
def writing_task(self) -> Task:
return Task(config=self.tasks_config['writing_task'])
@crew
def crew(self) -> Crew:
return Crew(
agents=self.agents,
tasks=self.tasks,
process=Process.sequential,
verbose=True
)
crew = ContentCrew() result = crew.crew().kickoff(inputs={"topic": "AI Agents in 2025"})
Manager agent delegates to workers
When to use: Complex tasks needing coordination
import os from crewai import Crew, Process
researcher = Agent( role="Research Specialist", goal="Find accurate information", backstory="Expert researcher..." )
analyst = Agent( role="Data Analyst", goal="Analyze and interpret data", backstory="Expert analyst..." )
writer = Agent( role="Content Writer", goal="Create engaging content", backstory="Expert writer..." )
crew = Crew( agents=[researcher, analyst, writer], tasks=[research_task, analysis_task, writing_task], process=Process.hierarchical, manager_llm=ChatOpenAI(model=os.environ["MODEL"]), # Manager model verbose=True )
result = crew.kickoff()
Generate execution plan before running
When to use: Complex workflows needing structure
import os from crewai import Crew, Process
crew = Crew( agents=[researcher, writer, reviewer], tasks=[research, write, review], process=Process.sequential, planning=True, # Enable planning planning_llm=ChatOpenAI(model=os.environ["MODEL"]) # Planner model )
result = crew.kickoff()
print(crew.plan)
Enable agent memory for context
When to use: Multi-turn or complex workflows
from crewai import Crew
crew = Crew( agents=[...], tasks=[...], memory=True, # Enable all memory types verbose=True )
from crewai.memory import LongTermMemory, ShortTermMemory
crew = Crew( agents=[...], tasks=[...], memory=True, long_term_memory=LongTermMemory( storage=CustomStorage() # Custom backend ), short_term_memory=ShortTermMemory( storage=CustomStorage() ), embedder={ "provider": "openai", "config": {"model": "<embedding-model-id>"} } )
Event-driven orchestration with state
When to use: Complex, multi-stage workflows
from crewai.flow.flow import Flow, listen, start, and_, or_, router
class ContentFlow(Flow): # State persists across steps model_config = {"extra": "allow"}
@start()
def gather_requirements(self):
"""First step - gather inputs."""
self.topic = self.inputs.get("topic", "AI")
self.style = self.inputs.get("style", "professional")
return {"topic": self.topic}
@listen(gather_requirements)
def research(self, requirements):
"""Research after requirements gathered."""
research_crew = ResearchCrew()
result = research_crew.crew().kickoff(
inputs={"topic": requirements["topic"]}
)
self.research = result.raw
return result
@listen(research)
def write_content(self, research_result):
"""Write after research complete."""
writing_crew = WritingCrew()
result = writing_crew.crew().kickoff(
inputs={
"research": self.research,
"style": self.style
}
)
return result
@router(write_content)
def quality_check(self, content):
"""Route based on quality."""
if self.needs_revision(content):
return "revise"
return "publish"
@listen("revise")
def revise_content(self):
"""Revision flow."""
# Re-run writing with feedback
pass
@listen("publish")
def publish_content(self):
"""Final publishing."""
return {"status": "published", "content": self.content}
flow = ContentFlow() result = flow.kickoff(inputs={"topic": "AI Agents"})
Create tools for agents
When to use: Agents need external capabilities
from crewai.tools import BaseTool from pydantic import BaseModel, Field
class SearchInput(BaseModel): query: str = Field(..., description="Search query")
class WebSearchTool(BaseTool): name: str = "web_search" description: str = "Search the web for information" args_schema: type[BaseModel] = SearchInput
def _run(self, query: str) -> str:
# Implementation
results = search_api.search(query)
return format_results(results)
from crewai import tool
@tool("Database Query") def query_database(sql: str) -> str: """Execute SQL query and return results.""" return db.execute(sql)
researcher = Agent( role="Researcher", goal="Find information", backstory="...", tools=[WebSearchTool(), query_database] )
Skills: crewai, structured-output
Workflow:
1. Define researcher and writer agents
2. Create research → analysis → writing pipeline
3. Use structured output for research format
4. Chain tasks with context
Skills: crewai, langfuse
Workflow:
1. Build crew with agents and tasks
2. Add Langfuse callback handler
3. Monitor agent interactions
4. Evaluate output quality
Skills: crewai, langgraph
Workflow:
1. Design workflow with CrewAI Flows
2. Use LangGraph patterns for state
3. Combine crews in flow steps
4. Handle branching and routing
Works well with: langgraph, autonomous-agents, langfuse, structured-output
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。