CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory

Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall/capture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally tight operational reference: exact call signatures for every tool action, a copy-paste curl example, and verbatim error strings with recovery guidance for each failure mode. The only structural gap is that the two specialized sub-procedures (admin org-wide writes, member brain connection) are inlined in SKILL.md rather than split into reference files.

Suggestions

Move the member-brain connection walkthrough (~18 lines, relevant to a small subset of turns) into a reference file and keep a one-line pointer in SKILL.md.

Consider the same split for the org-admin self-API section, keeping the core actions and failure modes as the always-loaded overview.

DimensionReasoningScore

Conciseness

Lean and operational throughout: substring-match semantics ("Matching is substring-based (all terms must match)"), empty-result interpretation, scope rules, and verbatim error strings each convey harness-specific facts Claude could not infer. No padding or explanations of known concepts; not 4 because there is no section that could be trimmed without losing actionable information.

5 / 5

Actionability

Every typed-tool operation has its exact call signature (`action: "add", facts: [{text}, …]`, `action: "delete" with `ids``), the org write path is a complete copy-paste curl command with headers and JSON body, and failure modes cite verbatim errors ("403 org memory writes require an org admin") with exact remedies. Not 4 because the common cases are fully executable, matching the anchor-5 example pattern of copy-paste commands plus specific behavioral notes.

5 / 5

Workflow Clarity

Curation is sequenced ("search or read to get each fact's `#id`, then fix facts that changed and delete stale..."), destructive edits have validation ("changes nothing and lists the bad ids"), the org-wide batch write has an explicit confirm-first checkpoint ("confirm the wording with the admin before writing"), and the Failure modes section is a per-error recovery feedback loop. Not 4 because checkpoints and error-recovery loops are explicit for every risky operation, including the 403/401/502 paths.

5 / 5

Progressive Disclosure

Well-organized single file: clear audience-labeled sections ("## Org-wide notebook (admins)", "## A member's own memory brain", "## Failure modes") and one clearly signaled cross-skill reference ("see the `secret-drop` skill") with no nesting. Not 5 because at ~90 lines (above the under-50-line simple-skill exception) the specialized admin and member-brain procedures are natural candidates for one-level-deep reference files; not 3 because structure is clean, labeled, and easy to navigate.

4 / 5

Total

19

/

20

Passed

Description

82%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 with an explicit what-and-when structure and concrete, natural trigger scenarios. The main deductions are the second-person voice ("your long-term memory", "your notebook"), which the rubric penalizes on specificity, and missing common trigger synonyms like "remember" or "forget".

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. "Deliberately searches, adds to, or curates long-term memory with the `memory` tool..."

Add natural trigger synonyms such as "remember this", "recall what you know about", or "forget that" to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names three concrete actions ("search, add to, or curate your long-term memory") with the tool named, which fits anchor 4 ("several specific actions; minor gaps" — read-other-notebook and admin paths are absent), but the rubric's voice guideline penalizes the second-person usage ("your long-term memory", "your notebook") by 1 point, landing at 3. Not 2 because the actions are concrete and domain-specific, far beyond "names the domain but actions are minimal".

3 / 5

Completeness

Explicitly answers both: what ("Deliberately search, add to, or curate your long-term memory with the `memory` tool") and when ("Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries"), matching the anchor-5 pattern of concrete trigger phrases. Not 4 because the "when" clause is already explicit and specific with three concrete scenarios.

5 / 5

Trigger Term Quality

Includes natural trigger scenarios users would actually say ("asked who someone is or what they're working on", "a durable fact worth keeping now", "stale or wrong entries you should clean up") plus keywords like memory, notebook, curate. Not 5 because common natural synonyms such as "remember this", "recall", or "forget that" are not covered.

4 / 5

Distinctiveness Conflict Risk

Clear niche (long-term memory management via the `memory` tool) with an explicit boundary against the default behavior ("beyond the automatic recall/capture every turn already does"), and distinct triggers unlikely to fire for unrelated skills. Not 4 because there is no meaningful overlap risk with a closely related skill — the niche and triggers are unambiguous.

5 / 5

Total

17

/

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

yc-software/qm

Path

skills-seed/memory/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.