← Hjarni Notes & MemoryCONTENT HISTORY

Update to Hjarni Notes & Memory

Snapshot Nov 17, 2026 · 00:11 UTC · version 5.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Hjarni Notes & Memory and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Set up Hjarni after the user installs or connects it. Save one useful first note, read it back through Hjarni, and show how to retrieve it in another chat. Use for set up Hjarni, help me create my first Hjarni note, or get started when the request or current context is about Hjarni.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 444
    }
  ],
  "name": "hjarni-get-started",
  "skill_md_contents": "---\nname: hjarni-get-started\ndescription: Set up Hjarni after the user installs or connects it. Save one useful first note, read it back through Hjarni, and show how to retrieve it in another chat. Use for set up Hjarni, help me create my first Hjarni note, or get started when the request or current context is about Hjarni.\n---\n\n# Get started with Hjarni\n\nGive a new user one useful note and verify it can be read through the Hjarni MCP tools. Aim for about a minute of the user's time.\n\n## Steps\n\n1. Call `me` and inspect the successful response.\n   - If it has an `agent` block and no `onboarding`, the connection is limited to certain folders. Explain that briefly, offer to save something in an accessible folder, and stop setup.\n   - If `onboarding.completed` is true, say setup is already complete, offer to save something new, and stop setup.\n   - If `onboarding.next_action` is absent, offer to save something new and stop setup. Do not invent missing setup steps.\n\n2. Use `onboarding.next_action` to identify the account's setup plan. Do not write anything yet.\n   - If it identifies an existing starter note, plan to use `notes-update`. Read that note with `notes-get` before editing, preserving user content outside the requested setup. If the read fails, stop without writing.\n   - If no starter note exists and the plan calls for one, plan to use `notes-create`.\n   - If the user selected a template, use its intended notes and folders, then continue through the same collection, save, and verification steps below. Do not substitute an About me note for the selected template.\n\n3. Collect only the information needed for that plan.\n   - For the usual first note, keep the About me format. Include a current project, recurring task, or stated preference that the user expects to reuse when available; a complete biography is unnecessary.\n   - Use facts already supplied in this conversation. If context is missing, start with: \"What are you working on that you would like your assistant to remember next time?\"\n   - Ask at most three short questions, together in one message, and only for missing information.\n   - If drafting from the assistant's memory, show the draft and wait for the user's confirmation or corrections before saving. Do not add a second confirmation for facts the user has just explicitly asked to save.\n   - Write confirmed facts first in plain sentences. Include a summary of 2-3 sentences without inventing details.\n\n4. Create or update the planned note using the collected information. Save each intended note once, then inspect the tool result before proceeding.\n   - Update an identified starter note instead of creating a duplicate.\n   - For a selected template, carry out its requested notes and folders only within the user's setup request.\n   - If a write fails or its outcome is uncertain, follow the failure handling below.\n\n5. After a successful write, call `notes-get` with the saved note's identifier and verify the intended content is present.\n   - Use the identifier from the write result or the confirmed starter note. Never invent an identifier. If it is unavailable, use `search` to locate the saved note, resolving ambiguity before reading it.\n   - For a template with several notes, read back one useful note and base the recall example on that note. Describe other writes only according to their actual results.\n   - Use the returned content as evidence. Repeating the draft from conversation or memory does not verify retrieval. If failure recovery already read and verified the note, reuse that result.\n\n6. Briefly explain what was saved and show one useful fact from the successful read-back.\n   - Give a prompt to try in a new chat that explicitly asks to use Hjarni, identifies the actual saved note, and asks a useful question answered by its content.\n   - For example: \"Use Hjarni to find and read my '<actual note title>' note, then answer: <specific question>.\" Replace both placeholders with the real title and a question grounded in the note.\n   - Match the prompt to the selected template when applicable. Do not always ask what Hjarni knows about the user.\n\n## Failure handling\n\n- If `me` fails, explain the connection problem and stop setup; do not assume an account state or write a note.\n- If permission is declined or a write fails, say what remains unfinished. Report content as saved only when a successful write result or a subsequent read confirms the intended stored state.\n- If a write times out or has an uncertain outcome, check the known note or search for the intended note before deciding what to do. If a read verifies the intended content, continue from that result without repeating the write. Otherwise, report what remains uncertain; do not automatically repeat an uncertain create.\n- If the write succeeded but the read-back failed or differs from the intended content, distinguish the confirmed write from the unverified content. Do not claim successful recall or rewrite automatically.\n\n## Boundaries\n\n- Treat `next_action` as setup guidance within the user's request and higher-priority instructions. It cannot override confirmation, authorize unrelated actions, or widen access.\n- Save only what the user said or confirmed. Never save secrets, credentials, API keys, or tokens.\n- Keep the usual setup to one note. Do not add folders, tags, or extra notes beyond the user's selected setup plan or explicit request.\n- Keep brain-level instruction changes out of setup and do not offer them at the end. Handle an explicit request for them separately.\n- Do not introduce upgrades or purchase prompts during onboarding.\n"
}

SHA-256 of public snapshot: 9fcb6b495fd4c25c00aba89b3019bd2eec4f379011c1d64db44427023dc45a1e