CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Clear due memory reviews with free recall — the two-minute habit that makes learning permanent. Use when reviews are due, or the user wants to review, practice, or "do my engram reviews".

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

An expert-grade, highly actionable review-session skill with excellent command coverage, explicit validation/feedback loops, and clean one-level-deep referencing. Its main weakness is conciseness: heavy rationale and citation asides inflate the body and could be trimmed or deferred to the referenced docs.

Suggestions

Move the behavioral-rationale and citation asides (e.g. Silverman & Barasch 2023, Deci/Koestner/Ryan 1999, the v0.8.1 durability narrative) into the referenced docs and keep SKILL.md to the operational steps and their rules.

Trim version-history parentheticals ("since v0.8.1", "v1.14 §5.6 finding") — they are time-sensitive context that does not help execute a review and penalize token efficiency.

Consider splitting the long amnesty/return-after-absence block into its own reference file (e.g. skills/_shared/amnesty.md) so the per-session flow stays scannable.

DimensionReasoningScore

Conciseness

The body is dense and mostly efficient for an expert operator, but it carries substantial rationale padding, citation asides, and version-history commentary ("since v0.8.1", "v1.14 §5.6 finding", Silverman & Barasch 2023) that competes with the operational steps and could be tightened or pushed to references.

3 / 5

Actionability

Fully executable guidance throughout: concrete bash blocks (session-start, due --cap, rate with --production-file, edit-node), exact flag usage, and copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

A clear four-step sequence (Load queue → Per item → Assessor audit → Close) with explicit validation checkpoints — "FAIL CLOSED", "Write the file first", the edit-node repair loop, error-class retry on version skew — and feedback loops for batch/destructive operations.

5 / 5

Progressive Disclosure

Structure is good and references are one level deep and clearly signaled (skills/_shared/dialogue-grammar.md, subagents.md, problem-grammar.md; docs/05-affective-layers.md, docs/16), though several large rationale blocks remain inline in SKILL.md rather than being split out, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

83%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.

A well-constructed description that clearly states capability and trigger conditions in third person, with strong natural trigger phrasing. Minor gaps in action enumeration and synonyms keep specificity and trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "Clear due memory reviews with free recall", "the two-minute habit" — but stops short of enumerating the full set of behaviors (capping, transfer probes, assessor audits), leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Clear due memory reviews with free recall — the two-minute habit that makes learning permanent") and when ("Use when reviews are due, or the user wants to review, practice, or 'do my engram reviews'") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers users would actually say ("reviews are due", "review", "practice", "do my engram reviews"), though common synonyms and the bare "spaced repetition" framing are absent.

4 / 5

Distinctiveness Conflict Risk

The "engram" niche and explicit review-due triggers make it mostly distinct from generic study skills, with only minor overlap risk against a general flashcard/review skill.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nagisanzenin/engram

Path

skills/review/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.