published-vs-plannedlisted
Install: claude install-skill RabbitDesigns22/claude-skills
# Published vs planned
A tool saying "success" is not a post on a profile. Schedulers accept a job and fail later: expired token, wrong account, rejected format, one network silently dropped. The owner then opens the page, finds nothing, and the agent has already said "all published". This skill closes that gap with one rule: **a row is "published" only if you saw it live, in this check.**
## When to use
- You just scheduled, uploaded or published something and are about to report it.
- Someone asks "did it go out?", "is everything saved?", "why isn't it on Instagram?".
- A recurring job posts content for clients and nobody has looked at the live pages.
Do not use it to design posts, write captions, or read ad results. It only answers: did the thing I planned exist where it should, when it should?
## The method
### 1. Build the plan list first (before touching the scheduler)
One row per item per network. Cross-posting to Facebook and Instagram is two rows.
| # | Account / page | Network | Format | Planned date-time + timezone | Asset (file name or id) | Caption, first words |
|---|---|---|---|---|---|---|
Rules:
- Write the timezone on every row. The scheduler's timezone and the account's timezone often differ.
- Take the list from the brief or approved calendar, not from what you remember doing.
- If a field is unknown, say so now. Do not fill it later from guesses.
### 2. After scheduling: read back from the scheduler's own list
Close the confirmation toast. Open