CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-management

Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话

Quality

76%

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

Quality

Content

56%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.

A protocol-heavy skill with genuinely strong safety engineering: explicit authorization gates, verification commands, an authority order for conflicts, and careful purge handling with dry-run search and honest limits on erasure claims. Weaknesses are repetition of the same authorization/ownership caveats, uneven concreteness (init/query/audit have runnable commands; archive/consolidate do not), and a reference graph that depends on files outside the skill folder while leaving three bundled templates unlinked.

Suggestions

State the authorization and registry-ownership rules once (e.g., in the Skill Contract) and reference that single statement from sections 3, 5, and 7 instead of repeating the caveats in each section.

Add concrete commands or file-path conventions for the Demote/Archive and Consolidate operations, matching the executable specificity already present for init, query, and audit validation.

Fix the reference graph: either vendor state-model.md, skill-contract.md, runtime-invocation.md, and registry-event-protocol.md into the skill's references/ directory or drop the links, and link the three bundled templates (gdpr-purge-log-template.md, glossary-template.md, hot-cache-template.md) from the body so they are discoverable.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no space is wasted explaining what memory, git, or GDPR are), but authorization and ownership caveats are repeated across the Skill Contract, Decision Gates, Save Results, and again within sections 3, 5, and 7 (e.g., "never accepts registry proposals", "not canonical truth" stated multiple times). This fits anchor 3 ("mostly efficient but... could be tightened") better than anchor 4, since the repetition is more than a minor trim.

3 / 5

Actionability

Some operations carry fully concrete commands (`python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" init`, `is-suppressed <aggregate-id>`, `validate-audit-artifact.py <artifact> --relative-path <artifact>`, `git status --ignored`), but archive/demote, consolidate, and parts of purge are described only abstractly ("Archive moves preserve content hash..." with no command), the referenced scripts/ directory is not part of the bundle, and the Quick Start shows natural-language intents rather than runnable examples. Mixed concrete/abstract guidance matches anchor 3 ("some concrete guidance but incomplete").

3 / 5

Workflow Clarity

Operations are clearly sequenced with numbered steps and real validation checkpoints: verify script/schema/catalog before init, "Confirm .gitignore excludes runtime memory and git status --ignored shows it as ignored", "Confirm suppression by replay, not by a cached view", "Rebuild and verify projections", plus explicit stop-conditions in Decision Gates for the destructive purge path. This satisfies the destructive-operation validation requirement, but there are minor gaps — no explicit error-recovery/feedback loop and no verification step for archive/demote — so anchor 4 fits better than anchor 5.

4 / 5

Progressive Disclosure

Sectioning is clean and there is a dedicated Reference Materials list, but 4 of 8 references point to `../../references/*.md` outside the skill bundle (state-model, skill-contract, runtime-invocation, registry-event-protocol) which do not resolve within this bundle and break the one-level-deep model, and 3 bundle files in references/ (gdpr-purge-log-template, glossary-template, hot-cache-template) are never linked from SKILL.md. More than minor organization gaps, fitting anchor 3 rather than anchor 4.

3 / 5

Total

13

/

20

Passed

Description

88%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.

A strong description: third-person voice, concrete action verbs covering every subcommand, an explicit 'Use when' trigger list with a quoted natural phrase, and a clear negative-scope boundary. The trailing Chinese gloss "项目记忆/跨会话" is unusual but serves bilingual discovery. Main improvement room is broader natural-language synonym coverage for memory-related requests.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "initialize runtime memory", "review saved findings", "archive stale work", "reconcile notes", "erase a subject", "manages authorized HOT/WARM/COLD working memory" — which comprehensively cover the skill's operations (init, review, archive, consolidate, purge). It matches anchor 5's "multiple specific concrete actions; comprehensive coverage"; a 4 would require noticeable coverage gaps, and none are evident since every subcommand from the argument-hint is represented.

5 / 5

Completeness

It explicitly answers "when" with concrete quoted trigger phrases ("Use when the user asks to 'remember project context'...") and "what" ("manages authorized HOT/WARM/COLD working memory... preserving registry event ownership and privacy controls"), plus an explicit exclusion clause ("Not for changing canonical registry facts"). This matches anchor 5's "clearly and explicitly answers both what AND when with concrete trigger phrases"; anchor 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

"remember project context" is a natural user phrase (quoted as a trigger), and "archive stale work", "reconcile notes", "erase a subject" are plausible user phrasings, but common synonyms like "save this", "project memory", "notes", or "recall" are missing. Good keyword coverage with a few natural terms absent fits anchor 4 rather than anchor 3 (which would require notably sparse keywords) or 5 (comprehensive synonym coverage).

4 / 5

Distinctiveness Conflict Risk

The HOT/WARM/COLD memory-lifecycle niche with registry-ownership routing is distinct, and the "Not for changing canonical registry facts - route those through the owning registry" boundary actively reduces mis-triggering. However, generic triggers like "remember project context" could overlap with other memory/note-keeping skills, so it is "mostly distinct; minor overlap risk" (anchor 4) rather than the minimal-conflict anchor 5.

4 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/memory-management/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.