Community写作与编辑github.com

publora/linkedin-post

Use when the user wants to publish or schedule a LinkedIn post through Publora: text, a multi-image grid, a video, a PDF document, or @mentions. Not for analytics, reactions, comments or reshares (use linkedin-analytics), and not for other platforms.

linkedin-post 是什么?

linkedin-post is a Claude Code agent skill that use when the user wants to publish or schedule a LinkedIn post through Publora: text, a multi-image grid, a video, a PDF document, or @mentions. Not for analytics, reactions, comments or reshares (use linkedin-analytics), and not for other platforms.

兼容平台Claude CodeCodex CLICursor
npx skills add https://github.com/publora/skills/tree/main/skills/linkedin-post

Installed? Explore more 写作与编辑 skills: steipete/notion, affaan-m/seo, affaan-m/brand-voice · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档


name: linkedin-post description: Use when the user wants to publish or schedule a LinkedIn post through Publora: text, a multi-image grid, a video, a PDF document, or @mentions. Not for analytics, reactions, comments or reshares (use linkedin-analytics), and not for other platforms.

LinkedIn Post

Create and schedule LinkedIn posts using the Publora MCP server. Supports text posts, single images, multi-image posts (grid layout), videos, and PDF documents.

Prerequisites

Plans: Works on the free Starter plan. Current limits and pricing: publora.com/pricing.

Getting Started

  1. Create account at publora.com/register (free)
  2. Connect LinkedIn via OAuth in Publora Dashboard
  3. Get API key at app.publora.com/dashboard/api
  4. Connect your agent to the MCP server at https://mcp.publora.com, authenticating with Authorization: Bearer sk_YOUR_API_KEY. In Claude Code:
claude mcp add publora --transport http https://mcp.publora.com \
  --header "Authorization: Bearer sk_YOUR_API_KEY"

Claude Desktop, Cursor, Codex, OpenClaw and the claude.ai connector each need a different config file or flow: see client setup for the exact path and snippet.

REST API Fallback

If the MCP server is unavailable or returns errors, use the REST API directly:

Base URL: https://api.publora.com/api/v1

Authentication: Use x-publora-key header (NOT Authorization: Bearer):

# Get your connected platforms
curl -X GET "https://api.publora.com/api/v1/platform-connections" \
  -H "x-publora-key: sk_your_api_key"

# Create a post
curl -X POST "https://api.publora.com/api/v1/create-post" \
  -H "x-publora-key: sk_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "platforms": ["linkedin-Tz9W5i6ZYG"],
    "content": "Your post content here",
    "scheduledTime": "2026-03-25T10:00:00Z"
  }'

Platform ID Format: linkedin-{id} where {id} is from /platform-connections response.

Example IDs: linkedin-Tz9W5i6ZYG, linkedin-abc123xyz

📖 Full API documentation: docs.publora.com

Platform Limits

FeatureLimit
Characters3,000 max
Visible before "see more"First 210 characters
ImagesUp to 10 (grid layout, not swipeable carousel)
Image size36,152,320 pixels is the primary gate; 50 MB ceiling
Image formatsJPEG, PNG, GIF, WebP (WebP auto-converted)
Video duration30 minutes
Video size500 MB max
Video formatMP4 only

Available Tools

create_post

Create a new LinkedIn post or schedule for later.

Parameters:

  • platforms: Array including your LinkedIn connection ID (e.g., ["linkedin-abc123"])
  • content: Post text (up to 3,000 characters)
  • scheduledTime: ISO 8601 UTC datetime. Optional: omit it and the post is created as a draft. Send a future time to schedule. A time five or more minutes in the past is rejected with SCHEDULED_TIME_IN_PAST, so for immediate posting use the current time plus a minute.
  • mediaUrls: up to 10 public https image or video URLs. Publora downloads them server-side and attaches them before validation, so media and scheduling happen in one call. This is the one-shot alternative to the draft then get_upload_url then complete_media flow. Ingestion is rate-limited to 60 URLs per hour.

get_upload_url

Get a presigned URL to upload media.

Parameters:

  • postGroupId: The post ID to attach media to
  • fileName: File name (e.g., "chart.png")
  • contentType: MIME type (e.g., "image/jpeg", "video/mp4", "application/pdf")
  • type: "image" or "video"

complete_media

Finalize a file uploaded through get_upload_url, after the presigned PUT succeeds. Optional, because scheduling also finalizes pending media, but calling it early surfaces format and probe errors before publish. Not needed for media attached with mediaUrls.

Parameters:

  • mediaId: the id returned by get_upload_url

list_connections

List your connected accounts with their platform IDs. Call this first and copy the IDs verbatim; they are never guessable.

list_posts / get_post / update_post / delete_post

Manage scheduled and draft posts. update_post also patches content and platforms on a draft or scheduled post, so fixing a typo or retargeting no longer means delete and recreate. delete_media and prune_media_reference clean up uploaded files.

Mentioning People and Companies

LinkedIn posts support @mentions using URN syntax:

