CtrlK
BlogDocsLog inGet started
Tessl Logo

session-summary

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

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The content is concise, highly actionable, and presents a clear sequenced workflow with conditional handling, though the sizable inline template could be externalized for cleaner progressive disclosure.

Suggestions

Move the full summary template block into a reference file (e.g., references/summary-template.md) and link to it from a brief inline sketch.

Add a short explicit validation step that checks the generated summary against the template fields before logging to Langfuse.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, explaining no background concepts and keeping every section tied to a concrete step or output field.

3 / 3

Actionability

It provides a complete, copy-paste-ready summary template with explicit fields, a metrics checklist, a 1-5 quality scale, and concrete conditional guidance for Langfuse availability.

3 / 3

Workflow Clarity

The six steps are clearly sequenced, with a conditional checkpoint in step 5 (log to Langfuse if available, else output for manual logging) and explicit guardrails in the 'Important' section.

3 / 3

Progressive Disclosure

Sections are well-organized, but the ~80-line body inlines a large template block that could reasonably live in a separate reference file, leaving room for better content splitting.

2 / 3

Total

11

/

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 conveys the skill's purpose and domain well and is tied to a distinct Langfuse niche, but it lacks an explicit 'Use when...' trigger clause and relies on somewhat abstract action phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when ending a traced session, logging to Langfuse, or when the user asks for a session summary').

Replace abstract phrasing like 'capture what happened' with concrete actions (e.g., 'extract goal, outcome, actions, and metrics from the conversation').

Include common user-facing variations such as 'session recap', 'trace summary', or 'observability log' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('session summary for Langfuse tracing') and several actions ('capture what happened, decisions made, and metrics'), but 'what happened' is somewhat abstract rather than a list of concrete, distinct actions.

2 / 3

Completeness

It clearly states what the skill does, but the 'when' is missing — there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Relevant keywords like 'session summary', 'Langfuse tracing', and 'observability' are present, but there is no 'Use when...' phrasing and common user variations are not covered.

2 / 3

Distinctiveness Conflict Risk

Tying the summary to 'Langfuse tracing' gives it a clear niche unlikely to conflict with unrelated skills, though 'session summary' could mildly overlap with general reflection skills.

3 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AndreJorgeLopes/devflow
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.