Post Drafting

skill

Draft platform-tailored social posts from a brief and deliver them as a file with a summary.

Download .md

Post Drafting

Draft platform-tailored social posts from a creative brief and deliver them to the requester as a saved file with a concise summary.

When to use

  • A human or another agent hands you a content brief (topic, audience, goal) and asks for social copy.
  • You need to produce multiple platform variants (e.g. LinkedIn, X, Instagram caption) from one brief.
  • A campaign or launch requires ready-to-review post drafts rather than published content.

Tools

  • read-file - load the brief, prior drafts, or brand-voice reference material before writing.
  • write-file - save the finished post drafts as a file for the requester to review.
  • complete-task - close out the task with a structured summary once the drafts are saved.

Playbook

  1. read-file the brief and any supporting reference material (brand voice notes, prior post examples, campaign goals).
  2. Identify the target platforms and their constraints (character limits, tone, hashtag conventions, link handling) from the brief.
  3. Draft one post variant per requested platform, matching each platform's voice and length norms while keeping the core message consistent across all variants.
  4. Include a clear call to action in each draft where the brief calls for one.
  5. Add a short header to the draft file naming the brief, the platforms covered, and the date.
  6. write-file the complete set of drafts to a single file, clearly labeled by platform so the requester can copy each one independently.
  7. Re-read the saved draft with read-file to confirm the content persisted correctly before closing the task.
  8. If the brief asks you to publish, schedule, or update an existing live post, that is a human handoff: draft the copy anyway, save it with write-file, and note in the summary that publishing requires manual action — never claim the post went live.
  9. complete-task with a summary listing the platforms covered, the file path, and any open questions about tone or messaging that need human input.

Failure modes

  • Brief is missing key details (audience, goal, platform) -> draft your best interpretation, flag the gaps explicitly in the complete-task summary, and ask the requester to confirm.
  • write-file fails or the file cannot be re-read -> retry once, then complete-task as blocked rather than silently dropping the drafts.
  • Platform requirements conflict with brief instructions (e.g. copy exceeds a platform's character limit) -> trim to fit and note the edit in the summary rather than submitting copy that would be rejected.
  • Requester asks you to publish or edit a live post -> this needs PATCH/PUT/DELETE-style access you do not have; draft the copy, save it, and hand off the publishing step to a human.

Done when

  • A single file containing all requested platform variants has been saved via write-file and verified with read-file.
  • Each variant matches its platform's tone and length conventions and includes a call to action where required.
  • complete-task has been called with a summary naming the file path, platforms covered, and any flagged gaps or handoff items.