langchain-dependencies

langchain-ai/langchain-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/langchain-ai/langchain-skills --skill langchain-dependencies
0 commentsdiscussion
summary

$22

skill.md

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 below).
  • Provider integrations (model, vector store, tools) are installed separately so you only pull in what you use.

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.3.0

Framework Choice

Framework When to use Core extra package
LangGraph Need fine-grained graph control, custom workflows, loops, or branching langgraph / @langchain/langgraph
Deep Agents Want batteries-included planning, memory, file context, and skills out of the box deepagents (depends on LangGraph; installs it as a transitive dep)

Both sit on top of langchain + langchain-core + langsmith.


Core Packages

Python — always required

Package Role Min version
langchain Agents, chains, retrieval 1.0
langchain-core Base types & interfaces (peer dep) 1.0
langsmith Tracing, evaluation, datasets 0.3.0

Python — orchestration (pick one)

Package Use when Min version
langgraph Building custom graphs directly 1.0
deepagents Using the Deep Agents framework latest

Python — model providers (pick the one(s) you use)

Package Provider
langchain-openai OpenAI (GPT-4o, o3, …)
langchain-anthropic Anthropic (Claude)
langchain-google-genai Google (Gemini)
langchain-mistralai Mistral
langchain-groq Groq (fast inference)
langchain-cohere Cohere
langchain-fireworks Fireworks AI
langchain-together Together AI
langchain-huggingface Hugging Face Hub
langchain-ollama Ollama (local models)
langchain-aws AWS Bedrock
langchain-azure-ai Azure AI Foundry

Python — common tool & retrieval packages

These packages have tighter compatibility requirements — use the latest available version unless you have a specific reason not to.

Package Adds Notes
langchain-tavily Tavily web search (TavilySearch) Dedicated integration package; prefer latest
langchain-text-splitters Text chunking utilities Semver, keep current
langchain-community 1000+ integrations (fallback) NOT semver — pin to minor series
faiss-cpu FAISS vector store (local) Via langchain-community; use latest
langchain-chroma Chroma vector store Dedicated integration package; prefer latest
langchain-pinecone Pinecone vector store Dedicated integration package; prefer latest
langchain-qdrant Qdrant vector store Dedicated integration package; prefer latest
langchain-weaviate Weaviate vector store Dedicated integration package; prefer latest
langsmith[pytest] pytest plugin for LangSmith Requires langsmith >= 0.3.4

langchain-community stability note: This package is NOT on semantic versioning. Minor releases can contain breaking changes. Prefer dedicated integration packages (e.g. langchain-chroma, langchain-tavily) when they exist — they are independently versioned and more stable.

TypeScript — always required

Package Role Min version
@langchain/core Base types & interfaces (peer dep) 1.0
langchain Agents, chains, retrieval 1.0
langsmith Tracing, evaluation, datasets 0.3.0

TypeScript — orchestration (pick one)

Package Use when Min version
@langchain/langgraph Building custom graphs directly 1.0
deepagents Using the Deep Agents framework latest

TypeScript — model providers (pick the one(s) you use)

Package Provider
@langchain/openai OpenAI (GPT-4o, o3, …)
@langchain/anthropic Anthropic (Claude)
@langchain/google-genai Google (Gemini)
@langchain/mistralai Mistral
@langchain/groq Groq (fast inference)
@langchain/cohere Cohere
@langchain/aws AWS Bedrock
@langchain/azure-openai Azure OpenAI
@langchain/ollama Ollama (local models)

TypeScript — common tool & retrieval packages

Package Adds Notes
@langchain/tavily Tavily web search (TavilySearch) Dedicated integration package; prefer latest
@langchain/community Broad set of community integrations Use sparingly; prefer dedicated packages
@langchain/pinecone Pinecone vector store Dedicated integration package; prefer latest
@langchain/qdrant Qdrant vector store Dedicated integration package; prefer latest
@langchain/weaviate Weaviate vector store Dedicated integration package; prefer latest

@langchain/core must be installed explicitly in yarn workspaces and monorepos — it is a peer dependency and will not always be hoisted automatically.


Minimal Project Templates

Add your model provider, e.g.:

langchain-openai

langchain-anthropic

langchain-google-genai

</python>
</ex-langgraph-python>

<ex-langgraph-typescript>
<typescript>
Minimal package.json dependencies for a LangGraph project (provider-agnostic).
```json
{
  "dependencies": {
    "@langchain/core": "^1.0.0",
    "langchain": "^1.0.0",
    "@langchain/langgraph": "^1.0.0",
    "langsmith": "^0.3.0"
  }
}

Add your model provider, e.g.:

langchain-anthropic

langchain-openai

</python>
</ex-deepagents-python>

<ex-deepagents-typescript>
<typescript>
Minimal package.json dependencies for a Deep Agents project (provider-agnostic).
```json
{
  "dependencies": {
    "deepagents": "latest",
    "@langchain/core": "^1.0.0",
    "langchain": "^1.0.0",
    "langsmith": "^0.3.0"
  }
}

Web search

langchain-tavily # use latest; partner package, semver

Vector store — pick one:

langchain-chroma # use latest; partner package, semver

langchain-pinecone # use latest; partner package, semver

langchain-qdrant # use latest; partner package, semver

Text processing

langchain-text-splitters # use latest; semver

Your model provider:

langchain-openai / langchain-anthropic / etc.

</python>
</ex-with-tools-python>

