hindsight-recall

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

100%Weight 40%Scale 1-3

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

The content is a tight, well-organized instruction-only skill: concise, actionable with named tools and files, and a clearly sequenced workflow with appropriate checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean and purposeful with no padding or explanation of concepts Claude already knows; every line (Trigger, Workflow, Guardrails, Output) earns its place.	3 / 3
Actionability	Gives concrete, specific guidance for an instruction-only skill: exact tools ('recall', 'reflect'), the exact context tag '<hindsight_memories>', and the exact fallback file '.cursor/mcp.json' with clear conditional branches.	3 / 3
Workflow Clarity	A clear 5-step sequenced workflow with conditional branches and a pre-check (steps 2-3 avoid redundant tool calls); this is a simple single-purpose skill with no destructive/batch operation, so the lack of an explicit feedback loop does not cap the score.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, organized into well-signaled sections (Trigger, Workflow, Guardrails, Output); no bundle files or referenced paths exist to verify.	3 / 3
	Total	12 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 specific and clearly scoped to a distinct niche, but it states only one action and omits an explicit 'Use when...' trigger clause, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasings (e.g., 'Use when the user asks about earlier decisions, previous sessions, or past project context').

Broaden trigger terms to include natural variations users would say ('remember when', 'last time', 'earlier', 'previous session') alongside 'Hindsight MCP tools'.

Name the concrete tool actions available (e.g., 'recall' and 'reflect') so the description lists multiple specific actions rather than just 'Search'.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Search long-term memory for relevant context') and domain ('past coding sessions', 'Hindsight MCP tools'), but lists only one action rather than multiple specific actions like the body's recall/reflect distinction.	2 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 2 even though 'when' is weakly implied by 'past coding sessions'.	2 / 3
Trigger Term Quality	Includes some natural terms ('past coding sessions', 'long-term memory') but 'Hindsight MCP tools' is technical jargon users would not naturally say, and common variations like 'earlier', 'last time', or 'remember when' are missing.	2 / 3
Distinctiveness Conflict Risk	Tied to a named, specific niche ('Hindsight MCP tools', 'long-term memory', 'past coding sessions') that is unlikely to overlap with or trigger other skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: vectorize-io/hindsight
Path: hindsight-integrations/cursor/skills/hindsight-recall/SKILL.md
Commit: ed120a2

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.