langchain-ai/deepagents-python-quickstart
Scaffold a minimal local Deep Agent in Python by following the official quickstart, using provider-native web search instead of Tavily. Use when the user wants to quickly build or try a Deep Agent locally.
npx skills add https://github.com/langchain-ai/langchain-skills --skill deepagents-python-quickstart
Follow the live docs — do not invent an alternate API from memory:
https://docs.langchain.com/oss/python/deepagents/quickstart
Fetch that page (Docs MCP or HTTP) and implement the research-agent shape it shows (create_deep_agent, research system prompt, invoke with a research question like “What is LangGraph?”).
Apply these on top of the quickstart (they keep setup minimal and model-agnostic):
> Which model should this agent use? Pass a provider:model string — e.g. openai:gpt-5.5, anthropic:claude-sonnet-5, google_genai:gemini-3.5-flash. Default if you're unsure: anthropic:claude-sonnet-5.
> We'll use that provider's built-in web search (no separate search API key).
deep-agent/) and do all work there — do not pollute the open project.internet_search / Tavily tool with the chosen provider's built-in web search. Look up the current tool shape on that provider's LangChain chat docs (examples as of writing — re-check if needed):| Provider | Built-in search tool |
|----------|----------------------|
| Anthropic | {"type": "web_search_20260209", "name": "web_search", "max_uses": 5} |
| OpenAI | {"type": "web_search"} |
| Google | {"google_search": {}} |
Prefer Anthropic / OpenAI / Google so provider search is available. Only secret: that provider's API key in .env (gitignored). Skip LangSmith tracing unless they ask.
deepagents (+ python-dotenv) and the provider package for their model — not tavily-python.deep-agents-core / customization / Managed Deep Agents for next steps.Take langchain-ai/deepagents-python-quickstart from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.