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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 identifies a specific tool (Langfuse), concrete actions (install, configure SDK auth, initialize tracing), explicit 'Use when' guidance, and natural trigger phrases. It uses proper third-person voice throughout and is concise without being vague. The narrow focus on a named product makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Install and configure Langfuse SDK authentication', 'configuring API keys', 'initializing Langfuse tracing'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (install and configure Langfuse SDK authentication for LLM observability) and 'when' (setting up a new Langfuse integration, configuring API keys, initializing tracing) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'install langfuse', 'setup langfuse', 'langfuse auth', 'configure langfuse API key', 'langfuse tracing setup'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Langfuse' is a specific product name, and the description is narrowly scoped to SDK authentication and tracing setup. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 skill with executable code for multiple platforms and SDK versions, clear step sequencing, and useful error handling. Its main weakness is verbosity—covering three language/version combinations inline makes it longer than necessary, and some explanatory text (key descriptions, dashboard navigation) could be trimmed. The content would benefit from splitting legacy vs modern SDK paths into separate referenced files.
Suggestions
Move v3 legacy SDK initialization (Step 5) into a separate referenced file to keep the main skill focused on the recommended v4+ path.
Remove explanatory phrases like 'identifies your project' and 'grants write access -- keep secret' that Claude already understands about API key patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content like explaining what public/secret keys are ('identifies your project', 'grants write access'), step-by-step dashboard navigation Claude doesn't need, and covering three separate language/version paths when the skill could be more focused. The version comparison table and error handling table add value but contribute to length. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready across TypeScript (v4+, v3) and Python. Install commands, environment variable setup, initialization code, and verification steps are all concrete with specific package names, import paths, and working code blocks. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (install → get keys → configure env → initialize → verify) with explicit verification at the end of each SDK variant. The error handling table serves as a troubleshooting checkpoint, and the workflow logically progresses from setup to validation. | 3 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and a reference to 'langfuse-hello-world' for next steps, plus external resource links. However, the v3 legacy SDK content and the v4+ content could arguably be split into separate files rather than inlined, making the main skill leaner. The SDK version comparison table is useful but adds bulk. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 | |
- Commit
c8a915c
- 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.