CtrlK
BlogDocsLog inGet started
Tessl Logo

switch-project

Overrides the auto-detected project scope to read and write memories under a different project ID, or enables global search to access all memories across all users and projects. Use when working across multiple projects, accessing memories from another repo, enabling team-wide memory access, or when auto-detection resolves to the wrong project.

70

Quality

86%

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

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

An actionable, well-structured skill with executable code for all three execution paths and a verification step in the main branch. It loses points for duplicated near-identical scripts and missing validation/feedback loops on the config-write branches.

Suggestions

Collapse the --global and --no-global branches into a single parameterized script (e.g. set global_search to a passed-in boolean) to remove the duplicated python3 block and tighten token use.

Add a feedback loop to the project-name branch: after the search_memories verification, state what to do if zero memories are found or the call errors (e.g. confirm the project_id is correct or guide re-mapping).

Verify the flag branches by reading settings.json back after writing (or printing the resolved global_search value) so the user can confirm the change took effect before restarting.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept over-explanation, but the --global and --no-global branches ship near-identical python3 blocks that differ only by True/False, and the intro restates the frontmatter description.

2 / 3

Actionability

Every branch provides fully executable, copy-paste-ready python3 -c scripts with exact print outputs, plus a concrete search_memores call with explicit filters and top_k.

3 / 3

Workflow Clarity

Steps are clearly numbered and the project-name branch includes a verification checkpoint, but there is no error-recovery feedback loop and the flag branches lack any verification of the written file.

2 / 3

Progressive Disclosure

Self-contained and cleanly organized into Usage and Execution sub-branches with no nested or dangling references, which is appropriate for a skill of this scope and size.

3 / 3

Total

10

/

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.

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger clause and a distinct, well-scoped niche. It avoids verbosity and over-claims while covering the natural ways a user would request this behavior.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Overrides the auto-detected project scope to read and write memories under a different project ID', 'enables global search to access all memories across all users and projects' — rather than vague language.

3 / 3

Completeness

Explicitly answers what it does (override project scope / enable global search) and when to use it via an explicit 'Use when...' clause with multiple triggers.

3 / 3

Trigger Term Quality

Covers natural trigger phrases users would say: 'working across multiple projects', 'accessing memories from another repo', 'team-wide memory access', 'auto-detection resolves to the wrong project'.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, specific niche (Mem0 memory project scoping and global search) with distinct triggers, making it unlikely to fire for unrelated skills.

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.