CtrlK
BlogDocsLog inGet started
Tessl Logo

hindsight-recall

Search long-term memory for relevant context from past coding sessions using Hindsight MCP tools

57

Quality

64%

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 ./hindsight-integrations/cursor/skills/hindsight-recall/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 content is well-structured, concise, and clearly sequenced for a simple skill, with appropriate guardrails and a sensible escalation checkpoint. Its main weakness is actionability: it names the recall/reflect tools but never shows how to call them, so Claude would still need to discover the invocation details.

Suggestions

Add a minimal example of the recall and reflect tool invocations (arguments or expected inputs) so the guidance is executable rather than just named.

Clarify what inputs the recall tool expects (e.g., query/topic string) so Claude knows how to formulate the search.

Add a brief note on how to interpret or present reflect output when reasoning over accumulated memories.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; every section (Trigger, Workflow, Guardrails, Output) earns its place.

5 / 5

Actionability

It names concrete tools (hindsight_memories, recall, reflect, .cursor/mcp.json) but gives no executable invocation syntax, parameters, or examples, leaving the actual usage incomplete.

3 / 5

Workflow Clarity

A clear 5-step sequence includes a conditional checkpoint (use session memory first, escalate to MCP only if insufficient); the skill is non-destructive so no validation cap applies, though an error-recovery loop is absent.

4 / 5

Progressive Disclosure

This is a short (<50 line) single-purpose skill with no external references needed, organized into clear sections (Trigger, Workflow, Guardrails, Output), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

51%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 a specific MCP toolset, but it lacks an explicit 'Use when...' trigger clause and broader natural-language trigger terms. Adding when-to-use phrasing and synonyms like 'recall' or 'remember' would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks what was decided before, recalls prior context, or references past sessions.'

Broaden trigger terms with natural synonyms users actually say: 'recall', 'remember', 'prior decisions', 'previous sessions'.

Specify additional concrete actions beyond 'search', such as 'recall relevant memories' and 'reflect over accumulated context for architectural decisions'.

DimensionReasoningScore

Specificity

Names the domain ('long-term memory', 'past coding sessions') and one concrete action ('Search...for relevant context') but offers only a single verb with no broader coverage of capabilities.

3 / 5

Completeness

The 'what' is clearly stated ('Search long-term memory for relevant context') but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like 'long-term memory' and 'past coding sessions' are present, but common natural variations users would actually say (e.g., 'remember', 'recall', 'what did we decide before') are missing.

3 / 5

Distinctiveness Conflict Risk

The 'Hindsight MCP tools' framing carves a clear niche with distinct triggers, with only minor overlap risk against generic memory-recall skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vectorize-io/hindsight
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.