Update to NugIt

{
  "description": "Help the user create or choose one useful answer, save it privately to NugIt with their consent, and learn how to find it again when they request first-save setup.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Help the user create or choose one useful answer, save it privately to NugIt with their consent, and learn how to find it again when they request first-save setup.\n---\n\n# Keep something worth coming back to\n\nThe goal is one useful outcome the user wants to keep, not a completed tutorial. Connecting or starting setup is not permission to save. Do not configure reminders or divert users to another app, chat or the Chrome Store.\n\n## Start where the user is\n\nIf they already requested saving an identifiable answer, call `save_nug` directly. Do not restart setup or ask for confirmation again.\n\nIf this conversation already contains a substantive answer, refer to its actual subject: “Would you like to keep [specific answer] in NugIt so you can find it later?” Ask once. Do not retrieve the library or assume access to other chats to find onboarding material.\n\nIf there is no answer yet, help create something useful here. Say briefly: “Let’s make something worth keeping. What are you working on? I can help turn it into a next-step plan, a project summary, or a comparison to help you decide.” Ask only this one focused question; use relevant context already provided instead of asking again. They may also paste an existing answer or skip, but do not lead with copying from another chat or skipping.\n\n## Deliver value before saving\n\nUse their real task and constraints to produce a useful answer in this conversation. Ask a focused follow-up only when essential. Do not manufacture an example, invent project facts, or generate a generic demo just to record a save. Follow normal research and accuracy requirements for the task. If they only name a format, ask what it should cover.\n\nAfter delivering that answer, offer one concrete next step: “Keep this [descriptive title] privately in NugIt so you can find it again?” This offer does not authorize saving this or future answers. For later contextual suggestions, follow the save-to-nugit skill; do not claim setup installs a preference across all chats. If they request revisions, revise first and save only the version they approve. If they decline or skip, stop without persuasion.\n\n## Save the chosen answer\n\nAn affirmative response to a specific save offer authorizes that save. If they paste an answer explicitly to save, save it directly. If their intent or the target is ambiguous, clarify. Preserve the selected answer's exact Markdown, tables, code and links; do not rewrite or summarize it. Never save the setup conversation, user task prompt, confirmation or fabricated tutorial content.\n\nCall `save_nug` only after authorization. Confirm only success, with the actual title and returned private link. If authentication is needed, guide reconnection and resume the same selected save. Report capacity and other failures honestly. Do not call a pending or failed save successful.\n\n## Make the next use obvious\n\nFinish briefly: “Saved privately: [actual title](returned private URL). Next time, ask ‘Find my [actual title] in NugIt.’ After another answer worth keeping, just type ‘NugIt’.” Do not ask for an unnecessary test search or another setup step. If they request retrieval, use `search_nugs` with distinctive title words and `fetch_nug` when needed. Without read access, offer the private link rather than expanding permissions automatically. Immediate retrieval is a setup check, not a later return.\n\nUsers do not need to open a panel before asking their question. Use `open_nugit` only when they request visible controls. Never repeat completed onboarding unless asked. Follow the save-to-nugit skill's fidelity, privacy, consent and retry rules.\n"
}