Conciseness

The body is lean with no explanations of concepts Claude already knows; every template and command is load-bearing (exact output formats, settings path, scope definitions). Only minor trimming is possible, e.g. the bash '|| echo "project"' fallback is immediately restated as 'If the command prints nothing, the scope is project (the default)', which is why this sits at anchor 4 rather than 5.

Actionability

Guidance is fully executable: a copy-paste bash one-liner to read the current scope, explicit Read/Write tool instructions for '~/.mem0/settings.json' with key-preservation rules and an example resulting file, plus exact output templates and per-scope effect lines. This matches the 'fully executable, covers common cases' anchor; it is not 4 because no key execution details are missing.

Workflow Clarity

The flow is explicit (determine intent -> view mode or change mode) with input validation ('Validate the target is one of project, session, global. If not, show the three options and stop') and missing-file handling ('treat a missing file as {}'). It stops short of anchor 5 because there is no post-write verification/re-read checkpoint after modifying the settings file.

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (scope definitions, Execution Steps 1-3, Notes, Output formatting) and nothing that belongs in a separate reference. Per the simple-skill scoring note, a skill with no need for external references and well-organized sections scores 5; there are no nested or buried references that would lower it.

Specificity

'Views or changes the default memory scope (project, session, or global) used when saving and searching memories' names the domain, two concrete actions, and enumerates the three scope values — several specific actions with minor coverage gaps (anchor 4). It is not 5 because the action set is narrow (view/change) rather than a comprehensive list of multiple distinct operations.

Completeness

It explicitly answers both questions: what ('Views or changes the default memory scope (project, session, or global) used when 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'). This mirrors the anchor-5 exemplar with concrete trigger phrasing, so it is not 4.

Trigger Term Quality

Natural user phrasings are well covered: 'memory scope', 'this repo', 'this run', 'shared across all their projects', 'saving and searching memories' — including the repo/run/projects synonyms. A few natural terms users might say ('default scope', 'switch scope', 'share memories') are only implied, which keeps this at anchor 4 rather than 5.

Distinctiveness Conflict Risk

It carves a clear niche (controlling memory scoping) with triggers unlikely to fire for unrelated skills, matching 'mostly distinct; minor overlap risk with closely related skills'. Not 5 because it could still overlap with sibling mem0/memory skills (e.g. ones about searching or saving memories) since the description never names the plugin.