CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-audit-dead-data-purge

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

63

Quality

73%

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

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally concise and well-organized for a simple skill, but its destructive purge workflow is implicit and lacks explicit sequencing and validation checkpoints, while its guidance is more evaluative than concretely executable.

Suggestions

Add an explicit numbered sequence (audit → apply the behavior-change test → confirm no real-world anchor → delete) with a verification step before deletion (workflow_clarity).

Provide a concrete before/after example of one dead vs. one live memory so the purge decision is copy-paste actionable (actionability).

DimensionReasoningScore

Conciseness

Lean and dense: every sentence carries a decision criterion or discipline, with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

3 / 3

Actionability

Provides a concrete self-test question and decision rule ('如果答案是不会...杀掉它'), but guidance is mostly evaluative rather than executable; it lacks concrete checklist steps or worked examples of the level-3 anchor.

2 / 3

Workflow Clarity

The judge→decide→kill flow is present but implicit and unnumbered, and the destructive purge operation has no explicit validation/verification checkpoint, which the rubric caps at 2 for destructive operations.

2 / 3

Progressive Disclosure

A short single-purpose skill under 50 lines with no bundle files; the body is organized into a clear '判定标准' section with two well-delineated sub-points, meeting the simple-skill allowance for a 3.

3 / 3

Total

10

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 cleanly answers both 'what' and 'when' with an explicit trigger clause and a distinctive niche, but the named actions and trigger keywords are relatively abstract rather than concrete and user-natural.

Suggestions

List one or two concrete operations beyond the single 'purge' action so the capability reads as comprehensive (specificity).

Add user-natural trigger phrasing (e.g., 'reviewing stale memories', 'cleaning up memory') alongside the abstract behavioral criteria (trigger_term_quality).

DimensionReasoningScore

Specificity

Names a concrete domain (memory/insight auditing) and the headline action ('死数据清洗' / dead-data purge), but does not list multiple distinct concrete actions like the level-3 anchor does.

2 / 3

Completeness

Explicitly states what it does ('死数据清洗') and when to use it ('当一条记忆读不读你的行为都不会变、感悟没有现实锚点时使用'), matching the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Uses an explicit '当...时使用' (Use when...) trigger clause, but the trigger conditions ('行为都不会变', '没有现实锚点') are abstract rather than the natural user-facing keywords a level-3 example would cover.

2 / 3

Distinctiveness Conflict Risk

Occupies a narrow, specific niche (purging no-op memories) with distinctive triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.