CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mempalace-recall

Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-engineered operational skill: concrete tool guidance, copy-paste repair commands, and unusually thorough error-recovery loops for empty results, server failures, and a corrupt vector index. The main improvement levers are trimming the persona section and the duplicated fact-supersession guidance, and splitting the recovery/coordination detail into reference files now that the body has grown past overview length.

Suggestions

Remove or compress the "Identity" persona section ("Act as a senior AI-memory systems engineer...") — it adds tokens without changing agent behavior, improving the conciseness score.

State the kg_supersede / kg_invalidate / kg_add distinction once (either in Protocol step 6 or in the Conflicting-facts unhappy path, not both) to remove duplication.

Move the corrupt-index recovery procedure and the coordination/logstream guidance into reference files linked from the body, slimming SKILL.md toward an overview with clearly signaled one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics (tool table, argument specs, repair commands, unhappy paths), but the "Identity" persona section ("Act as a senior AI-memory systems engineer with decades of experience") is padding, and the kg_supersede/kg_invalidate/kg_add guidance is stated twice (Protocol step 6 and the Conflicting-facts unhappy path) — trimmable, so anchor 4 rather than 5.

4 / 5

Actionability

Fully executable guidance throughout: named MCP tools with argument semantics ("`mempalace_search` takes a short natural-language `query` ... plus optional `wing` / `room` filters and `limit` (default 5)"), copy-paste shell commands (`mempalace --version`, the `mempalace repair --mode from-sqlite --archive-existing --yes` block), and a decision table mapping needs to tools that covers the common cases.

5 / 5

Workflow Clarity

A numbered 6-step Protocol with clear sequencing is backed by explicit validation checkpoints and feedback loops: a Step-0 availability check, "Stop when answered", the empty-results loop (one empty query does not prove absence — widen scope, then state what was checked rather than inventing an answer), and the corrupt-index recovery path with concrete repair commands and a warning not to re-mine (which drops MCP-added drawers).

5 / 5

Progressive Disclosure

No bundle files exist; the body is self-contained with well-labeled sections and clearly signaled, one-level-deep external links to the canonical protocol docs in the MemPalace repository. Structure is good and navigation is easy, but everything is inlined in a ~136-line body (unhappy-path repair detail and coordination-protocol material could live in separate reference files), so it lands on anchor 4 rather than the well-split anchor 5.

4 / 5

Total

18

/

20

Passed

Description

90%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 is a strong example: it pairs a concrete what with an explicit, naturally-phrased when clause, and it deliberately disambiguates itself from the sibling setup skill. Its only soft spot is that the what-side rests on a single action (search-before-answer) rather than a broader action list, capping specificity at the middle anchor.

DimensionReasoningScore

Specificity

"search the palace before answering" names the domain and one concrete action with enumerated scope ("past work, people, projects, or prior decisions"), but it does not list several distinct actions, so it fits the '1-2 concrete actions, not comprehensive' anchor rather than the level above.

3 / 5

Completeness

It explicitly answers both what ("Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions") and when ("Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time"), with concrete trigger phrases matching the top anchor exactly.

5 / 5

Trigger Term Quality

The description embeds verbatim natural user phrases ("what was decided, what happened before, who someone is, what was discussed last time") plus a catch-all ("anything that may already be filed in their memory palace") and an explicit invocation trigger ("or when mempalace-recall is invoked") — comprehensive synonym coverage for this domain.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche tied to a specific product ("requires the mempalace-mcp server") and explicitly distinguishes the sibling skill ("Complements the mempalace setup skill"), keeping conflict risk minimal.

5 / 5

Total

18

/

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

MemPalace/mempalace

Path

skills/mempalace-recall/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.