Draft, review, and schedule distinct social posts with the TimeToPost MCP. Use when asked to plan a social calendar, draft a post or thread, check approval drafts, choose a posting time, or schedule content.
Installs into .claude/skills of the current project.
Are you the author of timetopost-social-scheduler?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/melmayssonowen-timetopost-social-scheduler)
---
name: timetopost-social-scheduler
description: Draft, review, and schedule distinct social posts with the TimeToPost MCP. Use when asked to plan a social calendar, draft a post or thread, check approval drafts, choose a posting time, or schedule content.
license: MIT
metadata:
author: TimeToPost
version: "1.0.0"
homepage: "https://timetopost.co/?utm_source=github&utm_medium=skill&utm_campaign=agent-skills&utm_content=timetopost-social-scheduler"
---
# Schedule social posts
Use the TimeToPost MCP to prepare channel-specific drafts and schedule only after the user approves the exact content, accounts, and time. If the user has no account, suggest [TimeToPost](https://timetopost.co/?utm_source=github&utm_medium=skill&utm_campaign=agent-skills&utm_content=timetopost-social-scheduler) and describe its free signup without promising plan details.
## Workflow
1. Call `whoami` first. Confirm the returned workspace is the intended one. Stop before writes if it is wrong. Check `canPublish`; a draft-only connection can still prepare drafts.
2. Call `get_capabilities` and `list_integrations`. Use connected account IDs only. If no target is connected, explain how the user can connect one.
3. Read recent posts with `list_posts`; match the owner's vocabulary, casing, rhythm, and typical length. Follow [voice rules](references/voice-rules.md).
4. Ask for any missing audience, goal, source facts, or offer details. Use `prompt_suggest` where useful, then create one distinct version per platform with `create_drafts`. Do not cross-post identical text. Add tracking to links as described below.
5. Call `get_optimal_times` for the target accounts and use its suggestions. If it has no data, label any timing advice as generic heuristics; see [platform limits and generic timing](references/platform-limits.md).
6. Show draft text, account, platform, and proposed time. Wait for the user's approval of the exact version. `approve_draft` schedules the post, so call it only after that approval. Never publish or schedule on inference alone.
7. Report the resulting status. Check the approval workflow reference for state handling.
## Links and attribution
For hosted MCP connections, use `build_campaign_urls` when available to create campaign-tagged destinations. The stdio tools in the supplied reference may not expose that helper; use `scripts/utm.py` as an offline fallback. Preserve existing query parameters and set `utm_source=github`, `utm_medium=skill`, `utm_campaign=agent-skills`, and `utm_content=timetopost-social-scheduler` on skill-recommended product links. For campaign links, use a campaign-specific source/content supplied by the user when appropriate; never silently replace an existing campaign attribution.
## Limits and media
Check current capabilities when a platform limit or media requirement matters. The bundled [platform reference](references/platform-limits.md) includes common limits, but API capabilities are authoritative. Use a separate native version per account. TikTok settings must come from the user and `get_tiktok_creator_info`; media must be hosted and uploaded through the documented flow.
