Update to Misar.Blog

{
  "description": "Report on Misar.Blog performance — views, revenue, subscribers, engagement. Use for \"how is my blog doing\", traffic reports, or content performance analysis.",
  "included_files": [],
  "name": "blog-analytics-report",
  "skill_md_contents": "---\nname: blog-analytics-report\ndescription: Report on Misar.Blog performance — views, revenue, subscribers, engagement. Use for \"how is my blog doing\", traffic reports, or content performance analysis.\n---\n\n# Blog performance report\n\n## Gather\n\n- `get_analytics_summary` — views, revenue, subscribers over a window\n- `list_my_articles` (`status=published`) — what is live\n- `get_reactions` on top articles — engagement beyond raw views\n- `list_newsletter_subscribers` — audience growth\n\n## Interpret\n\nViews alone say little. Useful framings:\n\n- **Views per article**, not just total — total rises simply by publishing more.\n- **Which topics** earn views, so the next piece is informed rather than guessed.\n- **Reactions relative to views** — a high-view, low-reaction piece usually\n  means the title over-promised.\n- **Subscriber growth against publishing cadence** — the honest test of whether\n  the writing converts readers.\n\n## Structure\n\nHeadline numbers; best and worst article each with a one-line reason; audience\ngrowth; then the single highest-impact action for next month.\n\nUnder 400 words. State plainly when a figure was unavailable — never estimate\nand present it as measured.\n\n## Next steps\n\nGround recommendations in the data: if one topic outperforms, suggest a series\n(`manage-article-series`). If a strong piece underperforms on views, that is an\nSEO problem (`seo-optimize-article`), not a writing problem.\n"
}