Update to beehiiv

{
  "description": "Analyse how a beehiiv newsletter's recent posts performed and explain what drove the difference, especially subject lines. Use when someone asks how their newsletter or posts are doing, which subject lines or topics worked best, wants a performance report for a period, or asks what to write next or for a content calendar.",
  "included_files": [],
  "name": "performance-report",
  "skill_md_contents": "---\nname: performance-report\ndescription: Analyse how a beehiiv newsletter's recent posts performed and explain what drove the difference, especially subject lines. Use when someone asks how their newsletter or posts are doing, which subject lines or topics worked best, wants a performance report for a period, or asks what to write next or for a content calendar.\n---\n\n# Newsletter performance report\n\nThese are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.\n\nTell the publisher which posts worked, why, and what to do next, using only their own numbers.\n\nFind the publication first. If the account has several and the request doesn't say which, ask. List the published posts in the period (default: the last 30 days, or the last ten sends if that is sparse), fetch their stats, and get publication-level stats as the baseline.\n\nJudge subject lines by open rate and content by click rate. Compare each post with the publication's own average rather than industry benchmarks, because audiences differ too much for outside numbers to mean anything. With fewer than five sends, say the sample is too small to call a pattern.\n\nLook across the strongest and weakest posts for what separates them: subject line shape (numbers, questions, specificity, length), topic, and format. Name a pattern only when at least two posts support it.\n\nShape the answer like this:\n\n- A one-line headline with the single most useful finding.\n- A table of posts sorted best first: subject, send date, open rate, click rate.\n- Two to four patterns, each naming the posts that show it.\n- Two or three concrete next steps, such as a weak subject line rewritten in the winning style.\n\nWhen they ask what to write next, or for a content calendar, turn the next steps into a dated plan at their usual cadence, inferred from recent send dates. Check scheduled and draft posts first so the plan doesn't duplicate work already under way. Give each issue a date, a working title, a subject line in the style of their best performers, and the past post or pattern it builds on. Include one clearly labelled experiment so they keep learning.\n\nQuote every figure exactly as the tools return it.\n"
}