CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recollect

Use when the user reaches for something past they cannot name or locate — a discussion, line of work, topic, session or settled concept — by a vague time, an existence claim without a locator, or visible recall effort; not when they give an exact reference or seek new information. Finds it in past records so the user recognizes it in a story, knowing it took place, not that it still holds.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./anamnesis/skills/recollect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 skill is rigorously and exhaustively specified — a complete flow with validation checkpoints, a well-organized one-level reference bundle, and named failure modes — but it is severely baroque: a ~530-line Lean 4 formal contract whose rules are restated in multiple sections and again in prose, at a heavy token cost with no worked example to ground the abstract directives.

Suggestions

Move the Lean contract (or a compressed version of the essential state machine) into a reference file such as references/contract.md, keeping SKILL.md as a lean operational overview that links to it.

Deduplicate the close/hold/Elsewhere rules, which are currently described in FLOW, the Reaches axiom docstring, PHASE TRANSITIONS, LOOP, CONVERGENCE, and the Rules section — state each rule once and reference it.

Add one concrete worked example (a sample vague cue → the searches run → the composed presentation round) to ground the abstract judgment axioms in executable practice.

DimensionReasoningScore

Conciseness

The ~530-line Lean block restates the same state machine in FLOW, MORPHISM, PHASE TRANSITIONS, LOOP, and CONVERGENCE, and the close/hold/elsewhere rules are described yet again in the prose Rules section — several padded, redundant sections. Not a 1 because it does not explain generic concepts Claude already knows; the padding is duplication of domain-specific material.

2 / 5

Actionability

Some concrete guidance exists (reference-loading order, named failure modes with triggers, record locations deferred to real reference files), but the core operations are judgment axioms ("**Your collection** for one pass: what the cue... gives reason to read", "**Your reading** of the cue") with no worked example of a cue, search, or presentation. Anchor 3: concrete but incomplete, missing key executable detail.

3 / 5

Workflow Clarity

The sequence (activation → cue reading → search → ground → present → identify/hold/close) is explicitly specified with checkpoints: read capture-outcome.md before qualifying, read failure-modes.md before acting on a suspected mode, scope report on an unresolved close. Not a 5 because the formal notation and heavy redundancy make the flow hard to extract and follow.

4 / 5

Progressive Disclosure

All seven referenced files (claude.md, codex.md, capture-outcome.md, supra-session.md, fork-resume.md, failure-modes.md, round-composition.md) exist, are one level deep, and are conditionally signaled in the Reference loading section. Not a 5 because the monolithic 530-line inline Lean contract keeps SKILL.md from being a lean overview that content splitting would serve.

4 / 5

Total

13

/

20

Passed

Description

66%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 and explicitly answers both when to use the skill and what it does, in third person, with well-differentiated triggers and sensible negative triggers. Its main weaknesses are an abstract, literary register and missing the natural phrasings users would actually say when struggling to recall something.

DimensionReasoningScore

Specificity

"Finds it in past records so the user recognizes it in a story" names the domain and 1-2 actions, matching anchor 3. It is not a 4 because the register stays abstract ("reaches for something past", "a settled concept") rather than listing several concrete actions.

3 / 5

Completeness

Both parts are present: an explicit "Use when the user reaches for something past they cannot name or locate..." with concrete trigger conditions and negative triggers ("not when they give an exact reference or seek new information"), plus a what ("Finds it in past records..."). Not a 5 because the 'what' is stated abstractly rather than as concrete actions.

4 / 5

Trigger Term Quality

"a discussion, line of work, topic, session", "a vague time", and "visible recall effort" are plausible user words, but common natural phrasings ("remember when", "that conversation", "we talked about") are missing and "an existence claim without a locator" is jargon. Some relevant keywords, missing common variations — anchor 3.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche — vague recall of past work in session records — with distinct positive triggers and explicit exclusions (exact references, new-information requests), so conflict with search or retrieval skills is minimal.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (605 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

jongwony/epistemic-protocols

Path

anamnesis/skills/recollect/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.