Misar AI v1.1.1
Write and publish blog posts
Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
From the marketplace listing
Misar.Blog lets you write, publish and grow a blog from ChatGPT. Draft and edit articles, publish now or schedule for later, organise posts into series, research topics, generate SEO-friendly titles and cover images, and review comments, reactions, newsletter subscribers and traffic. It is built for writers, creators and teams who publish on Misar.Blog. A Misar.Blog account is required, and the plugin only changes articles owned by the signed-in account.
Language: English · Automatically detected from descriptions.
Oct 27, 2026 · 1 saved observations
Metadata · Oct 27, 2026 · 00:52 UTC · Compared with Oct 24, 2026 · 13:45 UTC
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Oct 24, 2026 · 13:45 UTC
Not present
Oct 27, 2026 · 00:52 UTC
false
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 3, 2026.
Review scenarios; not an exhaustive list.
Misar.Blog does not sell products or process payments through the plugin.
Terms may have changed since this observation.
Write a complete, SEO-optimised article draft and save it.
--- name: blog-analytics-report description: Report on Misar.Blog performance — views, revenue, subscribers, engagement. Use for "how is my blog doing", traffic reports, or content performance analysis. --- # Blog performance report ## Gather - `get_analytics_summary` — views, revenue, subscribers over a window - `list_my_articles` (`status=published`) — what is live - `get_reactions` on top articles — engagement beyond raw views - `list_newsletter_subscribers` — audience growth ## Interpret Views alone say little. Useful framings: - **Views per article**, not just total — total rises simply by publishing more. - **Which topics** earn views, so the next piece is informed rather than guessed. - **Reactions relative to views** — a high-view, low-reaction piece usually means the title over-promised. - **Subscriber growth against publishing cadence** — the honest test of whether the writing converts readers. ## Structure Headline numbers; best and worst article each with a one-line reason; audience growth; then the single highest-impact action for next month. Under 400 words. State plainly when a figure was unavailable — never estimate and present it as measured. ## Next steps Ground recommendations in the data: if one topic outperforms, suggest a series (`manage-article-series`). If a strong piece underperforms on views, that is an SEO problem (`seo-optimize-article`), not a writing problem.
--- name: manage-article-series description: Plan and manage a multi-part article series on Misar.Blog. Use for "series", "multi-part", "part 2", or organising related posts into a sequence. --- # Manage an article series ## Check first `get_series` — the user may already have a series this belongs in. Creating a second series on the same theme splits the reader journey and the internal linking value across both. `list_my_articles` — existing posts often become parts of the series. Adding them is better than rewriting them. ## Design Each part must stand alone (readers arrive mid-series from search) while building on the last. For each part give a title, a one-paragraph summary, and what the reader can do afterwards. 4–7 parts is the practical range. Longer series lose readers before the payoff. ## Build 1. `create_series` with the name and description. 2. `add_to_series` for each article, with an explicit position — order is what makes it a series rather than a tag. Add existing articles before drafting new ones, so the gaps are visible. ## Do not Draft every part up front unless asked. Publish one, see how it performs with `get_analytics_summary`, then adjust the rest.
--- name: newsletter-campaign-report description: Draft and review Misar.Blog newsletter issues and subscriber performance. Use for "newsletter", "email my subscribers", or newsletter performance questions. --- # Newsletter issues and performance ## Drafting an issue 1. `list_my_articles` (`status=published`) for the articles to feature. 2. `list_newsletter_issues` to match the structure and voice of past issues — subscribers notice a format that suddenly changes. For each featured article write a two-sentence hook that earns the click, using its **real** URL from the API. Open with a short personal intro; close with one call to action, not several. If fewer articles are available than requested, say so rather than padding the issue with filler. ## Reviewing performance - `list_newsletter_issues` — what has been sent - `list_newsletter_subscribers` — audience size and growth - `get_analytics_summary` — revenue and traffic context Compare issues against each other rather than against generic benchmarks: a newsletter's own baseline is the only meaningful reference for whether an issue landed. ## Do not Fabricate open or click figures for an issue. Report only what the API returns, and name what is missing.
--- name: promote-article description: Write platform-specific promotional copy for a Misar.Blog article. Use for "share this post", "social caption", "promote my article", or writing X/LinkedIn/Reddit copy. --- # Promote an article ## Read it first `get_article` by slug. Captions written from the title alone are the reason most promotional copy reads interchangeably. ## Write per platform, not once Each platform punishes copy written for a different one: - **X/Twitter** — under 280 characters, hook in the first line, link last. No hashtag stuffing. - **LinkedIn** — longer, first person, line breaks between short paragraphs. Lead with the insight, not the announcement. - **Reddit** — conversational and genuinely non-promotional, or it gets removed and the account penalised. Recommend a relevant subreddit and its rules, and say clearly when self-promotion is not welcome there. Always use the article's real URL from the API. ## Amplify - `get_reactions` — a post already resonating is the one worth promoting again. - `list_newsletter_issues` — feature it in the next issue rather than only posting socially. - `get_follow_status` when the user is considering outreach to another creator. ## Do not Claim engagement numbers, endorsements, or coverage that did not happen.
--- name: publish-blog-post description: Write, draft, and publish an article on Misar.Blog. Use when the user wants to write a post, publish an article, save a draft, or turn notes into a blog post. --- # Publish a blog post ## 1. Ground the piece before writing - `list_my_articles` — match the author's existing voice, and avoid re-covering a topic they have already published. - `search_articles` — check what already exists platform-wide on the subject, so the piece has an angle rather than duplicating someone else's. - `research_topic` — gather angles and sources. Writing before doing this produces generic output that reads like every other post on the topic. ## 2. Draft `create_draft` with `title`, `body_markdown`, and `tags`. - Markdown with `##` headings and short paragraphs. - Open with a direct answer to the question the title poses — this is what makes a piece quotable by AI answer engines and eligible for featured snippets. - 3–8 tags. More dilutes rather than broadens reach. **Show the draft and wait for approval before saving.** Never publish in the same step as writing. ## 3. Title and cover - `suggest_titles` / `generate_title_seo` for candidates. Keep under 60 characters so it is not truncated in search results. - `generate_cover_image` for a cover. Describe the subject concretely; abstract prompts produce unusable stock-feeling images. ## 4. Publish `publish_article` makes it public — get explicit confirmation first. Pass `schedule_at` to schedule instead. Use `update_article` for edits after the fact rather than creating a duplicate. ## Do not - Invent statistics, quotes, or sources. If `research_topic` did not surface it, do not assert it. - Publish without the user seeing the final text.
--- name: seo-optimize-article description: Audit and improve an existing Misar.Blog article for SEO, AEO, and AI-answer-engine citability. Use for "improve SEO", "why isn't this ranking", "meta description", or "optimise for AI search". --- # Optimise an article ## Read the actual article first `get_article` by slug. Auditing from the title alone produces generic advice that applies to any post and helps none. ## Audit Report an SEO score out of 100 **with the reasoning**, then: - **Keywords** the piece should rank for but never mentions. - **Title** — rewritten, under 60 characters, keyword near the front. - **Meta description** — rewritten, under 155 characters, written to earn the click rather than to summarise. - **Internal links** — use `search_articles` to find *real* published articles to link to. Never invent a URL; a broken internal link is worse than none. - **Structure** — headings that pose the question a reader searched for. ## AI answer engines (AEO/GEO) Distinct from classic SEO and increasingly where the traffic goes: - Answer the title's question directly in the first paragraph. Engines quote self-contained passages; a piece that builds to its answer never gets cited. - Keep each section independently comprehensible — a passage lifted out of context must still make sense. - Use concrete specifics (numbers, versions, dates). Vague claims do not get quoted. ## Apply `update_article` — but ask before changing anything. A title change on a ranking article can lose position, so flag that trade-off explicitly when the article already gets traffic.
Adds the Misar task skills, OAuth sign-in, and updated branding.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 3, 2026.
plugin_asdk_app_6ac4ed001d5c81918f6023c403630e67
Download plugin data (JSON)