<ex-with-tools-typescript>
<typescript>
Adding Tavily search and a vector store to a LangGraph project.
```json
{
  "dependencies": {
    "@langchain/core": "^1.0.0",
    "langchain": "^1.0.0",
    "@langchain/langgraph": "^1.0.0",
    "langsmith": "^0.3.0",
    "@langchain/tavily": "latest",
    "@langchain/pinecone": "latest"
  }
}

Versioning Policy & Upgrade Strategy

Package group Versioning Safe upgrade strategy
langchain, langchain-core Strict semver (1.0 LTS) Allow minor: >=1.0,<2.0
langgraph / @langchain/langgraph Strict semver (v1 LTS) Allow minor: >=1.0,<2.0
langsmith Strict semver Allow minor: >=0.3.0
Dedicated integration packages (e.g. langchain-tavily, langchain-chroma) Independently versioned Allow minor updates; use latest
langchain-community NOT semver Pin exact minor: >=0.4.0,<0.5.0
deepagents Follow project releases Pin to tested version in production

Breaking changes only happen in major versions (1.x → 2.x) for all semver-compliant packages. Deprecated features remain functional across the entire 1.x series with warnings.

Prefer dedicated integration packages over langchain-community. When a dedicated package exists (e.g. langchain-chroma instead of langchain-community's Chroma integration), use it — dedicated packages are independently versioned and better tested.

Community tool packages (Tavily, vector stores, etc.) should be kept at latest unless your project requires a locked environment. These packages frequently release compatibility fixes alongside LangChain/LangGraph updates.


Environment Variables

# LangSmith (always recommended for observability)
LANGSMITH_API_KEY=<your-key>
LANGSMITH_PROJECT=<project-name>   # optional, defaults to "default"

# Model provider — set the one(s) you use
OPENAI_API_KEY=<your-key>
ANTHROPIC_API_KEY=<your-key>
GOOGLE_API_KEY=<your-key>
MISTRAL_API_KEY=<your-key>
GROQ_API_KEY=<your-key>
COHERE_API_KEY=<your-key>
FIREWORKS_API_KEY=<your-key>
TOGETHER_API_KEY=<your-key>
HUGGINGFACEHUB_API_TOKEN=<your-key>

# Common tool/retrieval services
TAVILY_API_KEY=<your-key>          # for Tavily search
PINECONE_API_KEY=<your-key>        # for Pinecone

Common Mistakes

CORRECT: LangChain 1.0 LTS

langchain>=1.0,<2.0

</fix-legacy-version>

<fix-community-unpinned>
`langchain-community` can break on minor version bumps — it does not follow semver.

WRONG: allows minor-version updates that may be breaking

langchain-community>=0.4

CORRECT: pin to exact minor series

langchain-community>=0.4.0,<0.5.0

Also consider switching to the equivalent dedicated integration package if one exists (e.g. `langchain-chroma` instead of the community Chroma integration).
</fix-community-unpinned>

<fix-community-tool-outdated>
Community tool packages like `langchain-tavily` and vector store integrations release compatibility fixes alongside LangChain updates. Using an old pinned version can cause import errors or broken tool schemas.

RISKY: old pin may be incompatible with LangChain 1.0

langchain-tavily==0.0.1

BETTER: allow latest within the current major

langchain-tavily>=0.1

</fix-community-tool-outdated>

<fix-community-import-deprecated>
Many tools that used to live in `langchain-community` now have dedicated packages with updated import paths. Always prefer the dedicated package import.

```python
# WRONG — deprecated community import path
from langchain_community.tools.tavily_search import TavilySearchResults
from langchain_community.tools import WikipediaQueryRun
from langchain_community.vectorstores import Chroma
from langchain_community.vectorstores import Pinecone

# CORRECT — use dedicated package imports
from langchain_tavily import TavilySearch                  # pip: langchain-tavily (TavilySearchResults is deprecated)
from langchain_community.tools import WikipediaQueryRun  # no dedicated pkg yet
from langchain_chroma import Chroma                       # pip: langchain-chroma
from langchain_pinecone import PineconeVectorStore        # pip: langchain-pinecone

To find the current canonical import for any integration, search the integrations directory: https://python.langchain.com/docs/integrations/tools/

Each entry shows the correct package and import path. If a dedicated package exists, use it — the community path may still work but is considered legacy.

// CORRECT: always list @langchain/core explicitly { "dependencies": { "@langchain/core": "^1.0.0", "@langchain/langgraph": "^1.0.0" } }

</typescript>
</fix-core-not-installed>

<fix-python-version>
<python>
Python 3.9 and below are not supported by LangChain 1.0.
```python
# Verify before installing
import sys
assert sys.version_info >= (3, 10), "Python 3.10+ required for LangChain 1.0"
how to use langchain-dependencies

How to use langchain-dependencies on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add langchain-dependencies
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/langchain-ai/langchain-skills --skill langchain-dependencies

The skills CLI fetches langchain-dependencies from GitHub repository langchain-ai/langchain-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/langchain-dependencies

Reload or restart Cursor to activate langchain-dependencies. Access the skill through slash commands (e.g., /langchain-dependencies) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.662 reviews
  • Amina Chawla· Dec 24, 2024

    langchain-dependencies has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Meera Rao· Dec 20, 2024

    langchain-dependencies reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Amina Choi· Dec 8, 2024

    langchain-dependencies has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Meera Singh· Dec 8, 2024

    Keeps context tight: langchain-dependencies is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Amina Robinson· Nov 27, 2024

    langchain-dependencies fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Naina Ghosh· Nov 27, 2024

    Registry listing for langchain-dependencies matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Rahul Santra· Nov 19, 2024

    I recommend langchain-dependencies for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Amina Bansal· Nov 19, 2024

    Useful defaults in langchain-dependencies — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Tariq Srinivasan· Nov 15, 2024

    langchain-dependencies fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aisha Abbas· Nov 11, 2024

    langchain-dependencies is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 62

1 / 7