@{urn:li:person:MEMBER_ID|Display Name}       # Mention a person
@{urn:li:organization:ORG_ID|Company Name}    # Mention a company

Example:

Great insights from @{urn:li:person:4986615|Serge Bulaev} at @{urn:li:organization:107107343|Creative Content Crafts Inc}!

Important: The display name must exactly match the LinkedIn profile name (case-sensitive), including company suffixes like "Inc", "LLC", etc.

Do not hand-write member ids. The linkedin_list_mentionables MCP tool resolves a name to the correct URN; see the linkedin-analytics skill.

Important API Restrictions

  1. No organic carousels: Swipeable multi-image carousels are NOT available via API (only for sponsored content). Multi-image posts appear as a grid layout.

  2. No mixed media: Cannot combine images with videos or documents in the same post.

  3. No rich text: LinkedIn API does not support bold, italic, or other formatting. Use plain text or Unicode characters for emphasis.

  4. PDF alternative for carousels: To share multi-page swipeable content, upload a PDF document instead.

Examples

Simple Text Post

Schedule a LinkedIn post for tomorrow at 9 AM:
"We're thrilled to announce the release of our AI writing assistant. After 18 months of development, we're ready to help teams write better content faster."

Post with Mention

Create a LinkedIn post mentioning our CEO:
"Excited to share insights from @{urn:li:person:4986615|Serge Bulaev} on the future of AI in content creation."

Multi-Image Post

Create a LinkedIn post with 4 product screenshots showing our new dashboard features.

Note: Images will appear in a grid layout, not as a swipeable carousel.

PDF Document Post

Share our Q4 report as a PDF on LinkedIn with a summary caption.

This is the best way to share multi-page carousel-like content.

Best Practices

  1. First line matters: First 210 characters appear before "see more" - make them compelling
  2. Optimal length: Posts under 1,300 characters tend to perform better
  3. Posting times: Tuesday-Thursday, 8-10 AM in your audience's timezone
  4. Hashtags: Use 3-5 relevant hashtags - they're supported as plain text
  5. Engagement: End with a question to encourage comments

Troubleshooting

ErrorCauseSolution
"Account not connected"LinkedIn OAuth expiredReconnect in Publora dashboard
"MEDIA_ASSET_PROCESSING_FAILED"File too large or wrong formatCheck: images < 5 MB, videos < 500 MB MP4
"Rate limited" (429)Too many API callsWait and retry with backoff
"Cannot mix media types"Images + video in same postUse only one media type per post
MCP unavailableServer issueUse REST API fallback (see above)

Individual skills in this repo

This repo contains 8 individual skills — each has its own dedicated page.

publora/bluesky-post

Use when the user wants to post or schedule to Bluesky through Publora. Handles the 300-character cap, auto-detected hashtags and links, up to 4 images, and videos. Alt text cannot be set through the API. Needs a Bluesky app password, never the main password. Not for Mastodon (use social-post).

publora/instagram-post

Use when the user wants to post or schedule to Instagram through Publora: a single image, a 2-10 image carousel, a Reel or a Story. Requires a Business account and an image or video; text-only posts are rejected by the API. Not for Threads (use threads-post).

publora/linkedin-analytics

Analyze LinkedIn performance and manage engagement through Publora. Use when the user asks how a LinkedIn post or account performed (impressions, reach, reactions, comments, reshares, follower growth) or wants to react, comment, reshare or resolve an @mention. Statistics run over the REST API, engagement over MCP tools. Not for creating posts (use linkedin-post).

publora/social-post

Use when the user wants to post or schedule to YouTube, a Facebook Page or Mastodon through Publora. YouTube needs a video on every post, Facebook publishes to Pages only, Mastodon caps at 500 characters. Not for the platforms that have their own skill.

publora/telegram-post

Use when the user wants to post or schedule to a Telegram channel or group through Publora, using a bot. Covers Telegram markdown, silent delivery, link previews and forward protection. Bot API caps media captions at 1,024 characters and videos at 50 MB. Not for other platforms (each has its own skill).

publora/threads-post

Create and schedule Threads posts with image carousels and reply control via Publora MCP. Use when the user wants to post to Meta's Threads. Multi-part threading is currently disabled by the platform, so long content stays a single post. Not for Instagram (use instagram-post) or X threads (use x-post).

publora/tiktok-post

Use when the user wants to upload or schedule a TikTok video through Publora, with privacy, comment, duet, stitch and commercial-disclosure settings. Video runs 3 seconds to 10 minutes at 23+ FPS; carousels take up to 35 images. Unaudited apps can publish private videos only. Not for Reels (use instagram-post).

publora/x-post

Use when the user wants to post or schedule to X (Twitter) through Publora, including threads auto-split past 280 characters, up to 4 images, or a video up to 140 seconds. X needs a paid Publora plan. Not for Threads or Bluesky (each has its own skill).

相关技能

steipete/notion

Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.

community

affaan-m/seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

community

affaan-m/brand-voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

community

affaan-m/crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

community

affaan-m/x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

community

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

community