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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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, verified workflow, but is somewhat redundant across the v3/v4+ variants and keeps reference-style tables inline rather than splitting them into bundle files. Tightening duplication and offloading the comparison/error tables to references would lift conciseness and progressive disclosure.

Suggestions

Consolidate the v3 and v4+ initialization examples into one primary path with a brief legacy fallback, removing the restated facts in the version-comparison table.

Move the SDK Version Comparison and Error Handling tables into a reference file (e.g. references/migration.md) referenced from the body to improve progressive disclosure.

Trim the inline comments in code blocks that restate obvious steps to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but carries redundancy — full v3 and v4+ initialization examples, plus a version-comparison table and error table that restate details already shown inline. Not a 3 because the duplicated init paths and restated facts add tokens that could be tightened; not a 1 because there is no padding with concepts Claude already knows.	2 / 3
Actionability	Provides fully executable npm/pip install commands, env-var setup, and complete TypeScript/Python initialization with verification calls — copy-paste ready. Not a 2 because the code is complete rather than pseudocode or missing key details.	3 / 3
Workflow Clarity	Clear 6-step sequence with explicit verification in Steps 4, 5, and 6 ("Verify connection" / test trace) and an error-handling table for recovery guidance. Not a 2 because validation/verification checkpoints are present rather than implicit; the operation is not destructive/batch so no cap applies.	3 / 3
Progressive Disclosure	No bundle files exist, so all content sits inline in a single ~200-line file with comparison and error tables that could be split into reference files; the only "Resources" links point to external docs. Not a 3 because there is no well-signaled one-level-deep reference structure; not a 1 because the content is well-organized into clear sections rather than a monolithic wall.	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 strong: it states concrete capabilities, provides explicit natural trigger phrases, and answers both what and when without padding. It is third-person and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Install and configure Langfuse SDK authentication" with install/configure/auth/init tracing actions, matching the anchor for listing multiple specific concrete actions. Not a 2 because it goes beyond naming a domain plus a few actions.	3 / 3
Completeness	Explicitly answers both what ("Install and configure Langfuse SDK authentication") and when ("Use when setting up a new Langfuse integration..." plus "Trigger with phrases like..."). Not a 2 because the when-clause is explicit, not merely implied.	3 / 3
Trigger Term Quality	Explicit trigger phrases ("install langfuse", "setup langfuse", "langfuse auth", "configure langfuse API key", "langfuse tracing setup") are natural terms a user would say, giving good coverage. Not a 2 because it includes common variations rather than just one or two keywords.	3 / 3
Distinctiveness Conflict Risk	Langfuse-specific niche with distinct triggers ("langfuse auth", "configure langfuse API key") unlikely to fire for unrelated skills. Not a 2 because the Langfuse scope is narrow and clearly bounded rather than overlapping with general observability 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
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-install-auth/SKILL.md
Commit: b2e8c53

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.