NugIt

View saved version →

---
name: save-to-nugit
description: Use for reusable travel itineraries, trip plans, day-by-day schedules, website or project launch plans, team roles and handovers, recipes, comparisons, project summaries, message templates, checklists, technical solutions, researched recommendation shortlists, settings tables or practical reference explanations, project recaps with decisions, blockers and next actions, reusable prompts or workflows, and short personalised lists worth returning to. Complete the requested answer first, then consider one named private NugIt save offer under the eligibility and consent rules below; the user need not mention saving or NugIt. Also use for explicit saving and finding saved Nugs. Exclude trivial facts, casual chat and unfinished answer drafts.
---

# Save and reuse with NugIt

## Recognise useful answers worth keeping

After completing a self-contained answer with clear reuse value, you may offer once to save that named answer privately to NugIt, even when the user has not mentioned NugIt. Keep the existing categories: travel itineraries, trip plans, day-by-day schedules, website and project launch plans, team plans with roles and handovers, recipes, project summaries, decision comparisons, reusable message templates, checklists and technical solutions. Also recognise:

- Researched recommendation shortlists with useful selection reasons or constraints.
- Settings tables and practical reference explanations the user can consult again.
- Project recaps containing decisions, blockers and next actions.
- Reusable prompt templates and repeatable workflows.
- Short personalised lists worth returning to, such as a tailored watchlist or shortlist.

Judge reuse value, not length: a short tailored list can qualify while a one-line generic fact does not. A completed project recap or troubleshooting checkpoint can qualify even when the underlying work is ongoing; do not require the whole project to be finished. A reusable prompt produced as the requested answer is eligible content, distinct from the user's original task prompt or instructions to this plugin.

 Finish the requested task first; do not manufacture content to create a save opportunity. Use one short sentence, such as “Would you like to save [specific title] privately to NugIt so you can find it later?” Do not offer for short facts, casual chat, unfinished answer drafts, troubleshooting exchanges without a completed reusable checkpoint, tool confirmations, already-saved content, or discussions about developing NugIt itself. Do not append an offer to every answer. Never repeat an unanswered offer for the same item. If the user declines, do not offer again for that item or its revisions; if they ask to stop suggestions, stop for the rest of the conversation. Respect other named destinations. An offer is not consent: do not call save_nug, transmit the candidate content, or open a panel just to make the suggestion. A clear affirmative response to the named offer authorizes saving that specific answer; a revision request does not. Save only the accepted version, excluding the offer itself. Do not claim this preference persists across chats or configure reminders.

## Save only on consent

Use `save_nug` for an explicit request to save identified content in NugIt. A standalone “NugIt” (case-insensitive, with optional terminal punctuation) immediately after one identifiable useful assistant answer is an explicit request to save that answer privately. No prior plugin invocation or shortcut setup is required. Call save_nug directly, not open_nugit or a preview. Exclude user messages, setup instructions and tool confirmations. If the target is missing or ambiguous, ask which answer to save. A mention of NugIt within a question, repository discussion or another sentence is not this shortcut. Respect other destinations and distinguish saving from personal memory preferences.

Preserve the selected answer or excerpt faithfully as Markdown, including tables, co

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: setup
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.
---

# Keep something worth coming back to

The 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.

## Start where the user is

If they already requested saving an identifiable answer, call `save_nug` directly. Do not restart setup or ask for confirmation again.

If 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.

If 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.

## Deliver value before saving

Use 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.

After 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.

## Save the chosen answer

An 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.

Call `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.

## Make the next use obvious

Finish 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.

Users 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.