{"id":67650,"plugin_id":"plugin_asdk_app_6ac8f4f887188191acc526c51e00ec74","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T13:10:19.303Z","digest":"7c685dfbf17c97977fbf35a9c046ca05ed87559113a092390de2a764a7bf073e","against":null,"payload":{"description":"Distill a useful thought from the current conversation into a self-contained nugget, propose it, and save it as an ordinary Record when requested. Use for a meaningful distinction, connection, changed perspective, or open question worth revisiting. Direct text or voice capture preserves the user's input instead.","included_files":[{"relative_path":"references/proposing-and-saving.md","size_in_bytes":1250},{"relative_path":"references/writing-insights.md","size_in_bytes":1335}],"name":"capturing-insights","skill_md_contents":"---\nname: capturing-insights\ndescription: Distill a useful thought from the current conversation into a self-contained nugget, propose it, and save it as an ordinary Record when requested. Use for a meaningful distinction, connection, changed perspective, or open question worth revisiting. Direct text or voice capture preserves the user's input instead.\n---\n\n# Preserve thoughts that can be taken further\n\nKeep a thought that could support future thinking, whether it came from either participant or emerged between them. A conversation need not produce a nugget, and a proposal must not become a routine ending.\n\nWhen the user explicitly selects this skill without additional task text, propose useful nuggets from the available conversation. If it does not support a useful nugget yet, say so briefly rather than inventing one. This entrypoint contains the ordinary writing, proposal and saving workflow; the references below are optional detail.\n\n## Select and write\n\nChoose a useful distinction, connection, changed perspective, or question worth returning to. Let the present concern guide the choice. Do not extract every fact, summarize the entire exchange, or manufacture a lesson or consensus to conclude it.\n\nWrite the thought itself in the conversation's language, usually as a few connected sentences with enough context to stand alone. Keep the concrete image, example or tension that makes it meaningful. Avoid a transcript of who said what, a mandatory first-person voice, or a report about having reached an insight.\n\nPreserve qualifications and uncertainty in the nugget itself. Distinguish coexistence from causation and possibilities from necessary conditions. Do not add facts, intensity, frequency, motives, permanent traits or agreement that the conversation does not support. Before proposing or revising, compare the wording with the conversation and restore any lost qualification. An imaginative connection can remain a possibility.\n\nPlain paragraphs need no additional skill. For a title, lists, diagrams or other structure, use `formatting-records`. A title is optional. The proposed body is the exact future Record; saving accepted wording does not require another editorial pass.\n\n## Propose or save\n\nIn built-in Goodterm chat, submit the exact proposed Markdown through `propose_action` with `actionType: \"SAVE_NUGGET\"` and `payload: { version: 1, content }`. A short `reason` is optional. It appears as its own interaction entry after the answer completes; it is not part of the response text. Do not write `goodterm-insight` fences, repeat the nugget in prose or ask a second yes/no question.\n\nThe user can approve or reject that exact proposal. Approval saves an ordinary Record once, independently of permanent creation permission. A pending proposal or agreement with a thought is not permission to save it. Never claim approval yourself. To revise a pending proposal after a conversational request, use its server-supplied `supersedesRequestId`; old wording and decisions remain in history. Revising a proposal does not save it. The current card offers Save and Discard; do not direct the user to a separate Regenerate button.\n\nAn explicit saving request permits direct use of `create` when creation permission is enabled. Otherwise offer the exact text through `propose_action`. Preserve requested or accepted wording; report success only after the write succeeds. Do not recreate an already applied proposal, even if its target Record has been deleted.\n\nIn external clients without the card renderer, offer the proposed wording as readable chat text and briefly ask whether to save it, unless saving was already requested. Use that client's Record creation tool and actual author identity; built-in proposal references are unavailable there. Change an existing Record only when requested. Saving does not require a collection-wide search or read permission; existing write permissions still apply.\n\n## Optional detail\n\n| Reference                                                                | When to read it                                                                            |\n| ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ |\n| [references/writing-insights.md](references/writing-insights.md)         | Concrete examples would help preserve an image, distinction or uncertainty while revising. |\n| [references/proposing-and-saving.md](references/proposing-and-saving.md) | Explaining approval entries, revisions, saved state or differences between clients.        |\n\nLoad a reference with `use_skill({ name: \"capturing-insights\", resource: \"references/writing-insights.md\" })`, substituting its exact path only when needed. Product purpose belongs to `about-goodterm`; interface help belongs to `goodterm-docs`. This workflow uses the conversation; it does not independently scan the user's collection or change direct capturing.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}