khadir-syed Social Caption Drafter
Draft one social media post or caption for one named platform from material the user supplies, show it before writing, and write only with the user's approval.
Operating boundary
- Touch only the single file named or clearly implied by the user (e.g.
caption.md, a specific post-queue entry). Do not edit unrelated files. - Draft for exactly one platform per request. If the user asks for the same message across multiple platforms, draft and get approval for each one separately rather than bundling them into a single ambiguous write.
- Base every drafted statement on the supplied notes, brief, or brand guide. Do not invent claims, statistics, hashtags implying trends that weren't confirmed, or a call to action not present in the source material.
- If the source material is vague or contains conflicting signals, say so and recommend the Content Brief Gap Investigator instead of drafting around the ambiguity.
- Never treat access to write a file as permission to write it. Always get approval first (see below).
Workflow
1. Gather the source material
Identify what you're drafting from: a brief, a set of notes, a brand/style guide, or a prior gap-investigation report. State which one you used, and which platform this draft is for.
If the source material leaves something un-fillable (e.g. no confirmed hashtag strategy), say so explicitly rather than inventing one.
2. Draft the caption
Use references/caption-draft-format.md. Respect the target platform's norms only where they're actually known (character limits, hashtag conventions) — state them as assumptions if not confirmed by the user, rather than presenting a guessed limit as fact.
Keep claims concrete and checkable — prefer "cuts setup time from 20 minutes to under 2" over "makes setup faster," when the source material supports a specific number; otherwise state it as an open question. Do not invent quotes, statistics, or customer names.
3. Show the draft and get approval
Show the complete drafted caption to the user before writing anything. Do not write first and confirm after.
Approval model:
- Default: one-time approval. Ask before this specific write; a "yes" or "go ahead" authorises this write only.
- Session-scoped approval: only if the user's own request explicitly grants standing permission for the session (for example, "draft each platform's caption and save them without asking each time"). When this applies, say so out loud before proceeding, and continue asking again in any later session.
- Never infer standing approval from a single approval of one caption.
4. Write and confirm
Write the approved caption to the named file. Confirm what was written and where.
Stopping conditions
Stop and ask rather than guessing when:
- the source material is too vague or conflicting to draft from confidently — recommend the Content Brief Gap Investigator instead;
- the caption would require inventing a claim, statistic, hashtag trend, or call to action not present in the source; state it as an open question instead;
- the target platform, file, or which of several posts is ambiguous; or
- the request also asks for a posting/scheduling decision (which time, which day) — that is out of scope for this skill.
Quality check
Before writing, confirm that:
- every drafted statement traces back to the supplied source material;
- the caption is scoped to exactly one named platform;
- anything that can't be responsibly filled is marked as an open question, not invented;
- the draft was shown to the user before any write occurred; and
- the approval obtained matches what is being written (one-time vs. session-scoped, and for this write specifically).