CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mem-setup

This skill should be used when the user asks to "set up claude-mem", "pair claude-mem", "connect cmem", "add my cmem key", "set up cloud sync in Cowork", or provides cmem.ai Connect values (sync token, user id, SyncHub URL) for this plugin. Configures the claude-mem-cowork plugin credentials.

Quality

96%

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

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

Excellent instructional content: precise, secret-safe, and complete for its single purpose, with concrete key names, paths, commands, expected verify outputs, and an explicit fallback when verification fails. Nothing is padded, and everything actionable is executable.

DimensionReasoningScore

Conciseness

The body is lean and every line carries plugin-specific knowledge Claude cannot infer (ephemeral Cowork containers, exact key names, hooks staying off when local claude-mem exists, the expected 404 on /api/hooks/context). No padding or explanation of known concepts.

5 / 5

Actionability

Guidance is fully executable: exact config keys (apiKey, userId, syncHubUrl), exact env var names, exact file path and 0600 mode for ~/.claude-mem/settings.json, a copy-paste verify command, and concrete expected outputs (configured: true, hub.reachable: true). Sub-steps like packaging are delegated with the concrete action stated (zip as <plugin-name>.plugin) plus a named skill flow.

5 / 5

Workflow Clarity

A clear numbered sequence with an explicit verification step, failure interpretation ('A MISSING key means the write didn't land'), and a fallback path ('if it never does, pair through that skill's installer flow instead') — a genuine validate-fix-retry loop. Not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

A single-purpose, ~59-line skill with no bundle files (no references/, scripts/, or assets/ present, and none needed). Sections are well-organized (What to collect, Secret handling, Steps, Alternate source) and the only external pointers are clearly-signaled, one-level-deep references to other skills' flows.

5 / 5

Total

20

/

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.

A strong description: explicit trigger guidance with quoted natural user phrases, a clear if brief statement of what it does, and a distinct niche. The only weakness is that the 'what' clause names a single action, leaving capability coverage thin relative to the anchor examples.

Suggestions

Expand the 'what' clause with one or two more concrete actions, e.g. 'Configures the claude-mem-cowork plugin credentials (API key, user id, SyncHub URL) and verifies the pairing', to lift specificity.

Mention the outcome the configuration enables — 'so hooks can capture and inject memory' — in the description so the capability coverage reads as comprehensive for the skill's purpose.

DimensionReasoningScore

Specificity

The 'what' is a single concrete action — 'Configures the claude-mem-cowork plugin credentials' — with the involved values enumerated (sync token, user id, SyncHub URL). It names the domain precisely but does not list several distinct actions, so it sits at the '1-2 concrete actions' anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both questions: 'This skill should be used when the user asks to...' gives concrete trigger phrases, and 'Configures the claude-mem-cowork plugin credentials' states the what. This matches the anchor-5 pattern of explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

The description quotes natural user phrasings directly — 'set up claude-mem', 'pair claude-mem', 'connect cmem', 'add my cmem key', 'set up cloud sync in Cowork' — and covers the synonyms (claude-mem, cmem, cmem.ai, Cowork) plus the raw Connect values users might paste. This is comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is narrow (cmem.ai Cowork pairing for one specific plugin) and the triggers are product-specific phrases no other skill would claim, giving minimal overlap risk.

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

thedotmack/claude-mem

Path

cowork/skills/mem-setup/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.