langfuse-ci-integration

Configure Langfuse CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing, configuring CI pipelines, or integrating Langfuse tests into your build process. Trigger with phrases like "langfuse CI", "langfuse GitHub Actions", "langfuse automated tests", "CI langfuse", "langfuse pipeline".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/langfuse-pack/skills/langfuse-ci-integration/SKILL.md

Quality

Content

65%

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

A lean, well-organized CI integration guide with concrete code and a clear step sequence, but its actionability is undercut by SDK API names that likely don't match the real Langfuse JS SDK, and its length would benefit from splitting the inline code into bundle files.

Suggestions

Verify every Langfuse SDK call against the current JS SDK docs and replace non-standard imports/methods (e.g. '@langfuse/client' / 'LangfuseClient' / 'langfuse.runExperiment' / 'startActiveObservation') with the real 'langfuse' package API so the examples are truly copy-paste executable.

Add a validation checkpoint before the Step 4 prompt-deploy batch operation (e.g. dry-run / prompt-exists check) so the deploy workflow has an explicit validate-then-proceed gate.

Move the full workflow YAML and test/deploy scripts into files under scripts/ and references/, keeping SKILL.md as an overview that links to them one level deep, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes Claude's competence — it jumps straight into GitHub Actions YAML and test scripts with brief headers, never explaining what Langfuse, CI, or Vitest are, so every token earns its place per the level-3 anchor.	3 / 3
Actionability	Code is concrete and complete-looking (full YAML workflows, Vitest tests, deploy scripts), but several Langfuse SDK calls appear non-standard for the JS ecosystem ('@langfuse/client', 'LangfuseClient', 'langfuse.runExperiment', 'startActiveObservation'/'updateActiveObservation'), so the examples are not reliably copy-paste executable — matching the level-2 'missing key details' anchor rather than fully executable level-3.	2 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and include some verification (connectivity check, test assertions, a quality-regression check), but the prompt-deployment batch operation in Step 4 has no pre-deploy validation checkpoint, so per the rubric's batch-operation cap workflow clarity stays at 2.	2 / 3
Progressive Disclosure	The file is well-sectioned but ~240 lines with all workflow YAML and full test/deploy scripts inline and no bundle files in references/scripts/assets; large code blocks that could live in separate files are inline, matching the level-2 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that states both capability and trigger conditions with natural keyword coverage. Its only weak spot is specificity, where the listed actions are somewhat high-level restatements of the same integration task rather than multiple distinct concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and a few actions ('Configure Langfuse CI/CD integration with GitHub Actions and automated testing', 'configuring CI pipelines') but these are high-level variations of one integration task rather than multiple distinct concrete actions, matching the level-2 anchor rather than the multi-action level-3 example.	2 / 3
Completeness	It clearly answers both 'what' (Configure Langfuse CI/CD integration with GitHub Actions and automated testing) and 'when' (Use when setting up automated testing, configuring CI pipelines, or integrating Langfuse tests into your build process), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Explicit trigger phrases ('langfuse CI', 'langfuse GitHub Actions', 'langfuse automated tests', 'CI langfuse', 'langfuse pipeline') give good coverage of natural terms a user would actually say, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Langfuse-specific CI niche plus distinctive 'langfuse'-prefixed triggers make it unlikely to fire for the wrong skill, matching the clear-niche level-3 anchor.	3 / 3
	Total	11 / 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 — 13 / 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-ci-integration/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.