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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

76%Weight 40%Scale 1-5

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

The content is highly actionable and concise, with executable workflows and well-organized sections. Its main weakness is workflow validation: the production deploy step lacks a gating checkpoint, capping workflow clarity at 3.

Suggestions

Add a validation checkpoint before the production prompt deploy in Step 4 (e.g., gate the deploy workflow on the AI quality tests passing, or assert prompts validate before create) so destructive/batch operations are guarded.

Introduce an explicit validate -> fix -> retry feedback loop for at least one fragile step (e.g., 'if connectivity check or quality tests fail, review the error table, fix, and re-run') to lift workflow clarity above the cap.

Consider moving the longer example test scripts into a referenced file under references/ so the SKILL.md overview stays lean while still providing full executable examples.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, avoiding explanations of what Langfuse, GitHub Actions, or Vitest are, with only minor ceremonial elements like the connectivity-check one-liner that could be trimmed, fitting anchor 4 rather than the perfectly lean anchor 5.	4 / 5
Actionability	It provides complete, copy-paste-ready YAML workflows and TypeScript test/deploy/regression scripts covering the common CI cases, matching the anchor 5 example of fully executable guidance.	5 / 5
Workflow Clarity	Steps 1-5 are clearly sequenced and Steps 3 and 5 include assertion/threshold checkpoints, but the production prompt-deploy workflow (Step 4) lacks a pre-deploy validation gate and there is no explicit validate-fix-retry feedback loop, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into Overview, Prerequisites, sequenced Instructions, Best Practices, Error Handling, and external Resources with no nested references, fitting anchor 4 for good structure with minor organization gaps rather than the one-level-deep-reference anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 clearly identifies a niche skill and provides explicit trigger guidance, with good keyword coverage and low conflict risk. It is held just below top marks only because the 'what' is not a comprehensive multi-action enumeration.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions ('GitHub Actions and automated testing', 'CI/CD integration') rather than vague abstractions, with only minor coverage gaps, fitting the anchor 4 example better than the 1-2-action anchor 3.	4 / 5
Completeness	Both a 'what' ('Configure Langfuse CI/CD integration with GitHub Actions and automated testing') and an explicit 'when' with concrete trigger phrases are present, but the 'what' is a single integrated sentence rather than a multi-action list, so it sits just below the anchor 5 example.	4 / 5
Trigger Term Quality	It lists several natural trigger phrases ('langfuse CI', 'langfuse GitHub Actions', 'langfuse automated tests', 'CI langfuse', 'langfuse pipeline') with good variation, though it misses a few common synonyms like 'continuous integration', placing it at anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Langfuse-specific scope and Langfuse-prefixed trigger phrases carve a clear niche with minimal overlap risk, matching the anchor 5 example of a distinct trigger set.	5 / 5
	Total	17 / 20 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: 8585d6d

Reviewed: 13 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.