CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-audit-node-decomposition

节点分解。当一个节点体积过大、或塞了多个不相关概念导致disclosure无法覆盖时使用。

67

Quality

80%

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-node-decomposition/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 delivers an actionable, well-sequenced workflow with concrete decision criteria, blacklists, and validation feedback loops appropriate to a destructive memory operation. Its main weakness is rhetorical padding that inflates the token cost without adding guidance value.

Suggestions

Trim metaphor-heavy emphasis (e.g. "多层防爆盾", "防线就等于被击穿了") into plain rules to reduce tokens while preserving the same guidance.

Add one short before/after worked example of a node being decomposed so the abstract procedure has a concrete reference.

Consolidate the 空心节点词汇黑名单 and 父节点压力测试 into the质检 checklist so all verification gates live in one scannable place.

DimensionReasoningScore

Conciseness

It assumes Claude's familiarity with the memory-audit concepts and does not re-explain basics, but the prose is padded with metaphor and emphatic flourishes ("多层防爆盾", "断崖式衰减", "防线就等于被击穿了") that could be tightened.

2 / 3

Actionability

For an instruction-only skill it gives concrete, executable guidance: named tools ("update_memory", "read_memory"), an explicit decision test for concept boundaries, and a hard blacklist of banned phrases to scan for.

3 / 3

Workflow Clarity

A clearly sequenced 5-step process culminates in a 质检 step with two explicit validation tests and a feedback loop ("必须回到步骤 4 重写"), covering the destructive node-deletion operation.

3 / 3

Progressive Disclosure

The skill is a self-contained, under-50-line body with no bundle files and well-organized sections (诊断信号, 拆分流程), which meets the simple-skill bar for full marks.

3 / 3

Total

11

/

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 the skill does and when to use it with an explicit trigger clause, and occupies a distinct niche. It is held back from a top score only by naming a single action and using fairly technical trigger phrasing.

DimensionReasoningScore

Specificity

Names a single concrete action ("节点分解") and the trigger conditions, but does not list multiple specific concrete actions the way the score-3 anchor requires.

2 / 3

Completeness

It states both what ("节点分解") and an explicit when clause ("当一个节点体积过大...时使用"), satisfying the explicit-trigger requirement that would otherwise cap completeness at 2.

3 / 3

Trigger Term Quality

Relevant trigger terms like "节点体积过大", "多个不相关概念", and "disclosure无法覆盖" are present, but they are domain jargon and lack common natural-language variations.

2 / 3

Distinctiveness Conflict Risk

The triggers are tightly scoped to the memory-audit domain (nodes, disclosure, concept overload), making it unlikely to fire for an unrelated skill.

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.