CtrlK
BlogDocsLog inGet started
Tessl Logo

mem0-scope

Views or changes the default memory scope (project, session, or global) used when saving and searching memories. Use when the user wants to control whether memories are scoped to this repo, this run, or shared across all their projects.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully actionable single-purpose skill: executable commands, explicit tool use, a validation checkpoint with stop-on-invalid behavior, and destructive-op safeguards. It is well organized with no wasted tokens and no bundle files to disclose.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it explains neither what memory nor JSON is, and every section (scope definitions, execution steps, notes, formatting) earns its place, matching the score-3 'lean and efficient' anchor rather than the padded score-2 example.

3 / 3

Actionability

Provides executable bash for reading the current scope, explicit Read/Write tool instructions for the mutation, exact display templates, and per-scope effect lines — copy-paste ready with no pseudocode, matching the score-3 anchor.

3 / 3

Workflow Clarity

Clear Step 1→2→3 sequence with an explicit validation checkpoint (validate target scope; show the three options and stop if invalid), key-preservation and revert instructions, and a safeguard noting delete_all_memories ignores the default — the feedback-loop cap at 2 does not apply because validation is present.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the skill is a focused, well-organized single task with clear headers (Execution, Notes, Output formatting), so per the rubric's simple-skill guidance it scores 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, concrete, and uses correct third-person voice with an explicit 'Use when' trigger covering natural user phrasings. It clearly answers both what the skill does and when to invoke it, with low conflict risk.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('Views or changes the default memory scope') plus the three concrete scopes ('project, session, or global') and the affected operations ('saving and searching memories'), matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what (view/change the default memory scope for saving and searching memories) and when ('Use when the user wants to control whether memories are scoped to this repo, this run, or shared across all their projects'), matching the score-3 anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasings — 'scope', 'this repo', 'this run', 'shared across all their projects' — alongside the canonical scope names, giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The niche — controlling mem0 memory scope — is distinct and the triggers (repo/run/all-projects scoping) are unlikely to fire for unrelated skills, satisfying the clear-niche score-3 anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mem0ai/mem0
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.