CtrlK
BlogDocsLog inGet started
Tessl Logo

langfuse-core-workflow-b

Execute Langfuse secondary workflow: Evaluation, scoring, and datasets. Use when implementing LLM evaluation, adding user feedback, or setting up automated quality scoring and experiment datasets. Trigger with phrases like "langfuse evaluation", "langfuse scoring", "rate llm outputs", "langfuse feedback", "langfuse datasets", "langfuse experiments".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-structured, highly actionable skill body built around executable TypeScript examples for the core Langfuse evaluation workflow. Its main weakness is the absence of explicit validation feedback loops and a monolithic single-file layout.

Suggestions

Add an explicit validation/retry checkpoint (e.g., verify score.create() succeeded before proceeding, or check runExperiment results for failed items and retry) to strengthen workflow clarity.

Move the bulkier reference material (full API method signatures, extended experiment-runner options) into a referenced file so SKILL.md stays a lean overview.

Trim redundant inline comments and repeated imports across the code blocks to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly lean and code-driven with little over-explanation of concepts Claude already knows; a few redundant inline comments and repeated imports could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript covering scores, feedback, prompts, datasets, the experiment runner, and LLM-as-a-judge across the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced steps plus an error-handling table give a clear flow, but there is no explicit validate→fix→retry checkpoint inside the steps, capping it just under 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections with one-level references (external docs links and companion skills) and no nested references; the ~250-line monolithic body has minor organization gaps versus a fully split structure.

4 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, third-person description that clearly states capabilities, use-when triggers, and natural keyword phrases. Minor specificity gaps keep it just short of perfect on action concreteness.

DimensionReasoningScore

Specificity

Lists several concrete actions ("implementing LLM evaluation, adding user feedback", "setting up automated quality scoring and experiment datasets") with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.

4 / 5

Completeness

Explicitly answers both what ("Execute Langfuse secondary workflow: Evaluation, scoring, and datasets") and when ("Use when implementing…") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases ("langfuse evaluation", "langfuse scoring", "rate llm outputs", "langfuse feedback", "langfuse datasets", "langfuse experiments") users would plausibly say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Langfuse evaluation/scoring niche with langfuse-prefixed triggers, keeping conflict risk with unrelated skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.