{"id":6072,"plugin_id":"plugin_asdk_app_69c3058914bc81919b807c176a7c106c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:47:35.737Z","digest":"3475593db189b3f8c17465a973420b09c27abde77c3c373cf88a45503fc7c236","against":null,"payload":{"description":"Save decisions, findings, preferences, and conventions to the user's Hjarni knowledge base when they say remember this, save this, note this down, or add this to my notes. Updates an existing note when one covers the topic instead of creating a duplicate.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":427}],"name":"hjarni-remember","skill_md_contents":"---\nname: hjarni-remember\ndescription: Save decisions, findings, preferences, and conventions to the user's Hjarni knowledge base when they say remember this, save this, note this down, or add this to my notes. Updates an existing note when one covers the topic instead of creating a duplicate.\n---\n\n# Save knowledge to Hjarni\n\nCapture what the user asked to remember as a durable, well-filed note in their Hjarni knowledge base, using the Hjarni MCP tools.\n\n## Steps\n\n1. If this is the first Hjarni call in the conversation, call `me`, then `instructions-get` with level `brain`. Follow the user's brain instructions for naming, filing, summaries, and tags. If the user is near their note limit, prefer updating an existing note over creating a new one and tell them why.\n2. Distill the thing to remember into one clear fact, decision, or procedure. Strip conversation-specific detail (file paths from a one-off session, timestamps like \"today\") unless it is the point of the note. Convert relative dates to absolute dates.\n3. Call `search` with 1-2 queries for the topic. If an existing note covers it:\n   - Call `notes-get` to read the current version.\n   - Call `notes-update` with a targeted edit that adds or corrects the fact. Do not rewrite unrelated sections.\n4. If no note covers it, call `notes-create` with:\n   - A short, searchable title stating the fact, not the category (\"Deploys go through Kamal, never direct SSH\", not \"Deployment notes\").\n   - A markdown body with the fact first, then why it matters, then any how-to detail.\n   - A summary of 2-3 sentences. Always include a summary; it is what future searches surface.\n   - The most fitting folder. Call `containers-list` if you have not seen the folder tree this conversation. Only create a new folder when nothing fits and say so.\n   - Existing tags where they fit (`tags-list`); create a tag only for a genuinely new cross-cutting theme.\n5. Confirm to the user in one sentence: what was saved or updated, and in which folder.\n\n## Boundaries\n\n- Never save secrets, credentials, API keys, or tokens, even when asked. Offer to save where the secret lives instead (for example, the vault item name).\n- Do not save things the project's repository already records (code structure, git history, README content). Save the non-obvious context around them instead.\n- If the user's request is ambiguous between updating their brain-level instructions and saving a note, save a note. Only call `instructions-update` when the user explicitly asks to change how their AI behaves, and read the existing instructions first.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}