CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-summary

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/session-summary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is a well-structured, lean instruction-only skill: a clear 6-step workflow culminating in a copy-paste-ready summary template, with sensible fallbacks for missing Langfuse tools and hollow sessions. Its main weaknesses are the vague Langfuse logging step (no named tools or parameter mapping) and a small amount of soft guidance that could be trimmed.

Suggestions

Concretize step 5 by naming the Langfuse MCP tools to use (e.g., create_trace / create_score) and how each summary section maps to trace metadata, observations, and scored metrics, with a short example payload.

Trim soft guidance such as "Process improvements for next time" and the redundant quality-score commentary, and consider moving the output template to references/template.md to slim SKILL.md further.

DimensionReasoningScore

Conciseness

The body is directive throughout with no explanations of concepts Claude already knows; bullets like "Approximate session length based on message count and complexity" instruct rather than pad. Minor soft spots — "Process improvements for next time" and the calibration commentary in "Important" — could be trimmed, placing it just below the 'every token earns its place' anchor.

4 / 5

Actionability

The full markdown template (Session Summary block with Actions table, Decisions, Errors, Metrics, Quality Score, Tags) is copy-paste ready and steps 1-4 give concrete extraction guidance. The gap is step 5's "Use the appropriate Langfuse tracing tool to send" — no tool names, parameter mapping, or example invocation is given, so it is 'mostly executable' rather than fully so.

4 / 5

Workflow Clarity

A clear 6-step sequence includes conditional fallbacks ("If Langfuse tools are not available, output the summary for the user to log manually") and an edge-case guard ("If the session was a quick question/answer... say so instead of generating a hollow summary"), which function as checkpoints. Minor validation gap: no step verifies the Langfuse log succeeded or the summary is complete; this is a generation task, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Single self-contained file with no bundle directories and no references; sections (Steps, Important) are well-organized and nothing is buried. At ~80 body lines it exceeds the under-50-line exception that would allow an automatic 5, and the ~35-line output template is the kind of content that could arguably live in a references/ file, leaving minor organization headroom.

4 / 5

Total

16

/

20

Passed

Description

53%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 states what the skill does and anchors it to a specific platform (Langfuse), giving it reasonable distinctiveness. Its main weakness is the complete absence of 'when to use' trigger guidance and sparse natural trigger phrases, which caps both completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to summarize or recap a session, log session metrics to Langfuse, or review what happened in a conversation.'

Include natural trigger variations users would actually say — 'summarize this session', 'session recap', 'log this session to Langfuse' — rather than only the platform-adjacent terms 'tracing' and 'observability'.

Make the enumerated outputs more concrete (e.g., 'actions taken, errors and resolutions, quality scores, and tags') instead of the generic 'capture what happened, decisions made, and metrics'.

DimensionReasoningScore

Specificity

"Generate a session summary" names the domain and main action, and "capture what happened, decisions made, and metrics" enumerates deliverables, but those components are category-level abstractions rather than concrete operations, and coverage omits the errors, quality scores, and tags the skill actually produces. It sits between the anchor-3 example ('names domain and 1-2 concrete actions, but not comprehensive') and anchor 4, closer to 3 due to the vague 'what happened' phrasing.

3 / 5

Completeness

The 'what' is clear — generate a session summary for Langfuse tracing capturing decisions and metrics — but there is no 'Use when...' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3 ('clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

"session summary" and "Langfuse" are natural terms a user would plausibly say, matching 'some relevant keywords but missing common variations or synonyms'. Common phrasings like 'summarize this session', 'recap the conversation', or 'log this to Langfuse' are absent, keeping it below anchor 4.

3 / 5

Distinctiveness Conflict Risk

"session summary for Langfuse tracing" and "for observability" carve out a fairly specific niche with a named platform, so overlap risk is limited to closely related generic summarization/reflection skills. Not anchor 5 since the trigger phrasing is not distinct enough to fully separate it from other summary-style skills.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

skills/session-summary/SKILL.md

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.