CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

llm-application-dev-langchain-agent

Build production-grade AI agents with LangChain and LangGraph. Use when designing, implementing, or debugging a LangChain or LangGraph agent.

Quality

74%

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 ./skills/llm-application-dev-langchain-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

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

The body delivers genuinely useful, current API-specific code for LangGraph agents, but it is diluted by tautological filler sections, redundant best-practice lists, and incomplete snippets. As a monolithic 245-line file with no reference files and a checklist lacking validation checkpoints, it reads more like a compact internal reference than a well-disclosed skill.

Suggestions

Delete the tautological "Use this skill when" / "Do not use this skill when" bullets, the generic "Instructions" list, and the "Context: Build sophisticated AI agent system for: [user request]" placeholder — they restate the skill name without adding information (conciseness).

Split the body into one-level-deep reference files (e.g. references/rag.md, references/deployment.md, references/testing.md) and keep SKILL.md as a concise overview with clearly signaled links, instead of inlining ~245 lines in a single file (progressive_disclosure).

Turn the Implementation Checklist into a sequenced workflow with explicit validation checkpoints, e.g. "after building the state graph, run a smoke-test ainvoke before adding LangSmith tracing or caching" (workflow_clarity).

Fix the incomplete code: add the TypedDict/Annotated imports and a real reducer (add_messages) to the AgentState snippet, and define or remove the undefined AgentRequest, stream_response, and external_call names (actionability).

DimensionReasoningScore

Conciseness

The bulk is lean, code-dense reference material, but ~40 lines are pure filler: tautological sections like "Working on langchain/langgraph agent development expert tasks or workflows" and "The task is unrelated to langchain/langgraph agent development expert", generic instructions ("Clarify goals, constraints, and required inputs"), and a template placeholder "Build sophisticated AI agent system for: [user request]". Core Requirements, the Implementation Checklist, and Best Practices also restate each other, fitting anchor 3's "mostly efficient but could be tightened" rather than anchor 4.

3 / 5

Actionability

Most guidance is executable and API-specific (StateGraph wiring, create_react_agent, VoyageAIEmbeddings, StructuredTool.from_function, tenacity retry), matching anchor 4's "concrete code or commands with minor gaps"; it misses anchor 5 because the AgentState snippet lacks imports and uses an invalid string Annotated reducer, and the FastAPI example depends on undefined names (AgentRequest, stream_response, external_call).

4 / 5

Workflow Clarity

The Implementation Checklist provides a real build sequence (LLM → embeddings → tools → memory → graph → tracing → … → tests), but validation checkpoints are implicit at best — there is no "verify the graph runs before adding tracing" step and testing appears only as the eleventh item, fitting anchor 3's "sequence present but checkpoints missing or implicit" rather than anchor 4.

3 / 5

Progressive Disclosure

There are no bundle files or references at all: ~245 lines of material that clearly belongs in separate files (Production Deployment, RAG Pipeline, Testing & Evaluation) are fully inlined in SKILL.md, though good section headers provide structure — matching anchor 3's "some structure; content that should be separate is inline" rather than anchor 4, which requires appropriately split content with clear references.

3 / 5

Total

13

/

20

Passed

Description

78%Weight 40%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.

A strong description: it is concise, uses third person, and explicitly pairs a clear capability statement with an equally explicit "Use when" trigger clause built on natural framework keywords. Its main weakness is thin capability coverage — a single "build" action where a short list of concrete capabilities would improve specificity.

DimensionReasoningScore

Specificity

"Build production-grade AI agents with LangChain and LangGraph" names the domain plus one concrete action, but offers no broader capability coverage (memory, RAG, deployment, testing) that would justify anchor 4's "several specific actions"; it is more concrete than anchor 2's generic domain-only naming.

3 / 5

Completeness

The description explicitly answers both questions: "Build production-grade AI agents with LangChain and LangGraph" (what) and "Use when designing, implementing, or debugging a LangChain or LangGraph agent" (when), with a concrete trigger clause as explicit as the anchor-5 example; anchor 4's caveat ("when could be more explicit") does not apply.

5 / 5

Trigger Term Quality

"LangChain", "LangGraph", "agent", and "designing, implementing, or debugging" are terms users would naturally say, matching anchor 4's "good keyword coverage; a few natural terms missing"; it falls short of anchor 5 because synonyms like "multi-agent", "LLM application", "RAG", or "tool calling" are absent.

4 / 5

Distinctiveness Conflict Risk

Named frameworks create a clear niche with distinct triggers, but the broad agent-building scope (which the body extends to RAG, deployment, and observability) carries minor overlap risk with closely related skills, matching anchor 4 rather than anchor 5's "minimal conflict risk".

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/llm-application-dev-langchain-agent/SKILL.md

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.