{"id":104944,"plugin_id":"plugin_asdk_app_6ac01d33dd60819180f383d3c94a9546","kind":"skill","collection_source":"skill_api","comparison_source":null,"observed_at":"2026-11-19T01:34:38.281Z","digest":"5b869f5746db1b74d95c5377feda3b0cee57721010cb9da8ba2ef39c5f7e86f0","against":null,"payload":{"description":"Save something to the user's Dexi notes. Use when the user wants to save, capture, note down, or remember something — a finding, decision, code snippet, summary, or link — or says \"add this to Dexi\" / \"save that to my notes\".","included_files":[],"name":"dexi-capture","skill_md_contents":"---\nname: dexi-capture\ndescription: Save something to the user's Dexi notes. Use when the user wants to save, capture, note down, or remember something — a finding, decision, code snippet, summary, or link — or says \"add this to Dexi\" / \"save that to my notes\".\n---\n\n# Capture to Dexi\n\nSave the current finding, decision, or content the user pointed at as a Dexi note using the Dexi MCP `create_note` tool. If the user said what to capture, that is the content; otherwise capture the conclusion of the current conversation.\n\nHow to write the note:\n\n1. **Distill, don't dump.** A note should be the useful conclusion, not a transcript. For a debugging finding: the symptom, root cause, and fix. For a decision: what was decided and why. For research or a meeting: the takeaways, not the play-by-play. Short excerpts or code snippets are fine when they're the point; never paste pages of material.\n2. **Title**: a short, specific noun phrase the user could find again later (e.g. \"Railway healthchecks probe PORT, not the domain target port\").\n3. **Tags**: write 1–3 relevant `#hashtags` inline in the body — Dexi parses them into tags automatically. Reuse the user's existing vocabulary when known (call `list_tags` if unsure rather than inventing near-duplicates).\n4. **Body**: plain text. `[[Wiki Links]]` to related note titles are supported and encouraged when you know a related note exists.\n5. **Properties**: when the note has structured facts the user might filter on later (a status, a rating, a due date, an author), write them as `key:: value` lines at the start of the body — `status:: reading`, `due:: 2026-09-10`, `rating:: 4`. Dexi parses them into typed properties that bases can filter and sort. Reuse keys the user already has (`query_base`/`list_bases` show them) rather than inventing near-duplicates.\n\nCall `create_note` with the title and body. Then confirm to the user with the note title and its link: `https://app.dexi.net/dashboard/notes/<id>` (using the `id` from the tool result).\n\nBoundaries: create exactly one note per request, never edit or delete existing notes from this skill, and don't invent facts the conversation didn't establish. If `create_note` fails because the note limit was reached, relay the message to the user — don't retry.\n\nOn every Dexi tool call, pass the optional `intent` argument: one short sentence on what you are doing for the user (e.g. \"recall saved research on transformers\"). It never changes behavior — Dexi uses it in aggregate to improve the tools. Keep personal details out of it.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}