CtrlK
BlogDocsLog inGet started
Tessl Logo

llm-application-dev-langchain-agent

You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.

36

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/llm-application-dev-langchain-agent/SKILL.md

The canonical home for this skill is llm-application-dev-langchain-agent in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

39%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a broad reference for LangChain/LangGraph development with decent code examples, but suffers from verbosity, lack of workflow structure, and poor progressive disclosure. It reads more like a tutorial or cheat sheet than a focused skill instruction, explaining many concepts Claude already understands while missing critical validation checkpoints for production deployment workflows. The dead reference to a non-existent bundle file further weakens its utility.

Suggestions

Add explicit validation checkpoints to the workflow (e.g., 'Verify agent responds to a test query before adding memory', 'Run LangSmith trace validation before production deployment') and restructure the checklist into a sequenced workflow with dependencies.

Split the monolithic content into separate files: move RAG pipeline details, deployment patterns, and testing setup into referenced files (e.g., `resources/rag-patterns.md`, `resources/deployment.md`) and keep SKILL.md as a concise overview with navigation links.

Remove explanations of concepts Claude already knows (what ReAct agents are, what connection pooling is, what async means) and trim the best practices section to avoid restating guidance already present in the code examples.

Either create the referenced `resources/implementation-playbook.md` bundle file or remove the dead reference to it.

DimensionReasoningScore

Conciseness

The skill is noticeably verbose with significant redundancy. It explains concepts Claude already knows (what ReAct agents are, what RAG is, basic async patterns, what connection pooling is). The best practices section restates things already covered. Many sections read like a tutorial rather than a concise reference. The opening 'Use this skill when' / 'Do not use this skill when' sections are tautological.

2 / 5

Actionability

The skill provides concrete, executable Python code examples for state management, RAG pipelines, tool creation, FastAPI deployment, testing, and key patterns. Code is mostly copy-paste ready with real library imports. Minor gaps include the `$ARGUMENTS` placeholder without explanation, incomplete imports (TypedDict, Annotated not imported), and some code referencing undefined variables (e.g., `index`, `external_call`, `checkpointer`).

4 / 5

Workflow Clarity

Despite the implementation checklist at the end, there is no clear sequential workflow with validation checkpoints. The checklist is a flat list without ordering rationale or dependencies. There are no feedback loops or validation steps (e.g., 'verify the agent responds correctly before deploying'). For a skill involving production deployment and complex multi-step agent construction, the absence of validation/verification steps is a significant gap.

2 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` but no bundle files exist, making this a dead reference. The content is a monolithic wall of ~200 lines covering architecture, agent types, memory, RAG, tools, deployment, testing, patterns, and best practices all inline. Much of this content (RAG pipeline details, deployment patterns, testing setup) should be split into separate reference files. There is minimal structural navigation beyond section headers.

2 / 5

Total

10

/

20

Passed

Description

27%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is a persona statement ('You are an expert...') rather than a functional skill description. It uses first/second person framing, lacks any concrete actions or capabilities, and provides no 'when to use' guidance. The only redeeming quality is the mention of specific technologies (LangChain 0.1+, LangGraph) which provide some trigger term value.

Suggestions

Rewrite in third person with concrete actions, e.g., 'Builds LangChain agents, creates LangGraph workflows, configures tool integrations, and implements RAG pipelines using LangChain 0.1+ and LangGraph.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about LangChain, LangGraph, AI agents, chains, retrieval-augmented generation, or building conversational AI systems.'

Replace the persona framing ('You are an expert') with capability-focused language that describes what the skill does rather than what it is.

DimensionReasoningScore

Specificity

Names the domain (LangChain agent development) but provides no concrete actions. 'Production-grade AI systems' is vague and doesn't describe what the skill actually does (e.g., build agents, create chains, configure tools).

2 / 5

Completeness

There is no clear 'what does this do' beyond a vague identity statement, and there is no 'when should Claude use it' clause at all. The description reads as a persona declaration rather than a functional skill description.

1 / 5

Trigger Term Quality

Includes relevant keywords like 'LangChain', 'LangGraph', and 'agent' that users might naturally mention, but misses common variations and related terms like 'chains', 'tools', 'RAG', 'retrieval', 'prompt templates', or 'conversational AI'.

3 / 5

Distinctiveness Conflict Risk

The mention of LangChain 0.1+ and LangGraph provides some specificity, but 'AI systems' and 'agent developer' are broad enough to overlap with general coding skills or other AI framework skills.

3 / 5

Total

9

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.