Agent skill · Testing & QA

langchain-prompt-engineering

Manage LangChain 1.0 prompts like code \u2014 LangSmith prompt hub versioning,\n\ XML-tag conventions for Claude, few-shot example selection, discriminated-union\n\ extraction schemas, and A/B test wiring. Use when taking ad-hoc prompts into\nversion\ \ control, migrating prompts from f-strings to ChatPromptTemplate,\noptimizing prompts\ \ for Claude vs GPT-4o vs Gemini, or A/B testing a prompt\nchange. Trigger with\ \ \"langchain prompt hub\", \"langsmith prompts\",\n\"prompt versioning\", \"claude\ \ xml prompt\", \"few-shot example selector\",\n\"prompt engineering\".\n"

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-prompt-engineering --agent claude-code

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

Facts
Files in the skill folder: 6
SKILL.md size: 17 KB
Bundled scripts: none
Version: 2.5.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(python:*)Bash(pip:*)
Requires: Designed for Claude Code, also compatible with Codex
Path: skills/.curated/langchain-prompt-engineering/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

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

From the SKILL.md

# LangChain Prompt Engineering (Python) ## Overview A team inherits a LangChain 1.0 codebase with **47 prompt strings** embedded as f-string literals across 12 Python files. Nobody knows which version is live in production. Rollback is git-only — requires a deploy. An A/B test on a single prompt requires shipping code and running two services in parallel. A user pastes a JSON snippet containing `{

More from claude-code-plugins-plus-skills
All skills →
building-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analyticsprocessing-computer-vision-tasksProcess images using object detection, classification, and segmentation. Use when requesting…AI & Agentsvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsorchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivityrunning-clustering-algorithmsAnalyze datasets by running clustering algorithms (K-means, DBSCAN, hierarchical) to identify data…Data & Analyticspreprocessing-data-with-automated-pipelinesProcess automate data cleaning, transformation, and validation for ML tasks. Use when requesting…Data & Analytics
About this skill
What does the langchain-prompt-engineering skill do?

Manage LangChain 1.0 prompts like code \u2014 LangSmith prompt hub versioning,\n\ XML-tag conventions for Claude, few-shot example selection, discriminated-union\n\ extraction schemas, and A/B test wiring. Use when taking ad-hoc prompts into\nversion\ \ control, migrating prompts from f-strings to ChatPromptTemplate,\noptimizing prompts\ \ for Claude vs GPT-4o vs Gemini, or A/B testing a prompt\nchange. Trigger with\ \ \"langchain prompt hub\", \"langsmith prompts\",\n\"prompt versioning\", \"claude\ \ xml prompt\", \"few-shot example selector\",\n\"prompt engineering\".\n"

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-prompt-engineering --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 jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.