langchain-install-auth

Install and configure LangChain SDK with provider authentication. Use when setting up a new LangChain project, configuring API keys for OpenAI/Anthropic/Google, or initializing @langchain/core in Node.js or Python. Trigger: "install langchain", "setup langchain", "langchain auth", "configure langchain API key", "langchain credentials".

Quality

82%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

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.

This is a strong skill description that clearly defines its scope (LangChain SDK installation and configuration), specifies concrete actions, and provides explicit trigger terms. It uses proper third-person voice, includes a 'Use when' clause with specific scenarios, and is distinctive enough to avoid conflicts with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: install, configure, set up provider authentication, configure API keys for specific providers (OpenAI/Anthropic/Google), and initialize @langchain/core in Node.js or Python.	3 / 3
Completeness	Clearly answers both 'what' (install and configure LangChain SDK with provider authentication) and 'when' (explicit 'Use when' clause covering new project setup, API key configuration, and initialization scenarios, plus explicit trigger terms).	3 / 3
Trigger Term Quality	Includes excellent natural trigger terms that users would actually say: 'install langchain', 'setup langchain', 'langchain auth', 'configure langchain API key', 'langchain credentials'. Also includes provider names and language contexts (Node.js, Python).	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche focused specifically on LangChain SDK setup and authentication. The specific mention of LangChain, provider names, and setup/install context makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

64%

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

This is a solid, actionable setup skill with executable code for both TypeScript and Python ecosystems. Its main weakness is verbosity — the package architecture diagram, resources section, and some explanatory text could be trimmed or moved to separate files. The workflow is clear but lacks explicit validation checkpoints between configuration and verification steps.

Suggestions

Move the Package Architecture diagram, Error Handling table, and Troubleshooting section into a separate REFERENCE.md file, keeping SKILL.md focused on the install-configure-verify workflow.

Add an explicit validation checkpoint after Step 3 (e.g., 'Verify .env is gitignored: `grep .env .gitignore`') and add error recovery guidance in the verify steps (what to do if the connection test fails).

Remove the Prerequisites and Resources sections — Claude already knows Node.js/Python version requirements and can find documentation URLs.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary elements: the Package Architecture diagram, the Resources section with links Claude already knows, and the Prerequisites section stating obvious requirements. The error handling table and troubleshooting section add value but could be tighter.	2 / 3
Actionability	All code examples are fully executable and copy-paste ready. Install commands are specific, verification scripts are complete, and the .env setup includes concrete key prefixes and URLs. The error handling table maps specific errors to specific fixes.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced (install → configure → verify), but there's no explicit validation checkpoint after the .env creation step and no feedback loop for handling verification failures. For auth configuration involving secrets, a validation step after Step 3 (e.g., confirming .env is in .gitignore) would strengthen the workflow.	2 / 3
Progressive Disclosure	The content is reasonably structured with clear sections, but the error handling table, package architecture diagram, and troubleshooting section could be split into a separate reference file. For a setup skill, the inline content is somewhat long. The 'Next Steps' reference to langchain-hello-world is good progressive disclosure.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 4dee593

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.