Define what needs review
Separate routine updates from material claims, launches, customer references, and sensitive topics.
- List categories requiring approval.
- State the evidence for each category.
- Keep scope limited to the publication decision.
Review the publication bundle
Present the account, exact revision, media, links, source context, schedule, and timezone as one bundle.
- Identify the post revision.
- Show account and destination.
- Require review after meaningful edits.
Record the decision and verify delivery
Approval is a clear decision on an exact revision; afterward verify the destination record.
- Record who approved and when.
- Do not publish edited revisions without review.
- Keep a corrective path for failures.
A final quality check
- The claim has source evidence.
- Account and audience are explicit.
- Exact text, links, media, time, and timezone are visible.
- The approver has authority.
- A published record or failure state is checked.
Questions about this skill
- Does every post need approval?
- No. Define a proportionate policy: higher-risk claims and sensitive subjects need more review than routine evidence-backed updates.
- What invalidates an approval?
- Any meaningful change to text, account, links, media, claim, or schedule should require a fresh decision.
Put the skill to work
Bring the idea. LaunchPost helps shape the draft.
Use your own business context, voice, and source material to move from an idea to content ready for review.
Open LaunchPost