CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recall-before-task

Recall relevant memories from Hindsight before starting a task. Injects past learnings, decisions, and context into the current session.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/recall-before-task/SKILL.md

The canonical home for this skill is recall-before-task in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, well-structured instruction-only skill: it gives specific recall strategies, a named synthesis taxonomy, an exact output format, and explicit edge-case rules without padding. Its only weakness is the absence of concrete tool invocation syntax for the Hindsight tools it references.

DimensionReasoningScore

Conciseness

The body is efficient and directive ("Make multiple recall calls to cover different aspects", "Do NOT skip the recall step even if the task seems simple") with a copy-paste output template, but the opening framing line and some sub-bullets could be trimmed slightly.

4 / 5

Actionability

Concrete, specific guidance throughout: three distinct recall query strategies, four named synthesis categories (Hard Rules, Relevant Patterns, Gotchas, Related Decisions), and an exact presentation format. Minor gap: the exact Hindsight tool invocation syntax (parameters, other available tools) is not shown.

4 / 5

Workflow Clarity

Five clearly sequenced steps (parse → recall → synthesize → present → ask user) with explicit edge-case handling ("If no memories are retrieved, say so explicitly"). As a non-destructive, single-purpose skill under 50 lines with an unambiguous flow, it meets the simple-skill exception for a top score.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear "Steps" and "Important" sections; no bundle files exist, so nothing is misplaced inline. Per the simple-skill guideline, well-organized sections alone warrant a top score.

5 / 5

Total

18

/

20

Passed

Description

53%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 tool (Hindsight), giving it reasonable distinctiveness. However, it lacks an explicit "Use when..." trigger clause and natural synonyms users would actually say, capping completeness and trigger term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting any new task or when past learnings, decisions, or prior context could inform the work."

Include natural synonyms and user phrasings such as "remember", "prior context", "past sessions", or "search history" to improve trigger term coverage.

Enumerate a few more concrete actions (e.g., searching memories by topic or file path, synthesizing them into a summary) to lift specificity beyond two generic actions.

DimensionReasoningScore

Specificity

"Recall relevant memories from Hindsight" and "Injects past learnings, decisions, and context" name the domain plus two concrete actions, but coverage is not comprehensive (no mention of searching, synthesizing, or presenting memory content), matching the 1-2-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

The "what" is clear, but "before starting a task" only weakly implies when; there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "recall", "memories", "learnings", and "decisions" are relevant keywords, but common natural phrasings users would say ("remember", "prior context", "past sessions") are missing, fitting the some-keywords-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific "Hindsight" system carves a mostly distinct niche with only minor overlap risk against other memory-related skills; it lacks the explicit distinct trigger phrases needed for a 5.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

devflow-plugin/skills/recall-before-task/SKILL.md

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.