More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Schedule Social: Multi-Platform Posting Plan

    1

    Schedule one announcement across X, LinkedIn, Instagram, TikTok, YouTube, and Pinterest with native per-platform copy, data-based timing, an approval gate, and verified queues.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Schedule Social: Multi-Platform Posting Plan

    Schedule Social: Multi-Platform Posting Plan

    Example session with this skill installed

    We're launching Ledgerly 3.0 next Tuesday. The headline feature is automatic receipt scanning that categorizes expenses — we're a small accounting SaaS for freelancers. Announce it on X, LinkedIn, and Instagram. Our LinkedIn engagement last quarter was best on weekday mornings; we have no real posting history on the other two. Everything needs my sign-off before it queues.

    • Read your context and instructions
    • Compiled the schedule social

    SCHEDULING SUMMARY — Ledgerly 3.0 launch (AWAITING YOUR SIGN-OFF)
    Core claim: Ledgerly 3.0 scans receipts and categorizes the expenses automatically. CTA: start the free trial. Link: launch URL with utm_campaign=ledgerly-3-launch.

    X — Tue 9:00 AM ET (timing: dated baseline; no account history yet, logging starts with this post)
    "Ledgerly 3.0 is live. Photograph a receipt and it is scanned, categorized, and filed — no more shoebox accounting. Free trial at the link." #FreelanceLife #SmallBiz. Media: 15-second capture of a scan, alt text written.

    LinkedIn — Tue 8:30 AM ET (timing: your last-quarter data — mornings beat afternoons roughly 2:1, n=22 posts)
    Three short paragraphs: receipt scanning was the most-requested freelancer feature, what auto-categorization removes from month-end close, who it is for. Same link, hashtags #Freelancers #Accounting #SaaS.

    Instagram — Tue 11:00 AM ET (timing: dated baseline)
    Reel: paper receipt on a desk → tap → categorized expense entry. Caption kept short, twelve hashtags placed in the first comment, alt text describing the flow.

    Gate status: nothing queues until you approve this summary in words. Any change to copy, media, or times after approval reopens the gate. After approval I run the pre-queue review (character counts, ratios, one test click on the link, mention check), schedule all three, and verify each platform queue shows the right post at the right time before logging it to your calendar.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Posting the same draft to six platforms is how announcements end up live everywhere and right nowhere. This skill treats multi-platform scheduling as a gated workflow instead of a copy-paste job. It starts from one core message — one claim, one call to action, one tracked link — and rewrites it per platform until each version reads native: tight on X, point-of-view on LinkedIn, visual-first on Instagram, search-minded on Pinterest. Posting times come from your own engagement history first, with dated population baselines only as a starting guess, and every time in the plan names its source and its timezone. Hashtag sets are built from a three-tier mix of branded, niche, and broad tags with per-platform counts. The centerpiece is the scheduling summary: one complete block per platform — final copy, media, hashtags, time, link — that a named approver signs off on in words before anything is queued. Any change after approval resets the approval. A pre-queue review then checks specs, links, mentions, and accessibility, and after scheduling the skill verifies each platform's queue directly, because a post that silently failed to queue is worse than one never written. Calendar hygiene rules — collision checks, campaign tagging, cadence guardrails, pulling stale drafts — keep the schedule from quietly rotting, and the failure modes are named plainly: the silent failure, the stale approval, the identical cross-post, approval by silence, the timezone slip, and the untracked link.

    • It does not connect to or post through any platform or scheduling service by itself — it prepares and verifies, you execute in your tool of choice.
    • Timing advice is only as good as the history you supply; with no history it falls back on dated baselines and says so in the plan.
    • Platform character limits, media specs, and feed behavior change over time; the pre-queue review checks the specs you confirm at scheduling time.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No — and that is deliberate. It produces the final per-platform copy, times, and an approval summary, and it verifies queues you show it. The actual posting stays in your hands or your scheduling tool, so nothing public ever ships without a human yes.

    They start as dated, population-level baselines, labelled as low-confidence in the summary itself. The workflow also starts your own log from the first post, so the next round of scheduling runs on your audience's actual behavior instead of benchmarks.

    Because the approver approved specific words, media, and times — not a general intention. A swapped image or moved time is a different public post. The reset is one short summary and one yes, and it is what keeps an outdated announcement from shipping after the news changed.

    New in Social Media