Update to beehiiv

{
  "description": "Audit a new beehiiv publication, show what is set up and what is missing, and finish the setup the publisher picks. Use when someone has just signed up, has a new publication, or asks how to get started or set up their newsletter.",
  "included_files": [],
  "name": "onboarding",
  "skill_md_contents": "---\nname: onboarding\ndescription: Audit a new beehiiv publication, show what is set up and what is missing, and finish the setup the publisher picks. Use when someone has just signed up, has a new publication, or asks how to get started or set up their newsletter.\n---\n\n# Onboard a new publication\n\nThese are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.\n\nTake a new publication from sign-up to ready for its first send, doing only what the publisher chooses.\n\n1. **Audit first, change nothing.** Find the publication, and ask which one if there are several. Check the workspace's plan before anything else, because several write tools need a paid plan and knowing that up front beats finding out from a failed call. Then check what is set up and what is missing: name, description, tags, sender and email settings; a first post, drafted or published; logo, brand colours and site theme; welcome email automation; subscribe form; website pages; subscriber count; the author profile; the referral program and recommendations; paid tiers. If they already publish elsewhere, moving their existing posts in is an item too. A custom domain, a custom sending domain, and a subscriber import cannot be done through the tools, so mark them \"do it in beehiiv\" and link the step-by-step help article for each, found with the documentation search, with `?utm_source=mcp&utm_medium=skill` added to the link. Never pretend to do them.\n2. **Show one checklist.** Give a single table grouped into \"Should do now\" (what a newsletter needs before its first send, in this order: settings, subscriber import if they are moving from another platform, logo, subscribe form, website, welcome email, first post) and \"Can do later\". The subscribe form and website come before the first post because they bring in the first readers. Columns: item, status (done, missing or partly), and who does it (I can do it here, needs a paid plan, or do it in beehiiv). Keep it short enough to scan.\n3. **Let them choose.** Stop and ask which items they want done. Change nothing in the account until they pick.\n4. **Do only what they picked.** Ask only for facts the account cannot supply, such as their niche, audience, send cadence, or a site URL to take branding from. Anything that emails readers stays a draft: automations stay inactive and posts stay as drafts. Report what changed, with a link to where they can review each item. If you drafted a welcome email, state plainly that it stays off and sends nothing until they turn it on in the beehiiv automation editor.\n\nSome failures are expected:\n\n- A plan gate is correct behaviour. Mark that item \"needs a paid plan\" once and move on. Never retry it.\n- Before you edit a post's content, read it again so the edit uses the current version. Stale content causes errors.\n- On a website built with the simple builder, some site tools are not available yet. Say so, and leave the website items for beehiiv.\n"
}