CtrlK
BlogDocsLog inGet started
Tessl Logo

session-summary

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

56

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 content is a well-structured, actionable instruction skill with a clear sequenced workflow and a concrete output template, efficiently written without padding. It would reach the top anchor with a slightly leaner template and one or two explicit verification checkpoints.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with no padding of concepts Claude already knows; the only mild over-explanation is the 'Important' guardrail restating that retries lower efficiency, keeping it just below the 'lean, every token earns its place' anchor.

4 / 5

Actionability

It provides a concrete, copy-paste-ready structured template with exact fields and a metrics table, plus specific logging instructions; as an instruction-only skill the absence of code is not penalized, but a few fields stay abstract (<action>, <count>) which is a minor gap versus the fully-specified anchor at 5.

4 / 5

Workflow Clarity

A clear six-step sequence is present with a conditional checkpoint in step 5 (log to Langfuse if available, else output manually); since this is summary generation rather than a destructive/batch operation, no validation feedback loop is required, leaving it just short of the explicit validate/retry-loop anchor at 5.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear 'Steps' and 'Important' sections; content is appropriately kept in one file, though the ~80-line body and inline full template could arguably be split, so it sits at 'good structure, minor organization gaps' rather than 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 clearly communicates the skill's purpose and domain with a concrete, distinct niche, but it lacks any explicit trigger guidance ('Use when...') and its action list is generic rather than comprehensive. Adding a 'when to use' clause with natural user phrasing would lift both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when wrapping up a session for Langfuse observability, or when the user asks to summarize/log a session.'

Replace generic capture verbs with more specific actions (e.g. 'extracts goals, outcomes, actions, and quality metrics into a structured trace') to improve specificity.

Include common natural synonyms users might say ('session recap', 'log session to Langfuse', 'session metrics') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain (session summary for Langfuse tracing) and three concrete capture actions ('what happened, decisions made, and metrics'), but the actions are fairly generic and not comprehensive enough to reach the 'several specific actions' anchor at 4.

3 / 5

Completeness

It clearly states what the skill does ('Generate a session summary for Langfuse tracing') but provides no 'Use when...' trigger guidance, so per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

'session summary', 'Langfuse tracing', and 'observability' are relevant keywords, but common natural variations or synonyms a user might say are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Langfuse/observability tracing niche is mostly distinct with only minor overlap risk against generic summary or reflection skills, fitting the 'mostly distinct; minor overlap risk' anchor.

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