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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A thorough, highly actionable verification pipeline with strong workflow sequencing and validation checkpoints. The main weakness is conciseness — some scoping statements are repeated across sections and the inline scorecard example adds length.

Suggestions

Consolidate the 'logical correctness is human-review territory' statement to a single location; it currently appears in the description, the scorecard 'NOT checked' section, and 'Explicitly out of scope'.

Consider moving the full scorecard JSON example into a bundled reference file (e.g. references/scorecard.example.json) and summarizing its key fields inline, which would tighten the body and improve progressive disclosure.

Trim the verbose E2E recipe field descriptions where the table format already implies the contract, retaining only the behavioral constraints (timeouts, cleanup).

Dimension	Reasoning	Score
Conciseness	Mostly efficient and operational, but the 'out of scope' framing of logical-correctness gaps is restated three times (description, scorecard 'NOT checked' section, 'Explicitly out of scope') and the inline scorecard JSON is verbose, so it could be tightened.	3 / 5
Actionability	Fully executable throughout: concrete install/test/lint commands in tables, a copy-paste smoke-test snippet, concrete E2E recipe fields with a numbered execution order, and a full exit-code table covering the common cases.	5 / 5
Workflow Clarity	An 8-step pipeline with explicit validation checkpoints (refuse-on-precondition, Pass A must be 100% green as a hard fail, ready_probe polling, read_assert gate, always-cleanup), plus feedback-loop signals (exit 7 refuses the heal loop).	5 / 5
Progressive Disclosure	Well-organized single-file structure with clearly signaled one-level external references (the canonical-sources URLs to WebFetch) and no nested references; no bundle files exist, so most content sits inline with only minor gaps such as the inline scorecard schema.	4 / 5
	Total	17 / 20 Passed

Description

92%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 high-quality description: concrete actions, explicit positive and negative trigger guidance, and a sharply defined niche. The only mild gap is trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'installs dependencies', 'runs the repo's native test suite', 'exercises a real end-to-end smoke flow against the user's API key', 'Produces a scorecard' — covering the skill's purpose comprehensively.	5 / 5
Completeness	Explicitly answers both 'what' (verify a Mem0 integration via install, native tests, smoke flow, scorecard) and 'when' (concrete 'TRIGGER when' / 'DO NOT TRIGGER when' guidance), which is the anchor-5 pattern.	5 / 5
Trigger Term Quality	Natural trigger phrases ('verify', 'test the integration', 'run /mem0-test-integration') plus a directory-state trigger are present, but a few common synonyms/variations are missing so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear niche (verifying /mem0-integrate output) with distinct triggers and explicit negative triggers that deflect general test-running, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: mem0ai/mem0
Path: skills/mem0-test-integration/SKILL.md
Commit: 39bc023

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.