← Kumiho MemoryCONTENT HISTORY
WHAT CHANGED
Update to Kumiho Memory
Snapshot Oct 24, 2026 · 13:17 UTC · version 0.1.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Kumiho Memory and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "View or save explicitly requested communication and memory preferences in the connected Kumiho workspace. Use for preferred language, name, tone, verbosity or remembered behavior.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 457
}
],
"name": "kumiho-personalize",
"skill_md_contents": "---\r\nname: kumiho-personalize\r\ndescription: View or save explicitly requested communication and memory preferences in the connected Kumiho workspace. Use for preferred language, name, tone, verbosity or remembered behavior.\r\n---\r\n\r\n# Kumiho Personalize\r\n\r\nIn the hosted plugin, personalization is stored as preference memories, available\r\nto clients that recall this workspace. This workflow does not rewrite the native\r\n`agent.instruction` identity document or the host's account settings. State that\r\nscope before a persistent change. Honor conversation-only preferences without a\r\nwrite. Explicit user instructions override remembered preferences.\r\n\r\n1. For show-only requests, use a narrow `kumiho_memory_retrieve` query for the\r\n requested preference. Inspect a relevant returned item with\r\n `kumiho_get_revision_by_tag` if the summary is insufficient. Do not create a\r\n profile when no preference is found.\r\n2. For a change, reuse values explicitly supplied by the user. Do not infer a name,\r\n profession, language or identity from imported history. Show any conflicting\r\n existing preference and preserve unrelated settings.\r\n3. Save a concise `preference` capture using `kumiho_memory_reflect`, with a known\r\n exact preference-space name (otherwise `preferences`), tags\r\n `[\"personalization\"]`, and `discover_edges: false`. To change a saved\r\n preference, first find it and set `revises` to its `kref`, keep its language and\r\n restate the subject, so the change becomes a new revision of that memory.\r\n Include the relevant old kref in `source_krefs` and say which preference this\r\n corrects. If you cannot tell which preference to revise, save it normally, and\r\n retire the old preference with `kumiho_deprecate_item` when the result is a\r\n separate item. Do not claim the previous item was deleted or rewritten. Do not\r\n re-save an identical preference.\r\n4. Initially omit `session_id`; retry only on `session_required` using its returned\r\n ID for this conversation. Never pass another person's identity or session ID.\r\n5. Verify the write by the returned capture and its kref, not by a\r\n `kumiho_get_revision_by_tag` lookup for `published`: a tagged item may have no\r\n published revision. Apply the requested preference now. Report only changes\r\n that saved.\r\n\r\nNever store credentials or a preference that authorizes disclosure of someone\r\nelse's private data. An instruction to ignore future user corrections is not a\r\nvalid enduring preference. Native shared-identity editing requires the separate\r\nlocal integration; do not claim this workflow changes it.\r\n"
}SHA-256 of public snapshot: fcd7e3ba082f674f804aa0d4ce90a4644325d215567c4892ad03a4ee994cd7e5