Publish and schedule content to social media platforms (Twitter/X, Facebook, Instagram, LinkedIn) via the MCP bridge schedule_social_post tool as primary. The Design Stack media worker API is the fallback for advanced platform management. Covers platform-specific formatting, media attachment, scheduling, and WordPress-to-social publishing workflows. Use when posting to social platforms, scheduling future posts, attaching media to posts, checking optimal timing, or debugging API delivery failures.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when publishing or scheduling content to social media platforms. MCP bridge's schedule_social_post is the primary publishing tool.
This skill assumes you are using the MCP bridge. The WordPress plugin provides:
| MCP Tool | What it does |
|---|---|
schedule_social_post | Schedule or immediately publish content to multiple platforms with media, hashtags, and links |
Use this tool for all publishing. The media worker (http://localhost:3100/api/social/post) is a fallback for advanced scenarios or when the MCP tool doesn't cover a specific need.
Key mcp-ai WP-CLI commands for publishing workflows. Run via terminal:
| Command | Use for |
|---|---|
wp mcp-ai cron | Inspect scheduled social posts and cron events |
wp mcp-ai health | Check platform API credentials before publishing |
wp mcp-ai log | View publishing success/failure logs |
Trigger when ANY of the following is true:
Use schedule_social_post to publish or schedule posts:
Parameters:
content — Post text/content (required, 1–5000 chars)
platforms — Target platforms (required): ["facebook", "instagram", "twitter", "linkedin", "tiktok", "pinterest"]
scheduled_time — ISO 8601 datetime, or "optimal" for best-engagement timing
timezone — Timezone for scheduled time (default: WordPress timezone)
media_urls — Array of image/video URLs to attach
hashtags — Array of hashtag strings
link — URL to include in the post
recurrence — "none" (default), "daily", "weekly", "monthly"
recurrence_end — End date for recurring posts (ISO 8601)
get_optimal_timing — Set true to get optimal times without scheduling
Basic post to Twitter and LinkedIn:
content: "Just launched our new brand identity!"
platforms: ["twitter", "linkedin"]
Post with image, hashtags, and link:
content: "Check out our latest case study on brand design"
platforms: ["twitter", "linkedin", "facebook"]
media_urls: ["https://example.com/hero-image.jpg"]
hashtags: ["#BrandDesign", "#CaseStudy"]
link: "https://example.com/case-study"
Schedule for optimal time:
content: "Weekly design tips thread 🧵"
platforms: ["twitter"]
scheduled_time: "optimal"
Schedule for specific time:
content: "Product launch announcement!"
platforms: ["instagram", "facebook", "linkedin"]
scheduled_time: "2026-08-15T09:00:00Z"
timezone: "America/New_York"
Recurring weekly post:
content: "Monday Motivation: Design inspiration of the week"
platforms: ["instagram"]
recurrence: "weekly"
recurrence_end: "2026-12-31T00:00:00Z"
Check optimal timing without scheduling:
get_optimal_timing: true
Returns suggested posting times per platform based on audience engagement patterns.
| Platform | Text | Image | Video | Carousel | Scheduling |
|---|---|---|---|---|---|
| Twitter/X | ✅ 280 chars | ✅ up to 4 | ✅ 140s | ❌ | ✅ |
| ✅ 63K chars | ✅ | ✅ | ✅ | ✅ | |
| ✅ 2.2K | ✅ | ✅ (reels) | ✅ | ✅ (business) | |
| ✅ 3K | ✅ | ✅ | ❌ | ✅ | |
| TikTok | ✅ 2.2K | ✅ | ✅ | ❌ | ✅ |
| ✅ 500 | ✅ | ✅ | ❌ | ✅ |
For advanced scenarios or when debugging API connections, use the media worker:
const response = await fetch('http://localhost:3100/api/social/accounts');
const { platforms } = await response.json();
// [{ id: 'twitter', name: 'Twitter / X', connected: true }, ...]
const response = await fetch('http://localhost:3100/api/social/post', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
platform: 'twitter',
content: 'Just launched our new brand identity! 🎨✨',
hashtags: '#BrandDesign #CreativeStudio #NewLook',
}),
});
const response = await fetch('http://localhost:3100/api/social/post', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
platform: 'twitter',
content: 'Fresh design hot off the press! 🔥',
media_url: 'https://example.com/generated-image.jpg',
}),
});
Required env vars:
TWITTER_API_KEY — Consumer API key
TWITTER_API_SECRET — Consumer API secret
TWITTER_ACCESS_TOKEN — OAuth 2.0 access token
TWITTER_ACCESS_SECRET — OAuth 2.0 token secret
Get them at: https://developer.twitter.com/en/portal/dashboard
Free tier: 1,500 tweets/month, 1 app, 1 user.
Required env vars:
FACEBOOK_APP_ID — App ID
FACEBOOK_APP_SECRET — App secret
FACEBOOK_PAGE_TOKEN — Long-lived page access token
INSTAGRAM_TOKEN — Instagram Business account token
Get them at: https://developers.facebook.com/
Requirements: Facebook Page + Instagram Business/Creator account.
Required env vars:
LINKEDIN_CLIENT_ID — App client ID
LINKEDIN_CLIENT_SECRET — App secret
LINKEDIN_TOKEN — OAuth 2.0 access token
LINKEDIN_PERSON_URN — Your LinkedIn person URN
Get them at: https://www.linkedin.com/developers/
generate_gemini_image_validated (MCP).resize_image (MCP) for each platform's dimensions.schedule_social_post (MCP) to publish or schedule.schedule_social_post (MCP) first — it handles multi-platform posting, scheduling, and optimal timing in one call.get_optimal_timing: true to find best times, or scheduled_time: "optimal".WRONG — posting without verifying connected platform status first
→ The post silently fails. Always verify accounts are active before publishing.
RIGHT — check platform accounts first via schedule_social_post with get_optimal_timing: true
→ This validates API connectivity before the actual publish attempt.
WRONG — exceeding platform character limits (280 for Twitter, 2.2K for Instagram)
→ Truncated posts lose key messaging and CTAs.
RIGHT — truncate or split content per platform before scheduling
→ Write platform-length-aware copy; use threads for Twitter long-form.
WRONG — using identical content across all platforms without adaptation
→ LinkedIn audiences expect different tone than Instagram; hashtag norms differ.
RIGHT — tailor formatting per platform (hashtag count, line breaks, link placement, tone)
→ Write once, adapt per platform before calling schedule_social_post.
WRONG — scheduling 50 posts at once without checking rate limits
→ Twitter: 1,500/month (free tier); Facebook: 200/day/page; LinkedIn: 100/day.
RIGHT — spread posts across time; respect documented rate limits per platform
→ Use recurrence parameter for regular cadence instead of bulk one-shot scheduling.
WRONG — not capturing and storing post IDs/URLs after successful publishing
→ You lose the ability to track engagement or update/delete posts later.
RIGHT — store returned post URLs as WordPress post meta or in a tracking CCT
→ Enables analytics dashboards and cross-referencing with campaign performance.
WRONG — using media worker API directly when schedule_social_post covers the same needs
→ Adds unnecessary complexity and bypasses the MCP bridge's error handling.
RIGHT — use schedule_social_post (MCP) as primary; media worker only for unsupported platforms
→ Keep the publishing path simple and auditable through the MCP layer.
design-social-contentdesign-image-generationdesign-content-calendardesign-analytics-reportingdesign-social-content before publishing to generate platform-optimized captions.design-image-generation to create visuals for posts — use generate_gemini_image_validated (MCP).design-image-optimization to size images for each platform — use resize_image (MCP).design-content-calendar to plan and schedule posts.paper_store_* tools with connection_id to persist publishing logs to specific sites.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
日本語の概要は準備中です。原文の説明を表示しています。
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
日本語の概要は準備中です。原文の説明を表示しています。
Control a headless browser to navigate URLs, click elements, fill forms, extract content from JavaScript-rendered pages, take screenshots, and automate end-to-end web workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
日本語の概要は準備中です。原文の説明を表示しています。
Review code for quality, simplicity, and maintainability. Identifies unnecessary abstractions, duplicated logic, oversized functions, missing error handling, and naming issues — then fixes them automatically before presenting the result.
日本語の概要は準備中です。原文の説明を表示しています。
WooCommerce store operations through NV oOS Pro — product research, catalog cross-referencing, inventory lookups, and Shopify or Flowhub comparisons where integrations are configured.
日本語の概要は準備中です。原文の説明を表示しています。