Network fit

Takes one idea and ships it in the shape each network rewards: the right length, the right media, the right tone, the right amount of hashtags. A cross-posted copy-paste is the failure mode this skill prevents.

Before you start

1. get_account: autonomy, AI drafts left (generate_draft costs one per distinct voice), time zone.
2. list_channels: for each target the network, max_length (use this number, not memory: some channels carry their own limit), whether it needs an image or video, needs_reconnect, queue_paused.
3. list_personas: the voice each channel writes in. Different voices on different channels are intentional; keep them.
4. The source text: from the person, or get_post. Read references/networks.md for per-network detail.

Workflow

1. Find the core: one sentence that is the point, one concrete detail (a number, a scene, a name the person gave you), one action or question. Everything else is optional per network.
2. Group channels by shape:
   Long form: LinkedIn, Facebook, Telegram, YouTube description.
   Short and direct: X, Bluesky, Threads, Mastodon.
   Visual first: Instagram, TikTok, Pinterest.
   Local and practical: Google Business.
3. Write the versions.
   Person gave the words: one create_draft with all channel_ids, the long text as content and a shorter text per channel in per_channel (keyed by channel id). Free, linked by group_id.
   You need ProPost to write: generate_draft with an idea and the channel_ids; it writes for the longest network and condenses for the rest.
   Existing post to another channel: copy_post_to_channel (condenses if needed, original untouched). Then polish with update_post.
4. Tighten: if a version is too long, edit it yourself or rewrite_post ("under 280 characters, keep the number") which is limited to 3 per post. Do not just truncate a sentence mid-thought.
5. Media: add what the network requires. Instagram, Pinterest and TikTok photos need an image (propost-visual-posts); YouTube needs a video (propost-video-posts). attach_image with apply_to_linked: true shares it across copies; remember caps (X 4 images, Threads 1, etc.).
6. Hashtags (only where useful, see below): generate_hashtags for suggestions, then set_hashtags with the 1 to 3 you choose; it writes them on their own last line and refuses with too_long if they do not fit. create_draft's hashtags field only saves suggestions; it does not publish them.
7. Check: check_post on every copy; fix every issue.
8. Send by autonomy: add_to_queue (schedule level) or leave as drafts. Stagger the same idea across networks by a few hours or a day rather than posting all at once (propost-posting-schedule-optimizer).

Writing guidance

• Adapt the shape, not the facts. The number, the claim and the offer stay identical on every network.
• A good X version is not a LinkedIn post cut off at 280. Lead with the sharpest line, drop the setup, keep one link at most.
• Links: LinkedIn reach can drop when a link is in the body; put the link in the first comment if the person does that, or at the end. X and Bluesky show link previews; put it last. Instagram captions do not make links clickable: say "link in bio" only if true.
• Hashtags: LinkedIn 0 to 3, X 0 to 2, Bluesky 0 to 2, Threads 0 to 1, Mastodon 1 to 4 (they drive discovery, use CamelCase), Instagram 3 to 8 relevant ones, TikTok 3 to 5, Pinterest 2 to 5 keywords in the description, Facebook 0 to 2, Telegram 0 to 2, YouTube 3 maximum.
• Emojis: sparingly, as punctuation. No emoji walls, no "🚀" hype.
• Example. Core: "We cut onboarding from 9 days to 2 by removing one approval step."
  LinkedIn (about 900 characters): the story in 5 short paragraphs, the before and after, one question.
  X (under 280): "We cut onboarding from 9 days to 2. The change: one owner signs off, everyone else is told, not asked."
  Instagram: a stat-card image plus a 3-line caption and 4 tags.
  Google Business: skip unless it is a local offer; this is not its job.

Guardrails

• Never send a version to a network it does not suit just to fill a cell: say "skipped Google Business, not a local update".
• Do not change the meaning or invent details to make something fit.
• Respect needs_reconnect and queue_paused; skip and say why.
• Check lengths with check_post, not by eye: emoji and accents count by characters, and some channels have custom limits.
• publish_now only after an explicit yes with the final text shown per channel.
• Do not tag or name third parties without the person's say so.

If something fails

• too_long: shorten the text (or rewrite_post), then check_post.
• image_required / video_required: attach media first.
• quota_exceeded: write the versions yourself with create_draft.
• channel_needs_reconnect: skip that channel, ask them to reconnect.
• nothing_to_change: the edit equals what is there; move on.
• Others: see ../CONVENTIONS.md.