langfuse-install-auth

Install and configure Langfuse SDK authentication for LLM observability. Use when setting up a new Langfuse integration, configuring API keys, or initializing Langfuse tracing in your project. Trigger with phrases like "install langfuse", "setup langfuse", "langfuse auth", "configure langfuse API key", "langfuse tracing setup".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a clear, validated workflow, but it carries two full SDK-generation paths inline and omits any reference-file split for the comparison and error tables. Tightening the legacy path and externalizing reference material would lift conciseness and progressive disclosure.

Suggestions

Move the v3 legacy SDK instructions into a clearly marked 'Deprecated / v3' subsection or a separate reference file so version-sensitive content does not inflate the main flow.

Extract the 'SDK Version Comparison' and 'Error Handling' tables into a reference file (e.g. references/version-matrix.md) and link to it from the body to improve progressive disclosure.

Add a brief validation note to Step 3 (e.g. confirm keys are loaded before initializing the client) so the env-var step carries its own checkpoint.

Dimension	Reasoning	Score
Conciseness	Sections are mostly lean code, but the v3 legacy path is presented as a full parallel step rather than isolated in a deprecated/old-patterns section, so version-sensitive content inflates the body instead of being tightened.	2 / 3
Actionability	Every step ships executable, copy-paste-ready code and shell commands with concrete env vars and real package names, meeting the fully-executable anchor.	3 / 3
Workflow Clarity	Steps 1–6 are explicitly sequenced, with an embedded 'Verify connection' checkpoint and an error-handling table providing a feedback loop for recovery, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	No bundle files exist and the body is well-sectioned, but ~180 lines are entirely inline; the SDK version comparison and error-handling tables are candidates for one-level-deep reference files rather than living in the overview.	2 / 3
	Total	10 / 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.

The description is concise, third-person, and clearly states both capability and trigger conditions with natural keyword coverage. It is distinct and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Install and configure Langfuse SDK authentication', 'configuring API keys', 'initializing Langfuse tracing' — matching the anchor for several specific concrete actions rather than a single vague domain.	3 / 3
Completeness	Explicitly answers both what ('Install and configure Langfuse SDK authentication for LLM observability') and when ('Use when setting up a new Langfuse integration, configuring API keys, or initializing Langfuse tracing'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say — 'install langfuse', 'setup langfuse', 'langfuse auth', 'configure langfuse API key', 'langfuse tracing setup' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Langfuse SDK auth/observability) with distinct, product-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 1 day 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.