CtrlK
BlogDocsLog inGet started
Tessl Logo

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate and says "verify", "test the integration", "run /mem0-test-integration", or when a .mem0-integration/ directory exists and tests have not been run yet on the current branch. DO NOT TRIGGER when: the user wants to run general project tests (defer to the repo's native test command), or when no prior /mem0-integrate run exists in the current branch (ask them to run /mem0-integrate first). This skill ONLY catches compile and runtime bugs by design. Logical integration errors — wrong data stored, wrong time retrieved, wrong user scoping — are on the human reviewer.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A thorough, highly actionable verification pipeline with excellent workflow sequencing and validation checkpoints. Its main weaknesses are monolithic structure with no progressive disclosure to reference files, and some redundancy in the out-of-scope section.

Suggestions

Move the scorecard JSON schema and E2E recipe field reference into separate reference files (e.g. references/scorecard.schema.json, references/e2e-recipe.md) and link to them from the body, reducing the ~340-line SKILL.md toward an overview.

Collapse the 'Explicitly out of scope' section so it does not restate non-invasiveness, self-healing, and disposable-user_id points already made in the Non-invasiveness contract, steps 4–6, and Preconditions — reference those instead of repeating.

De-duplicate the self-heal-loop and disposable-user-id guidance, which each appear in three or more places, to recover token budget without losing the safety signal.

DimensionReasoningScore

Conciseness

The body is dense and largely avoids explaining concepts Claude already knows, but the "Explicitly out of scope" section and repeated self-heal/disposable-user-id notes restate points made earlier (steps 4, 5, 8, preconditions), so it could be tightened; not level-3 lean.

2 / 3

Actionability

Provides fully executable guidance throughout — exact install/test commands, a real Python smoke-test snippet, grep patterns for eager-init detection, a complete scorecard JSON template, and a precise exit-code table — copy-paste ready rather than descriptive.

3 / 3

Workflow Clarity

An 8-step pipeline with explicit validation checkpoints (install-fail exit 2, Pass A hard fail, non-zero type-check fail, smoke assertion, E2E read_assert gate) and mandatory cleanup "always, even on failure", matching the level-3 anchor for sequenced validation with feedback loops.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a ~340-line monolithic SKILL.md with no bundle/reference files; content such as the scorecard schema, E2E recipe field spec, and artifacts/exit tables is inline rather than split into one-level-deep references, so it sits at level-2 rather than the well-signaled multi-file level-3.

2 / 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 states concrete actions, explicit trigger and anti-trigger conditions, and clear scope boundaries. It leaves little ambiguity about when to invoke the skill or what it does.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard" — matching the level-3 anchor of several specific concrete actions rather than a vague domain mention.

3 / 3

Completeness

Explicitly answers both what (verify/install/test/smoke/scorecard) and when via a dedicated "TRIGGER when:" clause, satisfying the level-3 anchor and avoiding the missing-trigger cap at 2.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say ("verify", "test the integration", "run /mem0-test-integration") plus a `.mem0-integration/` directory signal, giving good coverage of likely trigger terms; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to verifying a /mem0-integrate run, with a "DO NOT TRIGGER when:" clause that explicitly defers general project tests, making it unlikely to fire for the wrong skill.

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.