Client Post Approvals

Client approvals usually live in email threads. A caption gets approved, someone fixes "just one word", and the post that goes out isn't the one the client signed off. Or nobody remembers whether round two was ever approved.

This Claude Code plugin gives approvals a proper trail, using your posts as Markdown files. The request command builds a clean review pack for the client (Markdown, or HTML to email) with each post's platform, date, media, caption and character count, and keeps a copy of exactly what was sent. Paste the client's reply, and Claude records the approvals and logs the change requests. It makes the edits you confirm and shows exactly what changed before the next round. Each approval is tied to a fingerprint (content hash) of the text the client saw, so a version they never saw can't be approved, and any later change is caught by the verify check. A hook locks approved and scheduled posts, and the approval record itself, against edits through Claude. Changing one means reopening it with a reason and sending it back. The status board shows what's waiting on the client and for how long.

Inside: 4 commands (/approval-request, /approval-apply, /approval-status, /approval-reopen), a skill with the rules and file formats, the approvals helper (Node.js, no packages), the locking hook, and three sample posts taken through two rounds, with tested outputs.

For freelance social media managers and small agencies. It uses the same post format as our Content Calendar Manager.

Limitations: it doesn't send email or post to platforms. The hook covers changes made through Claude, and verify catches the rest. It isn't an e-signature.