Agent skill · Code Review & Quality

langchain-dependencies

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill langchain-dependencies-harmeet10000-skills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/ai-llm/langchain-dependencies-harmeet10000-skills/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<overview> The LangChain ecosystem is split into focused, independently-versioned packages. Understanding which packages you need — and their version constraints — prevents incompatibilities and keeps upgrades predictable. **Key principles:** - **LangChain 1.0 is the current LTS release.** Always start new projects on 1.0+. LangChain 0.3 is legacy maintenance-only — do not use it for new work. - **langchain-core** is the shared foundation: always install it explicitly alongside any other package. - **langchain-community** (Python only) does NOT follow semantic versioning; pin it conservatively. - **LangGraph vs Deep Agents:** choose one orchestration approach based on your use case — they are alternatives, not a required stack (see [Framework Choice](#framework-choice) below). - Provider integrations (model, vector store, tools) are installed separately so you only pull in what you use. </overview> --- ## Environment Requirements <environment-requirements> | Requirement | Python | TypeScript / Node | |-------------|--------|-------------------| | Runtime minimum | **Python 3.10+** | **Node.js 20+** | | LangChain | **1.0+ (LTS)** | **1.0+ (LTS)** | | LangSmith SDK | >= 0.3.0 | >= 0.

What's inside
Steps it walks through
  1. Environment Requirements
  2. Framework Choice
  3. Core Packages
  4. Python — always required
  5. Python — orchestration (pick one)
  6. Python — model providers (pick the one(s) you use)
  7. Python — common tool & retrieval packages
  8. TypeScript — always required
  9. TypeScript — orchestration (pick one)
  10. TypeScript — model providers (pick the one(s) you use)
  11. TypeScript — common tool & retrieval packages
  12. Minimal Project Templates
  13. Versioning Policy & Upgrade Strategy
  14. Environment Variables
Ships with 1 file
  • metadata.json
Commands it runs
LangSmith (always recommended for observability)
Model provider — set the one(s) you use
Common tool/retrieval services
Verify before installing
node --version   # must be v20.x or higher
More from claude-skill-registry
All skills →
About this skill
What does the langchain-dependencies skill do?

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill langchain-dependencies-harmeet10000-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going