CtrlK
BlogDocsLog inGet started
Tessl Logo

session-history

Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured skill body: concrete tool call and output example, clear presentation workflow, and anti-pattern/checklist guardrails against the key risk of inventing session data. The only minor gap is that validation guidance sits in a separate checklist rather than inline in the workflow steps.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section (Quick start, Why, Anti-patterns, Checklist) earns its place, matching the top anchor.

5 / 5

Actionability

Provides a concrete copy-paste tool call (`memory_sessions { "limit": 20 }`) with an exact expected-output format, plus a precise presentation spec (first 8 chars of id, project, start time, status), fully covering the common case.

5 / 5

Workflow Clarity

A clear 5-step sequence is present and a Checklist provides verification, but validation lives in a separate section rather than as an explicit inline checkpoint in the workflow, fitting the 'clear sequence, minor validation gaps' anchor rather than the 5.

4 / 5

Progressive Disclosure

A short (under 50 lines), single-purpose skill with well-organized sections and only one clearly-signaled one-level reference (`../_shared/TROUBLESHOOTING.md`), matching the simple-skill allowance for a top score.

5 / 5

Total

19

/

20

Passed

Description

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

A clear, well-triggered description that concretely states what the skill does and when to use it, written in appropriate third-person voice. The main gap is specificity: only a single action is named where a couple more framing actions (e.g., surfacing decisions, observation counts) would round out coverage.

Suggestions

Add one or two more concrete actions to the description, e.g. 'surface key decisions and observation counts per session as a reverse-chronological timeline', to lift specificity beyond a single action.

Consider a distinguishing clause like 'per project' or 'most recent first' to further separate this skill from the sibling recap/handoff/recall skills that share the same data.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Show what happened in recent past sessions ... as a clean timeline"), but lists no additional actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action score 4.

3 / 5

Completeness

Explicitly answers both what ("Show what happened ... as a clean timeline") and when ("Use when the user asks ..."), with concrete trigger phrases matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes several natural phrases users would say ("what did we do last time", "session history", "past sessions", "overview of previous work"), giving good keyword coverage; not quite comprehensive enough for a 5 since a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

The project-session-history niche is mostly distinct with concrete triggers, but the See-also siblings (recap, handoff, recall) operate on the same data, creating minor overlap risk with closely related skills.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/agentmemory
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.