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	9263c15	Aug 23 2026, 02:39 PM

[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	9263c15	Commit Preview URL Branch Preview URL	Aug 23 2026, 02:40 PM

[claude]

Claude finished @ved015's task in 1m 8s —— View job

---

Reviewing PR #1435

• Fetch PR diff and review changes
• Check for existing review comments
• Review documentation for accuracy and issues
• Submit review summary

---

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 for v4 API.

Issues found: None — this looks good to ship.

Score: 10/10

The documentation is well-structured and accurate:

• API examples are correct: Uses q parameter consistently for search/profile, environment variables for API keys, and proper response shape access (.profile.static, .profile.dynamic, .searchResults?.results)
• Tool naming follows conventions: TypeScript (camelCase: searchMemories, addMemory) and Python (snake_case: search_memories, add_memory)
• Security guidance is solid: Warns about destructive operations (documentDelete, memoryForget), recommends filtering exposed tools, and documents the distinction between soft/hard deletes
• v4 API updates are reflected: New filter syntax with AND arrays, default threshold 0.6, pagination with 1-based page instead of offset, and correct documents.list() response shape

The new sections on "Agent tools vs middleware" and "Removing information — three different mechanisms" provide clear guidance for implementers. No bugs, security issues, or logic errors found.

[Dhravya]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• 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.