'crewai' 검색 결과

AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en orchestration d'agents autonomes (CrewAI, AutoGen, LangGraph, swarm patterns, planning)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomous Agents Specialist IA — Expert en agents autonomes (AutoGPT, CrewAI, LangGraph, planification multi-étapes, tool use)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Agent Orchestrator IA — Expert en orchestration multi-agent (CrewAI, AutoGen, LangGraph, task decomposition, coordination)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add DeepEval tracing to Python AI applications so execution steps appear in Confident AI. Choose a supported integration or manual @observe instrumentation, then capture inputs, outputs, step types, tags, and metadata.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace execution steps in a Python AI application
• Select tracing integrations for an existing framework
• Add manual tracing with @observe

Design systems where multiple agents work with separate task information. Choose coordination structures, define handoffs and shared state, and plan parallel work while checking whether communication costs and failure risks justify using more than one agent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Split large tasks across separate agent contexts
• Run independent research tasks in parallel
• Define handoffs between specialized agents

Inspect imports and agent patterns in existing Python code to identify its framework and recommend an Omnigent executor, the component that runs the agent. Explain unsupported frameworks and suggest available next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identify the framework used by existing Python agent code
• Choose an executor for Claude SDK or OpenAI Agents SDK code
• Check whether a framework has native support

Instrument Python or TypeScript agents to record runs for Failproof AI, verify local event files, and troubleshoot missing sessions. The skill also guides building evaluator workers that score completed runs on your own infrastructure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning where an agent should record events
• Adding run logging to an existing agent
• Troubleshooting missing events or sessions

Configures and runs agents with different adapters including Claude, OpenAI, CrewAI, Lyzr, and GitHub Models. Supports local execution, remote git repos, and one-shot prompts. Use when the user wants to run an agent, switch LLM providers, configure adapter settings, or launch agents from git repositories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

