Happycapy Social Publisher

HappyCapy Social Media Publisher

Publish content to 13+ social media platforms with platform-optimized styles, optional AI-generated media, and smart error handling.

Environment Note: This skill is designed for HappyCapy environment with fixed paths:

• Claude config: /home/node/.claude.json
• MCP config: /home/node/.mcp.json
• Claude settings: /home/node/.claude/settings.local.json
• User home: /home/node

Prerequisites Check

1. Check Late MCP Configuration

Read /home/node/.mcp.json to verify Late MCP is configured.

If Late MCP not configured, execute automatic setup:

Automatic Setup Flow

Step 1: Install uv (if needed)

# Check if uv is installed
uvx --version

# If not found, install it
curl -LsSf https://astral.sh/uv/install.sh | sh

Step 2: Interactive API Key Setup

Ask user via AskUserQuestion tool:

Question: "Do you have a Late API Key?"
Options:
- "Yes, I have one" → Ask for API Key input
- "No, need to register" → Guide to registration

If user needs to register:

1. Guide user to visit https://getlate.dev (free tier: 20 posts/month)
2. Instruct: Settings → API Keys → Create API key
3. Ask user to provide the key (format: sk_xxxxxxxxxxxxxxxx)

If user has key:

1. Request API Key input via AskUserQuestion
2. Validate format starts with sk_

Step 3: Auto-Configure Files

Read and intelligently merge configurations:

For /home/node/.mcp.json:

# Read existing config
config = read_json("/home/node/.mcp.json") or {"mcpServers": {}}

# Add late server
config["mcpServers"]["late"] = {
    "command": "/home/node/.local/bin/uvx",
    "args": ["--from", "late-sdk[mcp]", "late-mcp"],
    "env": {
        "LATE_API_KEY": api_key_from_user
    }
}

# Write back
write_json("/home/node/.mcp.json", config)

For /home/node/.claude.json:

# Read existing config
claude_config = read_json("/home/node/.claude.json") or {"mcpServers": {}}

# Add late server (same as .mcp.json)
claude_config["mcpServers"]["late"] = {
    "command": "/home/node/.local/bin/uvx",
    "args": ["--from", "late-sdk[mcp]", "late-mcp"],
    "env": {
        "LATE_API_KEY": api_key_from_user
    }
}

# Write back
write_json("/home/node/.claude.json", claude_config)

For /home/node/.claude/settings.local.json:

# Read existing settings
settings = read_json("/home/node/.claude/settings.local.json") or {}

# Add "late" to enabledMcpjsonServers if not present
if "enabledMcpjsonServers" not in settings:
    settings["enabledMcpjsonServers"] = []
if "late" not in settings["enabledMcpjsonServers"]:
    settings["enabledMcpjsonServers"].append("late")

# Write back
write_json("/home/node/.claude/settings.local.json", settings)

Step 4: Restart Prompt

Display message:

✅ Late MCP configured successfully!

Please start a new conversation for the configuration to take effect.

After starting new conversation, I will verify the setup and guide you to connect social media accounts.

2. Verify Setup and Connected Platforms

In the new conversation, verify configuration:

Call mcp__late__accounts_list

Handle results:

• Success with accounts: Proceed to platform selection workflow
• Success but no accounts: Guide user to connect platforms
• Error: Display error message, suggest checking API key validity

If no accounts found:

Your Late API is configured, but no social media accounts are connected yet.

Please visit: https://getlate.dev/accounts

Connect your desired platforms:
- LinkedIn (Direct OAuth)
- X/Twitter (Direct OAuth)
- Instagram (Professional/Creator account via Facebook)
- Threads (via Instagram)
- Facebook, TikTok, YouTube, Pinterest, Reddit, Telegram, Discord, etc.

After connecting accounts, call me again to start publishing!

Workflow

Step 1: Analyze Content

Extract from user's input:

• Core message: Main topic or announcement
• Key points: 3-5 bullet points to emphasize
• Tone: Professional, casual, inspiring, technical, etc.
• Call-to-action: Link, question, or engagement prompt
• Media suggestion: Does content benefit from video or image?

Step 2: Platform Selection

Show user their connected platforms from accounts_list result.

Late API supports 13+ platforms including:

• Instagram, Twitter/X, LinkedIn, Threads
• Facebook, TikTok, YouTube, Pinterest
• Reddit, Telegram, Discord, Mastodon
• And more

Display the platforms that the user has actually connected (from accounts_list).

Ask user to select which platforms to publish to:

• List all their connected platforms dynamically
• Allow selecting all or specific subset
• Explain any platform-specific requirements if needed

Step 3: Media Generation (Optional)

Ask user if they want AI-generated media:

Option A: Generate AI Video

• Use /generate-video skill with appropriate prompt
• Duration: 6-8 seconds (optimal for social media)
• Save to ./outputs/ directory
• Get video URL for publishing

Option B: Generate AI Image

• Use /generate-image skill
• Save to ./outputs/ directory
• Get image URL for publishing

Option C: User Upload

• Ask user to provide media URL or file path

Option D: Text Only

• Proceed without media

Step 4: Content Adaptation

Generate platform-specific versions of content following these guidelines:

Instagram (max 2,200 chars):

• Visual storytelling style
• Emoji-rich, engaging narrative
• 8 relevant hashtags (mix popular + niche)
• Emphasize visual elements

Twitter (max 280 chars):

• Concise and punchy
• Conversational tone
• 1-2 hashtags only
• Strong opening hook

LinkedIn (max 3,000 chars):

• Professional insights and analysis
• Value-driven content
• 3-5 industry hashtags
• Thought leadership angle

Threads (max 500 chars - STRICT):

• Casual, authentic story
• Personal touch and relatability
• NO hashtags (they don't work on Threads)
• Keep under 450 chars for safety buffer

For detailed platform strategies, see references/platform-styles.md

Step 5: Preview & Approval

Display all generated content to user:

## Preview

### Instagram (348 chars)
[content]

### Twitter (276 chars)
[content]

### LinkedIn (689 chars)
[content]

### Threads (413 chars)
[content]

Ask user:

1. Approve all and publish?
2. Edit specific platform content?
3. Cancel?

If user requests edits, modify specific platform content and re-preview.

Step 6: Publish

Once approved, publish to selected platforms:

For multiple platforms simultaneously:

Call mcp__late__posts_cross_post with:
{
  "profiles": ["profile_id_1", "profile_id_2", ...],
  "text": "platform-specific content",
  "media_urls": ["https://...video.mp4"] (if media exists)
}

For single platform:

Call mcp__late__posts_create with:
{
  "profile_id": "specific_profile_id",
  "text": "content",
  "media_urls": ["..."] (optional)
}

Step 7: Error Handling

Threads Character Limit Error:

If Threads post fails with "text too long" error:

1. First retry: Remove adjectives, condense sentences (target: 400 chars)
2. Second retry: Remove line breaks, simplify further (target: 350 chars)
3. Third retry: Rewrite to essential message only (target: 300 chars)
4. Manual fallback: Ask user to manually edit content

Each retry should maintain core message while shortening length.

Other Platform Errors:

• Media upload failures: Retry once, then fallback to text-only
• Rate limits: Show error, suggest trying again later
• Authentication errors: Guide user to reconnect platform at https://getlate.dev/accounts