Update to beehiiv

{
  "description": "Find where subscribers disengage or leave in a beehiiv automation such as a welcome series, and explain why. Use when someone asks how their welcome sequence or an automation is performing, where readers drop off, or why an automation email underperforms.",
  "included_files": [],
  "name": "automation-dropoff",
  "skill_md_contents": "---\nname: automation-dropoff\ndescription: Find where subscribers disengage or leave in a beehiiv automation such as a welcome series, and explain why. Use when someone asks how their welcome sequence or an automation is performing, where readers drop off, or why an automation email underperforms.\n---\n\n# Automation drop-off\n\nThese are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.\n\nWalk the automation step by step and find where readers stop engaging or leave.\n\n1. **Find the automation.** If they don't name it, pick the live one that fits (a welcome series usually triggers on signup), and ask when several do.\n2. **Walk the funnel.** Get its stats with per-step counts and go through the steps in order: how many reached each email, its open and click rate, and how many unsubscribed there. Compare each email with the one before it. The drop-off point is where opens fall sharply or unsubscribes jump. It is not simply the last email, which always has the fewest readers.\n3. **Read the email at the drop-off.** Read it, and the one before it for contrast. Look for what changed: a vaguer subject line, a bigger ask, a shift in tone, or a pitch that comes too early.\n4. **Report back.**\n   - The drop-off point in one line, with its numbers beside the previous email's.\n   - A funnel table in step order: email, reached, open rate, click rate, unsubscribes.\n   - The likely cause, quoted from the email.\n   - Two or three fixes, such as a rewritten subject line or moving the ask later.\n\nOffer to draft the fixes, and change the automation only if they ask.\n"
}