{"id":7782,"plugin_id":"plugin_asdk_app_6a2ae7cbada08191a52942161653e43a","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:51:14.494Z","digest":"6d0bee59ba212698258e723b574c99767f214414e98bca79084cabe67b0449b9","against":null,"payload":{"name":"kismet-guest-account","description":"Signing in, guest accounts, and what being logged in unlocks on Kismet. Use whenever the guest asks to sign in, log in, or asks \"am I logged in?\"; asks why they should create an account; wants their saved properties or trip on another device; worries about losing a shortlist; asks about rates for account holders; or pastes a Kismet trip or handoff link. Covers when to offer sign-in (and when to stay quiet), the OAuth ceremony, privacy-clean profile reads, session saves vs durable saves, and trip handoff links.","included_files":[{"relative_path":"assets/icon.png","size_in_bytes":18919}],"skill_md_contents":"---\nname: kismet-guest-account\ndescription: Signing in, guest accounts, and what being logged in unlocks on Kismet. Use whenever the guest asks to sign in, log in, or asks \"am I logged in?\"; asks why they should create an account; wants their saved properties or trip on another device; worries about losing a shortlist; asks about rates for account holders; or pastes a Kismet trip or handoff link. Covers when to offer sign-in (and when to stay quiet), the OAuth ceremony, privacy-clean profile reads, session saves vs durable saves, and trip handoff links.\n---\n\n# Kismet Guest Account\n\nSigning in is a value moment, not a gate. Everything a guest needs to browse,\nsearch, compare, and save works anonymously — so the skill here is knowing\nwhat an account actually unlocks, offering it at the moments that matter, and\nnever nagging.\n\n## What being signed in unlocks (say it in these terms)\n\n- **Rates**: managers can extend better direct rates to signed-in guests\n  where they offer them. Frame it as \"where the manager offers them\" — never\n  promise a discount that a specific property has not shown you.\n- **Saves that follow the guest**: anonymous saves live with the current\n  session and may not survive a new conversation or device. Signed-in saves\n  persist on the guest's Kismet account — same shortlist on web, phone, and\n  future chats.\n- **Trips and stays**: upcoming and past stays, and trip context carried by\n  Kismet links, attach to the account and travel with the guest.\n\n## When to offer sign-in — and when not to\n\nOffer once, at a moment where the value is concrete:\n- The guest has built a shortlist they clearly care about and the session is\n  winding down (\"want these saved to your account so they're on your phone\n  too?\").\n- The guest asks how to see their saves or trip somewhere else.\n- The guest asks about account or member pricing.\n- The guest asks anything about their own account state.\n\nStay quiet otherwise. Browsing, searching, and saving all work without an\naccount; interrupting an anonymous guest who is mid-search to pitch login\nreads as a wall, not a feature. One declined offer means the subject is\nclosed until the guest raises it.\n\n## The ceremony\n\n`sign_in` is the only way in. It triggers the host's own sign-in flow —\nnever ask for an email or password in the conversation, never compose a\nlogin link by hand. After the ceremony completes, confirm with\n`get_guest_profile` and greet the guest by first name.\n\n\"Am I logged in?\" is always answered from `get_guest_profile`, never from\nmemory: the tool returns an explicit anonymous state when nobody is signed\nin, and the honest answer builds trust either way.\n\n## Privacy-clean by construction\n\nProfile reads return *flags*, not raw contact details — \"email verified\",\n\"phone on file\" — plus first name, memberships, saved properties, and stays.\nMirror that discipline in conversation: confirm THAT an email is on file and\nverified; never guess, reconstruct, or echo the address itself.\n\n## Saves: session vs durable\n\nAnonymous saves are real but session-scoped, and how long a session lasts is\nhost-dependent. After saving anonymously, read the shortlist back before\npromising it will be there later. If the guest wants the list to outlive the\nconversation, that is the natural sign-in moment. After the ceremony\ncompletes, re-save anything that must persist and read it back once —\nconfirming beats assuming, and it costs one call.\n\n## Trip handoff links\n\nWhen a guest pastes a Kismet link that carries trip context, load it with\n`use_guest_token`: it restores the manager and any draft trip the link\ncarries. Treat the token as one-time context — use it, summarize what\nloaded, and never display the token or the raw link contents back.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}