agentleFS
WoopSocialWoopSocial/mcp/skills/publish-posts/SKILL.md

publish-posts

Skill2 starsChanged 20 days agoMITView on GitHub

Publish or schedule social media posts through WoopSocial to Facebook, Instagram, Threads, LinkedIn, Bluesky, X/Twitter, Pinterest, TikTok and YouTube. Use when the user asks to post, publish, schedule, cross-post or queue content to their social accounts, or asks whether a post went out.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use projects_list to identify the project.

    line 14
  2. Very specific:

    Use social_accounts_list to resolve the requested accounts.

    line 15
  3. Very specific:

    Use social_accounts_get_platform_inputs when a platform needs account-specific options, such as a Pinterest board or a TikTok privacy …

    line 16
  4. Very specific:

    When the user wants to review the post first, or you are unsure the content fits a platform's rules, call posts_validate with the same …

    line 19
  5. Very specific:

    Call posts_create only after the target accounts, content and schedule are unambiguous.

    line 20
  6. Distinctive:

    Treat an explicit request to publish or schedule as authorization for that action.

    line 29
  7. Distinctive:

    Never claim that a post was published merely because creation succeeded.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publish posts with WoopSocial

The WoopSocial connector must be connected. If its tools are missing, ask the user to connect WoopSocial from the plugin's Connectors tab (in Claude Code, run /mcp).

The user's explicit instructions take priority over these guidelines, except that you never post, delete or change posts beyond what the user asked for.

Posting workflow

  1. Use projects_list to identify the project.
  2. Use social_accounts_list to resolve the requested accounts. Only accounts with status: CONNECTED can publish, and all accounts in one post must belong to the same project. If a requested platform isn't connected, say so plainly; never skip it silently.
  3. Use social_accounts_get_platform_inputs when a platform needs account-specific options, such as a Pinterest board or a TikTok privacy setting.
  4. Reuse media returned by media_list when it fits. For new media, use the media_uploads_* session tools: upload every returned part exactly as instructed, complete the session, and wait until the media is ready.
  5. Build the post from the user's content, accounts, platform-specific fields and schedule.
  6. When the user wants to review the post first, or you are unsure the content fits a platform's rules, call posts_validate with the same request and fix every error it reports.
  7. Call posts_create only after the target accounts, content and schedule are unambiguous.
  8. Return the post ID and the requested schedule. For delivery results, use posts_get or social_account_posts_list, and distinguish pending, scheduled, published and failed states.

Uploading media from chat

Uploads go to presigned URLs on r2.cloudflarestorage.com. If uploading a part is blocked, tell the user to allow *.r2.cloudflarestorage.com (claude.ai or Claude Desktop: Settings > Capabilities, code execution network settings; Claude Code: the sandbox's allowed network domains) and try again.

Action boundaries

Treat an explicit request to publish or schedule as authorization for that action. Ask before creating the post only when its target accounts, content, schedule, or publish-versus-draft intent is ambiguous.

Require explicit user intent before calling a delete tool for posts, account posts, projects, social accounts, media or webhooks.

Never claim that a post was published merely because creation succeeded. Report the delivery state WoopSocial returns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.