How do I install the Memmesh Test Integration skill?

Run npx skillmds@latest add thinkfleetai/memmesh-test-integration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memmesh Test Integration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memmesh Test Integration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memmesh Test Integration free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Memmesh Test Integration?

thinkfleetai (@thinkfleetai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memmesh Test Integration by thinkfleetai

Name: Memmesh Test Integration
Author: thinkfleetai

Memmesh Test Integration

Verify a MemMesh integration produced by memmesh-integrate. Runs in the same workspace: executes the repo's native test suite, then exercises a real end-to-end smoke flow (observe → search → optionally predict) against the user's live key or local engine, and produces a pass/fail scorecard. TRIGGER when: the user has just run memmesh-integrate and says "verify", "test the integration", or when a `.memmesh-integration/` directory exists and tests have not been run yet. DO NOT TRIGGER for: first-time wiring (use memmesh-integrate) or vendor migration (use memmesh-migrate).

thinkfleetai e34410a 2.3 KB Updated Sep 17, 2026

File contents

memmesh-test-integration

Prove the integration actually works — not just that it typechecks.

Preconditions

A .memmesh-integration/ directory exists (else tell the user to run memmesh-integrate first).
Credentials: Hosted ⇒ MEMMESH_API_KEY set; Local ⇒ memmesh doctor passes.

Steps

Static gate. Typecheck / lint / build. Any failure ⇒ stop, report.
Native suite. Run the repo's own tests twice — once with MEMMESH_ENABLED unset (must be byte-for-byte the original behavior) and once set. Both must pass.
Real E2E smoke against the live engine (not a mock):
- observe a known fact for a throwaway userId (e.g. smoke-<runid>).
- search for it; assert the fact comes back.
- buildContext for the subject; assert the fact appears in the bundle.
- If prediction was wired: call predict / predictTarget and assert you get either a calibrated probability or an honest abstention — both are a pass; a crash or an uncalibrated 1.0/0.0 with no evidence is a fail.
- Clean up: memory_delete (or compliance.hardDeleteSubject) the throwaway subject so the smoke run leaves no residue.

Scorecard. Write .memmesh-integration/scorecard.md:

Check	Result
Typecheck / build	✅ / ❌
Native tests (flag off)	✅ / ❌
Native tests (flag on)	✅ / ❌
E2E observe→search	✅ / ❌
E2E buildContext	✅ / ❌
E2E predict (calibrated OR abstained)	✅ / ❌ / n/a
Smoke cleanup	✅ / ❌

Definition of done

Every applicable row green, throwaway data removed, and a one-paragraph verdict: ship / needs-work, with the failing checks called out.

---name: memmesh-test-integrationdescription: Verify a MemMesh integration produced by memmesh-integrate. Runs in the same workspace: executes the repo's native test suite, then exercises a real end-to-end smoke flow (observe → search → optionally predict) against the user's live key or local engine, and produces a pass/fail scorecard. TRIGGER when: the user has just run memmesh-integrate and says "verify", "test the integration", or when a `.memmesh-integration/` directory exists and tests have not been run yet. DO NOT TRIGGER for: first-time wiring (use memmesh-integrate) or vendor migration (use memmesh-migrate).license: Apache-2.0---# memmesh-test-integrationProve the integration actually works — not just that it typechecks.## Preconditions- A `.memmesh-integration/` directory exists (else tell the user to run `memmesh-integrate` first).- Credentials: Hosted ⇒ `MEMMESH_API_KEY` set; Local ⇒ `memmesh doctor` passes.## Steps1. **Static gate.** Typecheck / lint / build. Any failure ⇒ stop, report.2. **Native suite.** Run the repo's own tests **twice** — once with `MEMMESH_ENABLED` unset (must be byte-for-byte the original behavior) and once set. Both must pass.3. **Real E2E smoke** against the live engine (not a mock): - `observe` a known fact for a throwaway `userId` (e.g. `smoke-<runid>`). - `search` for it; assert the fact comes back. - `buildContext` for the subject; assert the fact appears in the bundle. - If prediction was wired: call `predict` / `predictTarget` and assert you get *either* a calibrated probability *or* an honest abstention — both are a pass; a crash or an uncalibrated 1.0/0.0 with no evidence is a fail. - Clean up: `memory_delete` (or `compliance.hardDeleteSubject`) the throwaway subject so the smoke run leaves no residue.4. **Scorecard.** Write `.memmesh-integration/scorecard.md`: | Check | Result | |---|---| | Typecheck / build | ✅ / ❌ | | Native tests (flag off) | ✅ / ❌ | | Native tests (flag on) | ✅ / ❌ | | E2E observe→search | ✅ / ❌ | | E2E buildContext | ✅ / ❌ | | E2E predict (calibrated OR abstained) | ✅ / ❌ / n/a | | Smoke cleanup | ✅ / ❌ |## Definition of doneEvery applicable row green, throwaway data removed, and a one-paragraph verdict:ship / needs-work, with the failing checks called out.

Frequently asked questions