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.

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a tight, well-structured instruction set with a clear workflow, concrete taxonomy and fields, and a useful worked example; it adds only what Claude would not already know and navigates cleanly despite having no bundle files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — terse category and field lists with concrete constraints ("max 10 words") and a compact worked example, with no padding or concept re-explanation.

3 / 3

Actionability

For an instruction-only skill it gives concrete, specific guidance: an explicit category taxonomy, exact memory fields with constraints, the named Hindsight `retain` tool to call, and a copy-ready example; it does not merely describe.

3 / 3

Workflow Clarity

A clear five-step sequence (Parse, Classify, Structure, Store, Confirm) with a decision branch in step 1; the task is non-destructive so no validation checkpoint is required, and the single-action flow is unambiguous.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the content is well organized into Steps and Example sections, which satisfies the simple-skill allowance for a top score without bundle files.

3 / 3

Total

12

/

12

Passed

Description

57%

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 ties it to a distinct niche (Hindsight memory retention), but lacks an explicit "Use when..." trigger and broader natural-language keyword coverage, leaving trigger guidance only implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user learns something worth remembering or wants to save an insight for future sessions."

Broaden natural trigger terms to include phrasings users actually say, such as "remember this", "save this insight", or "take note of this".

Spell out the concrete retention actions (e.g. classify, structure, store, confirm) in the description to raise specificity from a single action to multiple concrete actions.

DimensionReasoningScore

Specificity

It names the domain ("learning, discovery, or hard-won insight") and one concrete action ("Retain ... into Hindsight"), but does not list multiple specific concrete actions like the score-3 anchor requires.

2 / 3

Completeness

The "what" is clear, but there is no explicit "Use when..." trigger clause — the when is only implied ("so it's available in future sessions"), so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It includes relevant keywords a user might say ("learning", "discovery", "insight", "Hindsight") but misses common natural variations such as "remember this", "save this", or "take note", fitting the some-relevant-keywords anchor.

2 / 3

Distinctiveness Conflict Risk

The named Hindsight system and the specific memory-retention framing give it a clear niche unlikely to trigger for unrelated skills, matching the clear-niche anchor; it is not the level below because it is not merely a generic document/file skill.

3 / 3

Total

9

/

12

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.