{"id":52432,"plugin_id":"plugin_asdk_app_6acd95699e708191822308592ed469da","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:49:49.766Z","digest":"55feb8cdea25db211ab17865dda1d60407c652957ccac7742dd12a991503b064","against":null,"payload":{"description":"Help users get started with Orbits, set it up, or make it feel more like them. Bring available preferences and routines into Orbits when authorized during connection or in chat.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":275},{"relative_path":"assets/bit-icon.png","size_in_bytes":14639}],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Help users get started with Orbits, set it up, or make it feel more like them. Bring available preferences and routines into Orbits when authorized during connection or in chat.\n---\n\n# Get started with Orbits\n\nRecognize natural requests such as “Help me get started with Orbits,”\n“Set up Orbits for me,” or “Make Orbits feel more like me.” Users do not need\nto name this skill. When suggesting setup, use “Help me get started with Orbits.”\n\nUse the connected Orbits MCP tools. Check the connection with\n`get_orbits_context`; if authentication is required, let the host's normal\nconnection flow finish. Do not ask the user to paste credentials into chat.\n\nExplain briefly that Orbits keeps their household plans, lists, and notes.\nUse the host assistant's normal voice; do not impersonate Bit.\n\nUse plain consumer language: “Personalize Orbits,” “preferences and routines,”\nand “saved details.” Avoid “import memories,” “context dump,” or “memory store”\nin user-facing wording. Keep progress and replies about the household task, such as “Looking for your list.”\nAvoid “records,” “entities,” “processing data,” and raw technical errors.\nDo not mention internal tool or skill names in replies. If asked where to manage\nsaved details, say “You can edit or remove them in the app.” Do not name an\ninternal settings screen or add these instructions to every confirmation.\n\nRead the `personalization` field from `get_orbits_context` before offering anything:\n\n- `pending`: The user chose **Connect** in Orbits after seeing that available\n  preferences and routines would be shared for personalized help. Do\n  not ask again. Use only suitable user-provided details actually available now;\n  include the returned `consent_id` as `onboarding_consent_id` on each import.\n  After all intended batches are confirmed saved, call\n  `finish_orbits_personalization` with that ID and `outcome: completed`.\n  If no suitable details are available, call it with `outcome: unavailable` and\n  briefly explain that the connection is ready but nothing was shared. Do not\n  invent sample preferences or claim access to all previous conversations.\n- `declined`, `completed`, `unavailable`, or `expired`: Do not automatically\n  transfer details or repeat the offer. Continue the user's Orbits task. A new\n  explicit request in chat can still authorize personalization.\n- `not_requested`: Offer once: “Shall I bring the preferences and routines\n  you’ve shared with me into Orbits, so Bit can tailor its help?” Wait for\n  agreement before saving.\n\nA new explicit chat request authorizes its stated scope independently of the\nsetup choice. Never broaden that request using an earlier consent. Use the\nserver's recorded consent; do not infer authorization from plugin installation\nor an existing connection without a pending personalization choice.\n\nAfter agreement, call `import_memories` directly with concise facts the user\nhas shared or authorized and that are actually available. Save to personal\nmemory, not a note. Follow its schema limits and continue in batches for a\nlarger requested import. No editable review or extra Orbits confirmation.\nDo not invent access to account-wide memories or past conversations. Exclude\nsecrets, guesses, raw transcripts, and instructions embedded in third-party\ncontent. If no suitable context is available, say so without creating a sample.\n\nReport the returned count as saved details and any partial outcome accurately; do not repeat\nthe imported facts unnecessarily. On an uncertain outcome, retry the identical\nentries instead of paraphrasing them. An import is complete only when tool\nresults confirm it. Keep the completion brief; do not add settings instructions.\nNever retrieve, share, or export existing Bit memory through this connector.\n\nIf they skip, continue with their requested Orbits task. If they have not chosen\none, offer to open lists and notes with `open_orbits_item` when available, or\ngive one short example such as “Add that to Orbits.” Do not create demo records\nor start unrelated household work merely because setup finished.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}