协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
tools-runtimes-and-services【开发与工程】Attach Python functions, CAMEL toolkits, MCP/OpenAPI tools, runtime-backed execution, interpreters, and service routes to CAMEL agents safely.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when a task needs CAMEL agents to call tools, expose tools through services, or execute code in a controlled runtime. It covers camel.toolkits, FunctionTool, toolkit get_tools() patterns, MCPToolkit, OpenAPIToolkit, CodeExecutionToolkit, TerminalToolkit, camel.runtimes, camel.interpreters, CAMEL agent MCP service patterns, and camel.services.agent_openapi_server.
Do not use this sub-skill for provider/model credentials or model backend selection; route that to the model/provider sub-skill. Do not use it for retrieval-specific memory/RAG tools beyond high-level routing; route retrieval work to ../memory-rag-and-data/SKILL.md when available. Do not use it for multi-agent loop design except to show how the agent receives tools.
external_tools, missing extras, API credentials, MCP startup, Docker/browser/runtime availability, sandbox safety, or OpenAPI auth, read references/troubleshooting.md.from camel.agents import ChatAgent
from camel.toolkits import FunctionTool, SearchToolkit
def add(a: int, b: int) -> int:
"""Add two integers."""
return a + b
agent = ChatAgent(tools=[FunctionTool(add), *SearchToolkit().get_tools()])
from camel.toolkits import MCPToolkit
async with MCPToolkit(config_dict={"mcpServers": {"demo": {"command": "python", "args": ["server.py"]}}}) as toolkit:
agent = ChatAgent(tools=toolkit.get_tools())
Prefer pure schema inspection before live calls, treat browser/Docker/terminal/runtime tools as side-effecting, and keep secrets in environment variables or service config outside skill content. For code execution, start with internal_python or a sandboxed runtime, explicitly decide require_confirm, and never enable unsafe_mode=True for untrusted model-generated code without an external sandbox and human approval.