docs(skills): refresh Supermemory skill for 7-tool parity

[Dhravya]

Summary

• Update SKILL.md with proactive search and full 7-tool surface
• Refresh sdk-guide.md with v4 API examples and tool descriptions

Stacked on #1434

Test plan

• Review skill content for accuracy

Made with Cursor

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-mcp	4173edb	Sep 01 2026, 06:18 AM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	4173edb	Commit Preview URL Branch Preview URL	Sep 01 2026, 06:25 AM

[claude]

Claude finished @Dhravya's task in 1m 28s —— View job

---

PR Review Complete

• Fetch PR diff and existing review comments
• Review documentation changes for accuracy
• Check code examples for bugs/security issues
• Submit review summary

---

Overview: Documentation update that refreshes Supermemory skill docs for v4 API parity, including the 7-tool surface area, middleware patterns, and updated code examples.

Issues found: None — this looks good to ship.

Score: 10/10

I verified the documentation against the actual implementation in packages/tools/src/ai-sdk.ts and packages/tools/src/vercel/index.ts:

• All 7 tool names (searchMemories, addMemory, getProfile, documentList, documentAdd, documentDelete, memoryForget) match the implementation
• The supermemoryTools(apiKey, { containerTags: [...] }) signature is correct
• The withSupermemory middleware export and usage pattern is accurate
• Code examples use environment variables for API keys (good security practice)
• v4 API changes (query → q, updated response shapes, filter syntax) are documented correctly

The documentation is clear, accurate, and provides valuable guidance on when to use tools vs middleware patterns, and how to handle deletion operations properly.

[Dhravya]

• feat(sdk-playground): reflect SDK-owned memory block in debug view #1533
• feat(python-sdks): SDK-level cross-source memory deduplication #1532
• feat(tools): SDK-level cross-source memory deduplication #1531
• feat(sdk-playground): interactive SDK chat playground #1437
• chore(ci): wire JS tools unit tests into CI #1436
• docs(skills): refresh Supermemory skill for 7-tool parity #1435 👈 (View in Graphite)
• fix(python-sdks): v4 API migration for integration packages #1434
• feat(ai-sdk): re-export 7-tool surface #1433
• feat(tools): 7-tool parity and description refresh #1432
• chore(ci): Python SDK pytest workflow #1431
• feat(openai-sdk-python): 7-tool parity #1430
• fix(openai-sdk-python): migrate to v4 Supermemory APIs #1429
• main

---

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Overview: Documentation update that adds comprehensive guidance for Supermemory's 7-tool surface area, including agent tools vs middleware patterns, deletion mechanisms, and SDK examples.

Issues found: None — this looks good to ship.

Score: 10/10

The documentation is clear, accurate, and follows existing patterns. Examples use environment variables properly for API keys, tool naming conventions are consistent between TypeScript (camelCase) and Python (snake_case), and the new sections provide valuable guidance on when to use each tool.

[graphite-app]

Merge activity

• Sep 1, 4:33 AM UTC: Dhravya added this pull request to the Graphite merge queue.
• Sep 1, 4:34 AM UTC: The Graphite merge queue removed this pull request due to downstack failures on PR #1431.
• Sep 1, 4:34 AM UTC: The Graphite merge queue removed this pull request due to downstack failures on PR #1431.
• Sep 1, 5:59 AM UTC: Dhravya added this pull request to the Graphite merge queue.
• Sep 1, 6:16 AM UTC: Merged by the Graphite merge queue.

The base branch was changed.