mcpbeat

Langchain Python Quickstart

langchain-ai/langchain-python-quickstart

Scaffold a minimal local LangChain agent in Python by following the official quickstart. Use when the user wants to quickly build or try a LangChain agent locally.

369 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1080
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/langchain-ai/langchain-skills --skill langchain-python-quickstart

The instruction itself

2 sections, as written by the author

LangChain Python quickstart

Follow the live docs — do not invent an alternate API from memory:

https://docs.langchain.com/oss/python/langchain/quickstart

Fetch that page (Docs MCP or HTTP) and implement what it shows (weather agent + create_agent).

Local setup constraints

Apply these on top of the quickstart (they keep setup minimal and model-agnostic):

  • Ask which provider/model to use. Showcase that LangChain is model-agnostic. Suggested prompt:

> Which model should this agent use? Pass a provider:model string — e.g. openai:gpt-5.5, anthropic:claude-sonnet-5, google_genai:gemini-2.5-flash-lite. Default if you're unsure: anthropic:claude-sonnet-5.

Swap the quickstart's model string for their choice (or the default).

  • Create a new directory (e.g. langchain-agent/) and do all work there — do not pollute the open project.
  • Only secret: the provider API key in .env (gitignored). No LangSmith / Tavily unless they ask. Prefer they edit .env themselves — don't paste keys into chat.
  • Install the provider package needed for their model if the quickstart's base install isn't enough.
  • Run the example, show output, then stop. Point to langchain-fundamentals for next steps.

How to use it

Copy the folder

Take langchain-ai/langchain-python-quickstart from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.