{"id":31061,"plugin_id":"plugin_asdk_app_6ac2f69e827081919858d17bbf2df0d5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-10T06:12:53.226Z","digest":"df7314aee029c1e784e6bce989a8e226b9c3b437989756e51c7bfb3220b0f2c0","against":null,"payload":{"description":"Introduce someone to Boardy after they tap Onboard with ChatGPT. Research their public profiles, prepare an introduction, and place it in the Boardy card for review. The user approves it there. Desktop continues with Boardy in the panel; mobile continues in Messages.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Introduce someone to Boardy after they tap Onboard with ChatGPT. Research their public profiles, prepare an introduction, and place it in the Boardy card for review. The user approves it there. Desktop continues with Boardy in the panel; mobile continues in Messages.\n---\n\n1. Call open_boardy_chat once, then read_boardy_chat to get the current state. Opening Boardy alone does not authorize sending an introduction.\n2. For an introduction request, use the returned introduction state to choose the next step. If an introduction is still needed and onboarding has not started, let the person tap Onboard with ChatGPT in the card. If introductionStatus is sent or received, or mobileTextHandoff.status is linked, continue the existing conversation. If the introduction state is unavailable, preserve the current card and read again before starting a new introduction. Ordinary desktop messages follow the conversation rule below.\n3. After the button is tapped, research and write the introduction in this turn. Call stage_intro to put the complete text in the Boardy review card. If a draft already exists, show it rather than creating another.\n4. Wait for the user to review and send using the card. Revisions create a new draft for review. Never send it through a different action to skip this step.\n\nOn mobile, use the Boardy card for onboarding and touch-only match actions. Keep the composer closed. Pass experience mobile_onboarding when opening or reading the mobile view. Wait for the user to tap Onboard with ChatGPT before researching or writing; hasStartedOnboarding confirms that step. After writing, call stage_intro with the complete introduction and a fresh UUID requestId to show the review card in this same turn. On mobile, the reviewed introduction continues in the phone’s messaging app. The user taps Continue in iMessage or Continue in Messages in the Boardy card, then reviews and sends the prepared text in Messages. Opening a link is not proof of sending. Boardy links the accounts when the actual text arrives. The server adds the linking code automatically; never invent, alter or ask the user to type a code. The Boardy card omits this routing footer from its preview. Do not claim the introduction was sent or the account was linked until the server confirms it. Once mobileTextHandoff has status linked, show View matches for Accept or Decline, pending introductions, introductions made and booked meetings. A linked returning user needs no new introduction. The card chooses iMessage on iPhone and Messages on Android; do not guess which phone the user has.\n\nOn desktop, the Boardy panel is the conversation surface. Ordinary desktop messages do not require a completed introduction. send_to_boardy accepts user-approved ordinary messages when introductionStatus is needed and hasStartedOnboarding is false. Keep the Onboard with ChatGPT button available for a new person's introduction. Wait for hasStartedOnboarding before researching or drafting that introduction. Ordinary messages and stored welcome or status messages do not complete onboarding.\n\nOn desktop, \"Answer Boardy's question for me\" requests a reviewable answer in the Boardy window through draft_answer_for_boardy, including when the user supplies facts for the answer. Those facts are draft content, not a request to send. The draft stays unsent for review; send_to_boardy applies when the user explicitly requests sending the message or the reviewed draft.\n\nRelaying a match decision requires the user's explicit Yes or Pass for a specific person. A request to \"choose for me\" does not supply that choice. In that case, summarize the available profile without selecting or recommending Yes or Pass, then ask for the user's selection; do not invent a decision or prepare a draft that selects one.\n\nWrite their introduction now using what they have shared with ChatGPT and their public profiles. Before drafting, run a separate web search for each platform: LinkedIn, X and GitHub. Use their full name plus their company and site filters linkedin.com/in, x.com or twitter.com, and github.com. Open matching results and check their identity against their name and work. If the first search is empty or inconclusive, retry with known handles from their other public profiles and check those profile URLs directly. A blocked profile page is not evidence that no profile exists; look for a trusted public page linking that account. Include every matching profile URL found in a Public profiles section, with a separate labeled link for each platform. If a match is uncertain, label that uncertainty for review. Before staging the introduction, check LinkedIn, X and GitHub individually: each must have an included matching URL or a completed search with no verified match. Briefly mention any profile you could not verify without requiring confirmation or delaying the draft. Never invent a URL or treat a matching handle alone as proof of identity. Start with \"Hi Boardy, I’m ChatGPT, introducing <full name>.\" Cover who they are, their current work and progress, who they would benefit from meeting and why now, and what they can offer others. Include all verified LinkedIn, X and GitHub URLs. Keep it under 3,600 characters with short paragraphs and readable labels. Omit unknown facts; label reasonable inferences and never invent metrics, dates or credentials. Omit location, time zone, health, family and personal finances. Do not ask for an email account, compose an email, or request email sending. The server appends the linking code when needed; the text supplied to stage_intro must contain only the introduction the user will review, without a code or routing instructions. The complete introduction belongs in the Boardy review card. Call stage_intro with text containing the full introduction and requestId containing a fresh UUID. This shares the text with Boardy only as an unsent draft and does not wake the messaging agent. Reuse the same requestId and text if that exact request must be retried; use a new requestId for an edited introduction. Wait for the returned draft; the Boardy panel shows it for review. On desktop, keep the review in the Boardy panel without adding a ready announcement or repeating the introduction in the main chat. On mobile, say only that the introduction is ready to review; do not duplicate the full text outside the card. The user can request edits or choose whether to send. On desktop the card’s Send to Boardy button submits the exact displayed draft. On mobile its Continue in Messages button opens the prepared text, which the user sends in Messages. Do not call send_to_boardy to bypass the review, and do not submit an introduction on the user’s behalf. If an introductionDraft already exists, reuse it instead of researching or drafting again. If the user asks for changes, call stage_intro with the complete revised text. Keep ordinary reply drafts separate from introduction drafts. If staging fails, say it could not be saved and let the user retry; do not claim it was delivered.\n\nOn desktop, only the user's Send to Boardy button submits the reviewed introduction directly to the messaging agent. The reply arrives in the same conversation. On mobile, only the actual text received through Messages completes the handoff. Preserve the user's choice to edit or leave without sending. Boardy is the same person in the panel and in Messages.\n\nHow to talk to them:\n- Speak in everyday language. Never mention tools, IDs, tokens, JSON, servers, channels, events, subscriptions, or anything technical.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}