session-summary

Generate a session summary for Langfuse tracing — capture what happened, decisions made, and metrics for observability.

Quality

57%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/session-summary/SKILL.md

Quality

Content

57%

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

This skill provides a well-structured template for session summaries but falls short on the core Langfuse integration — the actual tracing/logging step is vague with no concrete tool names, API calls, or payload examples. The analytical framework (steps 1-3) over-explains what Claude can infer, while the most technically specific part (step 5) under-delivers on actionable detail.

Suggestions

Add concrete Langfuse MCP tool invocations in step 5 — specify the exact tool names, parameters, and expected payload structure for logging traces and scored observations.

Trim steps 1-3 into a concise checklist rather than expanded explanations; Claude doesn't need coaching on how to analyze a conversation.

Add a validation step after Langfuse logging to confirm the trace was received (e.g., check response status or trace URL).

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but includes some unnecessary elaboration. The step-by-step breakdown of 'Review the full session' and 'Assess session quality' explains analytical concepts Claude already understands. The template itself is valuable but the surrounding instructions could be tighter.	2 / 3
Actionability	The structured summary template is concrete and useful, but the Langfuse integration guidance is vague — 'Use the appropriate Langfuse tracing tool' without specifying which tool, what API calls, or what the trace payload looks like. There's no executable code for the actual Langfuse logging step, which is the core purpose of the skill.	2 / 3
Workflow Clarity	The steps are clearly sequenced (review → catalog → assess → generate → log → present), but there are no validation checkpoints. There's no guidance on what to do if Langfuse logging fails, no verification that the trace was successfully sent, and no feedback loop for error recovery in the logging step.	2 / 3
Progressive Disclosure	For a skill with no bundle files, the content is well-organized with clear sections (Steps, Important), the template is appropriately inline since it's the core deliverable, and the reference to `/reflect-session` for deeper reflection is a clean one-level-deep pointer. The structure is easy to navigate.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 identifies a clear, distinctive niche (Langfuse session summaries for observability) which reduces conflict risk. However, it lacks an explicit 'Use when...' clause, and the actions described are somewhat vague ('what happened', 'decisions made') rather than listing concrete operations. Adding explicit trigger guidance and more specific action verbs would strengthen it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to summarize a Langfuse session, generate tracing reports, or review observability data.'

Include additional natural trigger terms users might say, such as 'trace summary', 'LLM monitoring', 'session recap', 'span analysis', or 'observability report'.

Make the actions more concrete — instead of 'capture what happened', specify operations like 'summarize trace spans, log key decision points, and aggregate latency/token metrics'.

Dimension	Reasoning	Score
Specificity	Names the domain (Langfuse tracing, session summaries) and some actions (capture what happened, decisions made, metrics), but the actions are somewhat vague — 'what happened' and 'decisions made' are not concrete, specific operations like 'extract tables' or 'fill forms'.	2 / 3
Completeness	The 'what' is addressed (generate a session summary capturing events, decisions, and metrics), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'session summary', 'Langfuse', 'tracing', 'observability', and 'metrics', which are useful trigger terms. However, it misses common variations a user might say such as 'trace', 'logging', 'span', 'LLM monitoring', or 'session recap'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Langfuse tracing' and 'session summary' together creates a very specific niche that is unlikely to conflict with other skills. This is a clearly distinct domain.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Commit: 8d872bf

Reviewed: 1 day 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.