CtrlK
BlogDocsLog inGet started
Tessl Logo

retain-learning

Retain a new learning, discovery, or hard-won insight into Hindsight so it's available in future sessions.

63

Quality

73%

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/retain-learning/SKILL.md

The canonical home for this skill is retain-learning in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, concise, and highly actionable with concrete categories, fields, and a worked example; its only gap is the absence of a verification step confirming the retain call succeeded.

Suggestions

Add a brief validation step after storing, e.g. confirm the Hindsight retain tool returned success before reporting back to the user.

Trim the opening 'You need to retain a new learning into long-term memory via Hindsight.' line since it restates the description.

Optionally note how to handle a retain-tool failure (retry or surface the error) to complete the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no padded concept explanations; the only minor redundancy is the opening line restating the description's purpose.

4 / 5

Actionability

It provides concrete, copy-paste-ready guidance: six explicit categories, five exact memory fields, a named tool ('Hindsight retain tool'), and a fully worked example showing the structured output.

5 / 5

Workflow Clarity

A clear five-step sequence runs parse → classify → structure → store → confirm, with a confirmation checkpoint; it lacks an explicit check that the retain tool call succeeded, so it stops short of a 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed, and content is cleanly organized into 'Steps' and 'Example' sections, satisfying the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

61%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 the Hindsight tool, but it omits any explicit 'when to use' trigger guidance, which limits its completeness score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user learns something worth keeping for future sessions, or asks to remember/save a learning via Hindsight.'

Include a few more natural trigger synonyms users might say, such as 'save a learning', 'remember this', or 'store an insight'.

List one or two additional concrete actions (e.g. 'classify, structure, and store') to raise specificity beyond the single 'retain' verb.

DimensionReasoningScore

Specificity

It names the domain (retaining learnings into Hindsight) and one concrete action ('Retain a new learning, discovery, or hard-won insight') but offers only a single action verb rather than several distinct actions.

3 / 5

Completeness

The 'what' is clear ('retain a new learning... so it's available in future sessions') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms like 'learning', 'discovery', 'insight', 'Hindsight', and 'future sessions' are present; a few common phrasings users might say (e.g. 'save what I learned', 'remember this') are missing.

4 / 5

Distinctiveness Conflict Risk

Tying the action to the specific Hindsight tool gives it a clear niche with minimal conflict risk, though the general 'retain a learning' phrasing could faintly overlap with generic note-taking skills.

4 / 5

Total

14

/

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