CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-audit-dead-data-purge

死数据清洗。当一条记忆读不读你的行为都不会变、感悟没有现实锚点时使用。

59

Quality

67%

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 ./docs/skills/memory-audit-dead-data-purge/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 delivers a sharp, actionable judgment criterion for identifying dead data, well-organized for a simple skill. Its main weakness is the absence of validation/verification steps for a destructive purge operation, which caps workflow clarity.

Suggestions

Add an explicit validation step before deletion, e.g. re-confirm the memory has no real-world anchor and no behavioral impact with a second pass or a checklist, then delete.

Tighten the metaphorical passages ('缸中大脑', '承重墙') into concise direct guidance to improve token efficiency.

Provide a brief concrete procedure for executing the purge (locate, confirm, delete, log) so the destructive action is sequenced rather than implied.

DimensionReasoningScore

Conciseness

Mostly efficient with a clear decision test, but rhetorical flourishes ('缸中大脑的自言自语', '承重墙') pad the prose and could be trimmed; not a 4 because the metaphorical passages are non-essential.

3 / 5

Actionability

Provides a concrete, executable decision criterion ('如果答案是"不会",那这就是死数据。杀掉它。') for an instruction-only judgment skill; minor gaps in how to actually execute the purge keep it from 5.

4 / 5

Workflow Clarity

A destructive operation (deleting memories) with no validation/verification checkpoint or sequenced feedback loop, so per the destructive-cap guideline it cannot exceed 3; the single judgment criterion keeps it at rather than below 3.

3 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with no external references, organized into clear sections (intro + 判定标准 with two labeled criteria), meeting the simple-skill exception for a top score.

5 / 5

Total

15

/

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 concisely states a niche purpose and an explicit, concrete trigger condition, covering both what and when. It is slightly held back by a terse 'what' and moderate rather than exhaustive trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('死数据清洗') and a single concrete action (purge/clean dead data) but offers no broader action coverage, matching the 'names domain and 1-2 concrete actions' anchor; not a 4 because only one action is named.

3 / 5

Completeness

Both 'what' (死数据清洗) and 'when' (当...时使用) are present with a concrete trigger; the 'what' is terse and could state the action more explicitly, keeping it below 5.

4 / 5

Trigger Term Quality

The explicit '当一条记忆读不读你的行为都不会变、感悟没有现实锚点时使用' gives a natural, situational trigger a memory-maintaining user would voice; a few common synonyms/phrasings are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

'死数据清洗' with the behavioral-increment trigger carves a clear niche unlikely to fire for unrelated skills; minor overlap risk with general memory-curation skills keeps it from 5.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dataojitori/nocturne_memory
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.