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.

60

Quality

76%

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

Quality

Content

78%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-organized, mostly lean instruction-only workflow with concrete steps and a strong worked example; its only gaps are the implicit retain-tool invocation syntax and the absence of an error-recovery loop.

Suggestions

Show the exact Hindsight 'retain' tool call (argument shape) so the store step is copy-paste ready rather than implied.

Add a brief error-recovery note for the store step (e.g., what to do if retain fails or rejects the payload).

Consider trimming the opening restatement line since the frontmatter description already conveys the task.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with only minor trimmable redundancy such as the opening line restating the task already conveyed by the description.

4 / 5

Actionability

Concrete, specific guidance with a fully worked TypeORM example covering all structured fields, but the exact invocation of the Hindsight 'retain' tool is described rather than shown.

4 / 5

Workflow Clarity

A clear five-step sequence (parse, classify, structure, store, confirm) with an edge-case branch in step 1 and a confirm checkpoint, but no error-recovery path if the store step fails.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is organized into clearly signaled 'Steps' and 'Example' sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

17

/

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 is concise and third-person, clearly naming the domain and a concrete action with good natural trigger terms, but it omits any explicit 'Use when...' clause and lists only a single action, leaving the trigger guidance implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to remember a learning, discovery, or insight for future sessions.'

List the concrete actions the skill performs (parse, classify, structure, store, confirm) to broaden specificity beyond the single 'Retain' verb.

Add common synonyms users say ("remember this", "save this insight", "note this") to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (long-term memory via Hindsight) and one concrete action ("Retain a new learning, discovery, or hard-won insight") but does not enumerate multiple distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Clearly states what the skill does ("Retain a new learning... into Hindsight so it's available in future sessions") but lacks any explicit 'Use when...' trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("learning", "discovery", "hard-won insight") with good coverage, but omits common synonyms like "remember", "save", or "note this".

4 / 5

Distinctiveness Conflict Risk

Tied to the named Hindsight system with a distinct retain-memory trigger, but could overlap slightly with other memory/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.

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.