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

88%

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

The canonical home for this skill is mempalace-recall in MemPalace/mempalace

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.

The body is highly actionable and well-structured: exact tool names, a decision table, an explicit numbered protocol, and detailed error-recovery paths including copy-paste repair commands. The main improvements are trimming the persona/duplicated guidance and moving recovery and coordination detail into bundled reference files so SKILL.md stays a lean overview.

Suggestions

Move the corrupt-index recovery steps and the coordination-protocol aside into a bundled reference file (e.g., references/recovery.md) and link from the body, keeping SKILL.md a lean overview.

Trim the 'Identity' persona paragraph and deduplicate the supersede/invalidate/add guidance, which appears in both Protocol step 6 and the 'Conflicting facts' unhappy path.

Prune the 'Official References' section to links that aid recall execution (e.g., drop the Cursor Skills documentation link).

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, with no filler explaining known concepts; minor trims remain — the 'Act as a senior AI-memory systems engineer' persona line, the four 'Official References' links, and the supersede/invalidate/add guidance repeated in both Protocol step 6 and the 'Conflicting facts' unhappy path. Fits 'efficient; minor instances of over-explanation' rather than 'every token earns its place'.

4 / 5

Actionability

Concrete throughout: exact MCP tool names with a need→tool table, argument guidance ('takes a short natural-language query … plus optional wing / room filters and limit (default 5)'), explicit decision rules for fact changes, and copy-paste-ready commands ('mempalace repair --mode from-sqlite --archive-existing --yes'). Matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The numbered 6-step Protocol has explicit checkpoints ('If unsure about a fact: say "let me check the palace" and query', 'Stop when answered') plus four detailed unhappy-path recovery loops, including a repair sequence validated by 'mempalace repair-status' and a warning that re-mining 'drops MCP-added drawers and diary entries (#1843)'. Matches the anchor for clear sequencing with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

A well-sectioned single-file skill with clearly signaled one-level-deep links ('The full canonical protocol … is published in the MemPalace repository'), but no bundled reference files exist and, at ~136 lines, the corrupt-index recovery and coordination-protocol detail could live in separate reference files. Fits 'good structure; most content is appropriately placed; minor organization gaps' rather than fully split content.

4 / 5

Total

18

/

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: it states what the skill does, gives an explicit 'Apply when…' list of natural user questions, and draws a clear boundary against the sibling setup skill. The main gap is specificity — only the single 'search the palace' action is named, leaving the KG, diary, and verbatim-quoting capabilities unmentioned in the frontmatter.

Suggestions

Name the skill's concrete actions in the description (e.g., 'quote stored entries verbatim, query the knowledge graph for time-bound facts, and record session continuity in the diary') instead of only 'search the palace'.

Add a few natural trigger variants users actually say — such as 'remember when…', 'last session', or 'previously' — to round out trigger coverage.

DimensionReasoningScore

Specificity

It names the domain ('Recall protocol for MemPalace') and one concrete action — 'search the palace before answering' — but does not enumerate the skill's other concrete capabilities (verbatim quoting, KG queries, diary writes). Fits 'names domain and 1-2 concrete actions, but not comprehensive'; clearly below the 'several specific actions' anchor.

3 / 5

Completeness

It explicitly answers what ('search the palace before answering about past work, people, projects, or prior decisions') and when via an explicit 'Apply when…' clause listing concrete trigger phrases plus direct invocation ('or when mempalace-recall is invoked'). Matches the anchor for clearly and explicitly answering both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural user phrasings like 'what was decided', 'what happened before', 'who someone is', and 'what was discussed last time' give good keyword coverage, but common variants ('remember when…', 'last session', 'previously') are absent. Matches 'good keyword coverage; a few natural terms missing' rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (recall from the MemPalace memory palace) with an explicit boundary against the sibling skill — 'Complements the mempalace setup skill and requires the mempalace-mcp server' — and distinct question-shaped triggers. Matches 'clear niche with distinct triggers; minimal conflict risk'; not 4 because the overlap with the setup skill is explicitly delineated.

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

MemPalace/mempalace

Path

.claude-plugin/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.