Skill Content

Publishing

Technical rules for publishing content to social media and websites — platform limits, formatting, API patterns, OG tags, multi-platform workflow.

Overview

Publishing provides universal technical rules for the final step of content distribution. It does NOT cover writing (see the writing skill) or quality review (see humanize and factcheck skills). Instead, it handles: how to format content for each platform, what limits apply, how to post correctly, and how to verify the result.

Supported Platforms

  • Telegram — Bot API: sendMessage (4096 chars), sendPhoto caption (1024 chars), HTML formatting subset, discussion group comments
  • LinkedIn — 3000 chars, no HTML/Markdown, Unicode bold workaround, 1200×627 images
  • Facebook — 63,206 chars, no rich text via API, OG-based link previews
  • X / Twitter — 280 chars (free) / 25,000 (Premium+), links count as 23 chars, threads
  • VK — 15,895 chars, limited HTML via API, up to 10 images
  • Instagram — 2,200 chars caption, no clickable links in captions, max 30 hashtags, carousel up to 10

Website Publishing

OG tags (og:title, og:description, og:image 1200×630), Twitter Card tags, blog post technical checklist (slug-friendly URLs, canonical links, heading hierarchy, image optimization, hreflang for multi-language).

Multi-Platform Workflow

  1. Start from the longest version (Telegram/Facebook — most text capacity)
  2. Adapt down for constrained platforms: LinkedIn trim to 3000, X/Twitter extract hook + link or thread, Instagram rewrite as caption
  3. Recommended publication order: Website/blog first (SEO indexing), then Telegram, LinkedIn, Facebook, X, VK, Instagram

Testing and Verification

  • Always test in private chat / draft / staging before publishing
  • Verify link preview cards render correctly (OG debuggers per platform)
  • Check formatting renders — no raw HTML/Markdown shown
  • Test on mobile — most social media consumption is mobile
  • OG cache busting: Facebook Sharing Debugger, LinkedIn Post Inspector, Telegram @webpagebot