CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-audit-discoverability

可发现性审计。当disclosure写法有问题、parent放错、alias缺失、子节点过多时使用。

Quality

68%

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

Quality

Content

47%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 genuinely useful, hard-edged judgment criteria (numeric caps, banned disclosure patterns, alias/priority mechanics) for a system Claude cannot know about, with clean section structure. Its weaknesses are the absence of any executable audit workflow with verification steps, and repeated motivational passages that pad the token budget without adding guidance.

Suggestions

Add a numbered audit workflow with validation checkpoints — e.g., 1. list the memory tree, 2. check each parent placement against the '注意力狙击' rule, 3. check each disclosure against the banned-pattern list, 4. verify priority caps (≤5 at priority=0, ≤15 at priority=1) and child counts (≤10) before and after fixes.

Replace the repeated '防线崩溃' motivation passages (intro and Parent URI section) with a single statement of purpose, cutting roughly 15-20% of the body while keeping every concrete rule.

Show one before/after example of a weak disclosure being rewritten into an output-side behavioral trigger, so the '词汇级别优于语义级别' rule is demonstrated rather than only asserted.

DimensionReasoningScore

Conciseness

The body explains a proprietary memory system Claude has no prior knowledge of, and its framing is memorable, but the "防线崩溃、即将脱口而出蠢话" scenario is repeated in both the intro and the Parent URI section, and the "等于隐形/等于不存在" argument is restated across sections. Anchor 3 fits: mostly efficient but with repetition and rhetorical padding that could be tightened; not 4 because the duplicated motivation passages are clearly trimmable.

3 / 5

Actionability

Concrete rules are present — "priority=0 全库最多 5 条,priority=1 最多 15 条", "单一父节点下的子节点数 ≤ 10", and the explicit banned-pattern list ("禁止:所有形如'当我感到/意识到/发现自己在…'的写法") with example disclosure phrasings. However, the actual audit procedure (how to enumerate the tree, which tool calls to make, what the output is) is never specified, matching anchor 3: concrete guidance with key execution details missing; not 4 because the operational steps are absent, not merely gapped.

3 / 5

Workflow Clarity

The content is organized as per-concept criteria (parent, disclosure, alias, trigger, priority, child count) rather than as an audit sequence — there are no ordered steps and no validation checkpoints; "巡检验证" is a single heuristic ("感觉太工整了→立刻警惕") rather than a verify/fix/re-check loop. Anchor 2 fits: an implied checklist exists but the workflow is poorly defined and validation is absent; not 3 because even an implicit inspect→evaluate→fix sequence is missing.

2 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the ~77-line body is well-delimited by clear section headers with content appropriately placed for a self-contained guide. Anchor 4 fits: good structure with minor organization gaps (e.g., the disclosure trigger-phrase examples could live in their own subsection); not 5 because the body exceeds the under-50-line simple-skill threshold and a couple of sections could be tightened or split.

4 / 5

Total

12

/

20

Passed

Description

73%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 has an explicit and well-targeted 'when' clause built on distinctive domain vocabulary, giving it strong trigger quality and near-zero conflict risk. Its main weakness is the terse 'what' — "可发现性审计" names the activity but leaves the concrete actions and outputs of the audit unstated.

DimensionReasoningScore

Specificity

Names the domain ("可发现性审计") and four concrete audit targets ("disclosure写法有问题、parent放错、alias缺失、子节点过多"), but the only action stated is the generic "审计" — it never says what the skill actually does (review placements, rewrite disclosures, add aliases). Anchor 3 fits: domain plus concrete objects, without specific capabilities; not 4 because no distinct actions are listed.

3 / 5

Completeness

An explicit "当…时使用" (Use when…) clause with four concrete trigger conditions answers 'when' clearly, and "可发现性审计" answers 'what', but only tersely — the description never states the audit's scope or output. Anchor 4 fits: both present, the 'what' could be more explicit; not 3 because the trigger guidance is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Terms like "disclosure", "parent", "alias", and "子节点" paired with failure modes ("放错", "缺失", "过多") are exactly the natural vocabulary a user managing this memory tree would say. Not 5 because common variations and related trigger terms (e.g., "priority", "trigger", "记忆树", English synonyms) are absent.

4 / 5

Distinctiveness Conflict Risk

The trigger conditions revolve around niche, system-specific vocabulary (disclosure, parent placement, alias, child-node count) that no other skill would plausibly fire on. This matches anchor 5: a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Dataojitori/nocturne_memory

Path

docs/skills/memory-audit-discoverability/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.