.claude/skills/multi-ai-local-memoryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Connect supported AI models, agents, and clients to one user-owned local shared memory through Multi-AI Local Memory. Default local memory app is Obsidian and default intermediary is OpenClaw, but neither is required.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/multi-ai-local-memoryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/multi-ai-local-memoryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/multi-ai-local-memoryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @a7904282000/multi-ai-local-memoryclawhub inspect @a7904282000/multi-ai-local-memory --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:7076970aae8eb6253c93f1bca2cd556e4973fba93865e57feeaf3fb9f0dbe419README.mdskill-card.mdSKILL.mdMulti-AI Local Memory 1.0.0 establishes requirements for connecting supported AI endpoints to one user-owned local memory. - Defines shared-memory behavior: recall relevant context before a turn and capture durable new information afterward. - Sets rules for durable memory, sensitive information, and preserving imported source files exactly. - Clarifies that provider-private memory is separate and must not be claimed as modified without an official interface. - Documents setup expectations, completion checks, and evidence-based failure handling.