CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

langchain-orchestration

Comprehensive guide for building production-grade LLM applications using LangChain's chains, agents, memory systems, RAG patterns, and advanced orchestration

Quality

61%

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/luxor-ai-integration/skills/langchain-orchestration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 content is a sprawling, mostly-executable LangChain pattern catalog that scores well on actionability but poorly on token efficiency, workflow clarity, and progressive disclosure. It functions as an inlined API reference rather than an overview that offloads detail to bundle files.

Suggestions

Split the body into one-level-deep reference files (e.g., references/chains.md, references/agents.md, references/rag.md, references/memory.md) and keep SKILL.md as a concise overview with clearly signaled links, lifting progressive_disclosure and conciseness.

Add explicit validation/verification checkpoints to any workflow involving batch or destructive operations (e.g., the batch-processing and caching sections), including a validate->fix->retry loop so workflow_clarity can exceed 3.

Fix cross-section variable gaps by either defining 'llm', 'prompt', and 'documents' once in a shared setup snippet or noting they carry over, so examples are truly copy-paste ready.

DimensionReasoningScore

Conciseness

The body is a ~1550-line monolithic catalog whose aggregate token cost is far beyond what SKILL.md should carry inline; much of it restates LangChain API usage Claude largely already knows, and large swaths (full LLM-integration, callbacks, and retrieval sections) clearly belong in separate reference files.

2 / 5

Actionability

Most sections provide concrete, copy-paste-ready executable Python (e.g., the LCEL chain, ReAct agent, and RAG chain examples), but there are minor gaps: variables like 'llm', 'documents', and 'prompt' are used before/without definition across sections, and several examples embed placeholder 'your-api-key' values.

4 / 5

Workflow Clarity

The skill is a catalog of independent patterns rather than a sequenced process, and there are no validation checkpoints anywhere; the batch-processing section in particular lacks the validate->fix->retry feedback loop the rubric requires for batch operations, which caps this dimension low.

2 / 5

Progressive Disclosure

It is a monolithic inlined reference with no bundle files; content that clearly belongs in separate files (RAG, agents, memory, integrations) is all stuffed into SKILL.md, and the sole external reference ('see EXAMPLES.md') is buried at the very end and does not exist on disk.

2 / 5

Total

10

/

20

Passed

Description

66%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.

The description is specific and distinct, naming LangChain and its core capability areas, but it omits any explicit 'Use when' trigger guidance, which caps its completeness. It reads as a topic catalog rather than a trigger-phrase-bearing skill description.

Suggestions

Add an explicit 'Use when ...' clause naming concrete trigger phrases (e.g., 'Use when building LangChain chains, agents, RAG pipelines, or memory systems in Python').

Include natural synonym/variations users might say (e.g., 'retrieval-augmented generation', 'LangGraph', 'LCEL') to broaden trigger-term coverage toward the anchor-5 example.

Tighten the single 'building ... using' construction into multiple concrete verbs (build, compose, orchestrate, retrieve) to lift specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Names the LangChain/LLM domain and enumerates five concrete capability areas ('chains, agents, memory systems, RAG patterns, and advanced orchestration'), which is several specific items, though the single verb 'building ... using' keeps it just short of the comprehensive-actions anchor at 5.

4 / 5

Completeness

It clearly states the 'what' (building production-grade LLM apps with the listed LangChain capabilities) but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains natural terms users would say ('LangChain', 'LLM applications', 'RAG', 'agents'), giving good keyword coverage, but misses common synonyms/variations such as 'retrieval-augmented generation' or file/concept extensions that the anchor-5 example includes.

4 / 5

Distinctiveness Conflict Risk

The LangChain-specific framing ('using LangChain's chains, agents, memory systems, RAG patterns') carves a distinct niche with minimal conflict risk, though the broad 'LLM applications' phrasing leaves minor overlap with general LLM skills.

4 / 5

Total

15

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

manutej/luxor-claude-marketplace

Path

plugins/luxor-ai-integration/skills/langchain-orchestration/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.