← beehiivCONTENT HISTORY

Update to beehiiv

Snapshot Oct 24, 2026 · 12:58 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save beehiiv and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Edit, tighten, or rewrite a beehiiv post in the publication's own voice, or turn notes, a transcript, or an outline into a new draft. Use when someone wants a post shortened, restructured, proofread, rewritten, repurposed, or drafted from source material.",
  "included_files": [],
  "name": "edit-post",
  "skill_md_contents": "---\nname: edit-post\ndescription: Edit, tighten, or rewrite a beehiiv post in the publication's own voice, or turn notes, a transcript, or an outline into a new draft. Use when someone wants a post shortened, restructured, proofread, rewritten, repurposed, or drafted from source material.\n---\n\n# Edit a post\n\nThese are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.\n\nLeave the publisher with a better draft that still sounds like them, and a clear account of what changed.\n\n1. **Find the post.** If they don't name it, check recent drafts, and ask when more than one fits.\n2. **Learn the voice.** Skim two or three recent published posts: how they open, how they sign off, how sections are labelled, and how long paragraphs run. Keep their recurring openers, sign-offs, and section labels word for word, because readers recognise them.\n3. **Edit.** Change only what the request needs and leave strong blocks alone, so the publisher's own sentences survive. Read the post again right before you change it, so the edit uses the current version; stale content causes errors. When a draft feels long, the usual culprits are throat-clearing intros, hedges, and asides, so cut those before cutting substance.\n4. **Drafting from source material:** use the structure their posts already follow and take facts only from the source. Mark anything you would have to invent as `[TK: what's needed]` for them to fill in.\n5. **Report back.** List what you changed and why, give the old and new word counts, and link the draft in the editor. Say plainly that it is still a draft and that they publish it from beehiiv.\n"
}

SHA-256 of public snapshot: 1b2cf5140d8b3722cfc68bf5ab08a54dc69ff20291dba344f74b8334f7af3dfc