Update to Misar.Blog

{
  "description": "Draft and review Misar.Blog newsletter issues and subscriber performance. Use for \"newsletter\", \"email my subscribers\", or newsletter performance questions.",
  "included_files": [],
  "name": "newsletter-campaign-report",
  "skill_md_contents": "---\nname: newsletter-campaign-report\ndescription: Draft and review Misar.Blog newsletter issues and subscriber performance. Use for \"newsletter\", \"email my subscribers\", or newsletter performance questions.\n---\n\n# Newsletter issues and performance\n\n## Drafting an issue\n\n1. `list_my_articles` (`status=published`) for the articles to feature.\n2. `list_newsletter_issues` to match the structure and voice of past issues —\n   subscribers notice a format that suddenly changes.\n\nFor each featured article write a two-sentence hook that earns the click, using\nits **real** URL from the API. Open with a short personal intro; close with one\ncall to action, not several.\n\nIf fewer articles are available than requested, say so rather than padding the\nissue with filler.\n\n## Reviewing performance\n\n- `list_newsletter_issues` — what has been sent\n- `list_newsletter_subscribers` — audience size and growth\n- `get_analytics_summary` — revenue and traffic context\n\nCompare issues against each other rather than against generic benchmarks: a\nnewsletter's own baseline is the only meaningful reference for whether an issue\nlanded.\n\n## Do not\n\nFabricate open or click figures for an issue. Report only what the API returns,\nand name what is missing.\n"
}