CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-review

Review a project's archival_memory and propose promotions, near-duplicate merges, and stale cleanup for user approval. Read-only — applies nothing.

65

Quality

79%

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 ./skills/memory-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable and the destructive-apply workflow is exceptionally well-gated with dry-run, path verification, user confirmation, and a backup-abort feedback loop. The only weaker dimension is progressive disclosure, constrained by the absence of any bundle reference files to split content into.

DimensionReasoningScore

Conciseness

The body is efficient and largely assumes Claude's competence; the HNSW/pool-cap and Phase-1 limitation notes are project-specific and earn their place, with only minor redundancy (read-only emphasis repeated) keeping it below 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands ('uv run python scripts/core/memory_review.py <project>', 'memory_apply.py ... --ids ... --execute') with flags and concrete examples covering the common cases.

5 / 5

Workflow Clarity

Clear four-step sequence with explicit validation checkpoints for a destructive/database operation: dry-run first, verify resolved paths, confirm with user, and a pg_dump backup that aborts the apply on failure, with a feedback loop on backup failure.

5 / 5

Progressive Disclosure

No bundle files exist, so the single well-sectioned SKILL.md (Usage, numbered Process, Rules) holds all content with clearly signaled script paths; good structure with minor organization gaps rather than the ideal one-level-deep reference split.

4 / 5

Total

18

/

20

Passed

Description

70%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 is specific, distinctive, and names concrete actions in third person, but it omits an explicit 'Use when...' trigger clause, capping completeness at 3. Adding a natural-language trigger condition would lift the overall score.

Suggestions

Add an explicit 'Use when ...' clause stating when to invoke the skill, e.g. 'Use when the user wants to review, tidy, or promote project memories.'

Replace or gloss the jargon term 'archival_memory' with a natural synonym so trigger terms match how users actually phrase the request.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions ('promotions, near-duplicate merges, and stale cleanup'), giving near-comprehensive coverage with only minor elaboration gaps, fitting the score-4 anchor better than 5's broader action list.

4 / 5

Completeness

A clear 'what' is present but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('memory', 'promotions', 'merges', 'stale cleanup') that users would plausibly say, though 'archival_memory' is technical jargon and a few natural synonyms are missing, so it sits above 3 but below 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (project archival_memory review with promotions/merges/cleanup) with distinct triggers and minimal overlap with other skills, matching the score-5 anchor.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing, 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
stephenfeather/opc
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.