ProPost account setup audit

Reads the whole account, scores it against what a consistent personal-brand setup needs, and turns every gap into a specific fix. Fixes that the connection's autonomy allows are made with the person's yes; the rest become a short to-do list for them in ProPost.

Before you start

1. get_account: plan, renewal, AI drafts used/limit/reset, weekly scheduling cap, channels connected vs allowed, time zone, approval setting, this connection's autonomy. Note which fixes your level allows.
2. list_channels: id, network, kind, max_length, needs_reconnect, queue_paused, media requirements.
3. list_personas: the default voice, named voices, channel_ids per voice.
4. For each healthy channel: get_posting_schedule (slots, paused, next free slot) and suggest_posting_times (better times, and whether they come from the person's own history or general patterns).
5. list_posts with status: "scheduled", then "draft" and "failed" (limit 100 each): the real queue, the backlog and the broken posts.
6. list_ideas (limit 200): how deep the idea bank is.

Do all reads before saying anything; the audit is one message, not a drip.

Workflow

1. Score each area from the reads, using the checklist below.
2. Report as a table: area, status (ok / needs attention / blocked), the evidence in one line, the fix. Lead with blockers, then quick wins.
3. Propose fixes in priority order and ask once: "Shall I do 1 to 4?" Do not change anything before a yes.
4. Apply the approved fixes (see the fix table), then re-read the affected area (get_posting_schedule, list_personas) to confirm it took.
5. Hand over the rest: things only the person can do (reconnect a channel, raise the autonomy level, upgrade the plan, edit the default voice in profile settings), each with the exact place in ProPost.
6. Offer the next step: propost-brand-voice if voices are thin, propost-content-pillars if the idea bank is empty, propost-weekly-content-plan to fill the queue.

The checklist

Writing guidance

The audit is a diagnosis, so write it like one.

• Evidence, not adjectives. "LinkedIn has 0 scheduled posts and its next free slot is tomorrow 08:30, so nothing is going out" beats "your queue needs work".
• Rank by consequence. Nothing posting (paused queue, reconnect, empty runway) outranks tidiness (old drafts).
• One recommendation per row, in the person's terms: "Add Tue/Thu/Sat 08:30 for LinkedIn", not "optimise your cadence".
• Keep it under about 15 lines of table plus a 3-line summary. A long audit does not get acted on.

Example summary:

Your account is blocked on one thing: LinkedIn needs reconnecting, so nothing can go out there. Once that is done, the quickest wins are posting times (none are set for Instagram) and 11 drafts older than a month.

Guardrails

• Read-only until the person says yes to specific fixes.
• Never publish_now during an audit, even to "test" a channel.
• set_posting_schedule, delete_post, delete_idea and update_persona overwrite or remove things: name exactly what changes first.
• Don't change a voice to "improve" it without samples or the person's input.
• Don't try a tool above the connection's autonomy to see if it works.
• Don't count AI drafts you have not checked in get_account.

If something fails

• plan_required: the connector needs Pro or Premium. Tell the person; stop.
• autonomy_limit: list the fixes as a to-do for ProPost, or ask them to raise the level in Settings, Integrations.
• channel_needs_reconnect: ask for the reconnect, skip the channel.
• invalid_day / invalid_time / too_many_slots: use mon..sun, HH:mm 24-hour, at most 12 times a day.
• rate_limited: batch the reads, wait, continue.
• Anything else: see ../CONVENTIONS.md.