交互式 AI Agent 开发工作坊：通过 6 阶段深度协作对话，引导用户完成 Agent 需求分析、架构设计、 工具定义、Prompt 与编排设计、代码生成、验证迭代，产出可直接运行的 Agent 项目。 框架无关设计优先，支持 LangChain / EINO / AutoGen / AgentScope / CrewAI 等 ADK 框架。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ADK 框架适配层。为 LangChain / EINO / AutoGen / AgentScope / CrewAI 提供框架特定的 代码模板、惯用模式、API 映射和项目结构，供 agent-dev-workshop Phase 5 代码生成使用。 每个框架 reference 文件标注 verified_date 用于版本锁定。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and deploy AI agents with CloudBase Agent SDK (TypeScript & Python). Implements the AG-UI protocol for streaming agent-UI communication. Use when deploying agent servers, using LangGraph/LangChain/CrewAI adapters, building custom adapters, understanding AG-UI protocol events, or building web/mini-program UI clients. Supports both TypeScript (@cloudbase/agent-server) and Python (cloudbase-agent-server via FastAPI).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decision protocol for the map-reduce / dynamic fan-out pattern in LM pipelines — "given list L, run f(item) for each item in parallel, then combine". Activates when the coder agent is about to process N items with N LM calls (per-doc summarize, per-query retrieve, per-candidate rank, parallel tool fan-out). Encodes the *when*, *how many at once*, *what to do when one fails*, and *how to reduce* — not the API of any single framework. Cross-framework: LangGraph `Send`, CrewAI parallel tasks / Flow, `asyncio.gather`, `ThreadPoolExecutor`, LlamaIndex batch retrieval.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tool skill — the *first move* in any LM-debugging session: dump the actual rendered prompt the framework sent to the model, before changing anything else. Activate when an LM call produced an unexpected output (wrong answer, schema violation, refusal, truncation, cost spike, latency spike, infinite loop, "model got dumber after upgrade"). The skill enforces a 30-second inspect step BEFORE any prompt edit, model swap, retry, or temperature tweak. Cross-framework cheat sheet: DSPy `inspect_history`, LangGraph `get_state_history`, CrewAI `step_callback`, LangChain `set_debug`/`set_verbose`, Aider `/diff`+`--verbose`, raw OpenAI/Anthropic via `OPENAI_LOG=debug`/`ANTHROPIC_LOG=debug` or HTTPX event hooks. Do NOT activate for first-time prompt authoring, exploratory prompt design, or non-LM bugs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decision protocol for managing the context/session state of an AI coding tool: when to /clear, when to keep context, and how to detect "context bleed" — the failure mode where stale conversation history biases the model against the current task. Surfaces a discipline that Aider (/clear), Claude Code (/clear), CrewAI (memory=False, re-instantiate), and LangGraph (new thread_id, subgraph isolation) all encode separately but none name as a skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Universal discipline for any LM-driven loop — agent retries, plan-act-observe, multi-agent handoffs, optimiser passes, test-fix cycles. Encodes the one rule every framework documents quietly and every team relearns expensively: the LM in the loop is NEVER a reliable terminator. Termination must be provided by an explicit counter + exit predicate + stagnation signal + escalation path that live OUTSIDE the LM's control. This is a tool- level, framework-agnostic skill. It maps onto LangGraph (recursion_limit + state counter + interrupt), CrewAI (max_iter + max_rpm + human_input), Claude / OpenAI SDKs (max_iterations + tool_use_budget), DSPy (declared evaluation budget), Aider (REPL + explicit retry cap), and AutoGen (max_consecutive_auto_reply). Search keywords: infinite loop, recursion limit, recursion_limit, GraphRecursionError, max iterations, max_iter, agent stuck, agent won't stop, runaway agent, ReAct loop not terminating, agent repeating itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neutral, framework-agnostic decision tree for project kickoff: "which agent / RAG / LLM framework should I reach for?" Synthesizes the ecosystem sections of 7 landmark-project SOPs (LangGraph, LlamaIndex, DSPy, CrewAI, vLLM, Aider, Dify) into one layered rubric. Core stance: frameworks are LAYERS, not competitors — a real project usually combines DSPy (compile) + LlamaIndex (retrieve) + LangGraph (orchestrate) + vLLM (serve), and you choose ONE per layer, not one to rule all. Use when starting any LLM/agent/RAG project, or whenever the "which framework?" question is asked. Deliberately neutral — unlike vendor docs and the LangChain-biased `framework-selection` on skill.sh, this skill has no horse in the race.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decision protocol for wrapping a REST / GraphQL / RPC API as a tool an LLM agent can call. The load-bearing premise: the *tool surface* is an LM-friendly subset of the *API surface* — one tool per user intent, not one per endpoint. Activates when a coder agent must expose an external HTTP API to a model (function calling, tool_use, MCP, LangChain `@tool`, CrewAI `BaseTool`). Encodes the *what to surface, how to name, how to shape, how to fail* — not any single framework's API. ~80% of agent tools in production are HTTP wrappers; this is the SOP for getting them right.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decision protocol for making side-effectful agent tools idempotent — so when an LLM tool call is retried (timeout, framework resume, user re-run, model duplicate emit), the second call is a no-op instead of a double-send. The load-bearing premise: the LM cannot promise it'll call exactly once; the tool must promise the second call is safe. Framework-agnostic — applies to LangGraph node bodies that re-run on resume, MCP tools, OpenAI tool-calling retries, CrewAI delegated tool invocations, and direct HTTP wrappers. Search keywords: duplicate email sent, charged twice, exactly-once, idempotency key, tool called twice, retry side effect, double-send, at-least-once delivery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build multi-agent AI systems for construction estimation. Use CrewAI/LangGraph to orchestrate specialized agents: QTO agent, pricing agent, validation agent. Automate complex estimation workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

E2B is a cloud platform that gives AI agents secure, isolated sandboxes — ephemeral Linux VMs with a filesystem, package managers, and internet access — to run AI-generated code safely. Use when a user wants an agent to execute Python or JavaScript, install packages, read/write files, or run a long process without risking the host machine, or wants to wire code execution into a LangChain, CrewAI, or custom agent loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AG-UI (Agent-User Interaction Protocol) is an open, event-based protocol that streams an AI agent's text, tool calls, state and lifecycle events to a frontend over HTTP and Server-Sent Events. Use when the user wants to build an AG-UI server, connect an agent or framework (LangGraph, Mastra, CrewAI, Pydantic AI) to a React or custom UI, stream agent progress and state, or use CopilotKit with AG-UI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.