CtrlK
BlogDocsLog inGet started
Tessl Logo

langchain-architecture

Design LLM applications using LangChain 1.x and LangGraph for agents, memory, and tool integration. Use when building LangChain applications, implementing AI agents, or creating complex LLM workflows.

83

1.66x
Quality

Does it follow best practices?

Impact

83%

1.66x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A thorough, highly actionable LangChain/LangGraph reference rich in executable code, but it is overly long and monolithic with concept recaps and un-deprecated version-sensitive claims. It lacks progressive disclosure into separate files and explicit validation feedback loops in its workflows.

Suggestions

Move time-sensitive claims (e.g. 'langchain (1.2.x)', 'Claude Sonnet 4.5 recommended', 'standard for building agents in 2026') into a dedicated 'Version notes' or deprecated section, or remove them, to improve conciseness and longevity.

Split the large inline pattern catalog (RAG, multi-agent, memory, performance) into one-level-deep reference files (e.g. PATTERNS.md, MEMORY.md, PERFORMANCE.md) linked from a concise overview in SKILL.md.

Add explicit validate→fix→retry checkpoints (e.g. verifying a compiled graph or testing a tool before proceeding) to the multi-step workflows so workflow clarity can reach 3.

DimensionReasoningScore

Conciseness

The body is a ~460-line monolith that recaps concepts Claude already knows ('LangGraph is the standard for building agents in 2026') and embeds time-sensitive version/model claims ('langchain (1.2.x)', 'Claude Sonnet 4.5 recommended') outside any deprecated section; code is mostly efficient but the overall length is padded.

2 / 3

Actionability

Provides numerous complete, copy-paste-ready, executable examples (ReAct agent, RAG StateGraph, multi-agent orchestration, memory checkpointers, callbacks, streaming, tests) with concrete imports and runnable logic.

3 / 3

Workflow Clarity

Patterns are sequenced as code and a production checklist exists, but there are no explicit validate→fix→retry feedback loops or validation checkpoints for risky operations, which the rubric caps at 2 for this kind of work.

2 / 3

Progressive Disclosure

No bundle files exist and all content is crammed inline in one large file; material that should be split out (full architecture patterns, memory management, performance tuning) is not separated into one-level-deep references, though section headers are clear.

2 / 3

Total

9

/

12

Passed

Description

100%

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 concise, well-constructed description that names concrete capabilities and provides an explicit 'Use when' trigger clause with natural keywords. It is distinct from sibling skills and uses correct third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('Design LLM applications using LangChain 1.x and LangGraph for agents, memory, and tool integration'), naming specific actions and targets rather than vague language; third-person voice is correct.

3 / 3

Completeness

Explicitly answers both what ('Design LLM applications... for agents, memory, and tool integration') and when ('Use when building LangChain applications, implementing AI agents, or creating complex LLM workflows').

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — 'LangChain applications', 'AI agents', 'LLM workflows', 'LangGraph' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (LangChain 1.x / LangGraph) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (667 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.