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 ./devflow-plugin/skills/session-summary/SKILL.md

The canonical home for this skill is session-summary in AndreJorgeLopes/devflow

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, mostly lean instruction set with a concrete, copy-paste-ready summary template, sensible conditional handling of Langfuse availability, and useful objectivity guardrails. Its main gaps are the unspecified Langfuse MCP tool calls, slightly redundant listing of summary fields, and a dangling $ARGUMENTS placeholder.

Suggestions

Name the specific Langfuse MCP tools and expected arguments for sending the trace, scored observations, and tags, so step 5 is executable rather than leaving the tool choice to inference.

Remove the dangling "$ARGUMENTS" placeholder at the end of the body — it is inert in a SKILL.md and consumes context without effect.

Trim the duplication between steps 1 and 3 and the template by having the steps reference the template fields instead of restating them, or move the 35-line template to a references/ file to keep the body under ~50 lines.

DimensionReasoningScore

Conciseness

The body is directive and free of explanations of concepts Claude already knows, but there is minor redundancy — the Goal/Outcome/Duration/Scope and quality factors from steps 1 and 3 are re-stated verbatim in the template, and a dangling "$ARGUMENTS" token sits at the end — so it is efficient with trimmable instances rather than fully lean.

4 / 5

Actionability

The full output template (actions table, decisions, errors, metrics, quality scores, tags) with a concrete session-ID format "YYYYMMDD-HHMM-<short-hash>" is copy-paste ready, and the fallback when Langfuse tools are unavailable is specified; it falls short of fully executable because "Use the appropriate Langfuse tracing tool" leaves the actual MCP tool calls for traces and scored observations unspecified.

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit conditional branch (log to Langfuse if available, otherwise output for manual logging) and guardrails like "Be objective about quality scores. A session with many retries is not a 5/5 on efficiency"; minor gaps remain — e.g., how to compute Duration from message count and how to count memories/learnings — and no explicit checkpoints are needed for this non-destructive task, so it sits just below the fully validated anchor.

4 / 5

Progressive Disclosure

Sections (Steps, Important) are well organized with all content appropriately inline, no buried or nested references, and no bundle files to navigate; it scores 4 rather than 5 because the body is roughly 80 lines with a 35-line template that could live in a references file, exceeding the under-50-line simple-skill exception that would otherwise allow a 5.

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 communicates a clear purpose in a distinct niche (Langfuse observability session summaries) but reads as a capability statement rather than a trigger description. It lacks any explicit 'when to use' guidance and only a narrow set of natural trigger terms, capping completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to summarize or recap a session, or wants session activity logged to Langfuse for observability."

Include natural trigger variations such as "session summary", "session recap", "session retrospective", and "log this session to Langfuse" so the skill surfaces for phrasings users actually say.

Mention the concrete output artifacts (structured summary with actions, decisions, errors, metrics, and quality scores) so the 'what' covers more than a single generic action.

DimensionReasoningScore

Specificity

The description names the domain ("Langfuse tracing", "observability") and the core action ("Generate a session summary") with its contents ("capture what happened, decisions made, and metrics"), but these are facets of a single action rather than several distinct capabilities, matching the anchor for 1-2 concrete actions with incomplete coverage.

3 / 5

Completeness

The 'what' is clear ("Generate a session summary for Langfuse tracing — capture what happened, decisions made, and metrics") but the 'when' is entirely absent with no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"session summary" and "Langfuse" are natural terms a user might say, but coverage stops there — missing common variations such as "summarize this session", "recap", "retrospective", or "log to Langfuse", so relevant keywords exist while synonyms and natural trigger phrases are missing.

3 / 5

Distinctiveness Conflict Risk

"Langfuse tracing" and the observability focus give the skill a clear niche with minimal conflict risk, but a generic request to summarize or recap a session could overlap with broader reflection/summarization skills, so it is mostly distinct with minor overlap risk rather than fully distinct.

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

devflow-plugin/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.