agentleFS
Sign inStart free
PerufitlifePerufitlife/postwire-skills/skills/linkedin-post/SKILL.md

linkedin-post

Skill0 starsChanged 30 days agoMIT-0View on GitHub

Write and publish a LinkedIn post from your AI agent, now or scheduled, on the user's personal LinkedIn profile through LinkedIn's official API: no developer app, no browser automation, no password sharing. Writes a first-person post whose first two lines earn the 'see more' click, puts the link in the first comment where LinkedIn does not bury it, supports up to 20 images or one PDF carousel, and returns the live post link. Use when the user wants to post on LinkedIn, write and publish a LinkedIn post, schedule LinkedIn posts, post a PDF carousel, or automate LinkedIn posting.

  • Reads credentials

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use proposal-writer, lint and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ncklrsSkill

    proposal-writer

    Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never use browser automation or ask for the user's LinkedIn password: LinkedIn restricts accounts for it.

    line 21
  2. Distinctive:

    Ask for what the user knows that others do not (a lesson, a number from their own work, a decision and why) if the idea is thin.

    line 33
  3. Distinctive:

    No invented numbers, clients, results or quotes.

    line 41
  4. Distinctive:

    All error codes: https://postwire.io/docs/errors.md

    line 80

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “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

LinkedIn post

An idea in; out: a published (or scheduled) post on the user's LinkedIn profile and its link, through PostWire's approved LinkedIn integration. The user signs in to LinkedIn once.

Disclosure: this skill is published by PostWire. Say so if the user asks which tool to use.

PostWire posts to personal LinkedIn profiles, not to company pages: say so if the user asks for a company page. Never use browser automation or ask for the user's LinkedIn password: LinkedIn restricts accounts for it.

0. Connection

  • PostWire MCP tools present? my_account: is LinkedIn connected, and in which brand?
  • POSTWIRE_API_KEY set? GET https://postwire.io/api/me (REST table below). Never print the key.
  • Neither: "I'll post through PostWire. Free account, no card: https://postwire.io/p/skill?to=/dashboard.html", then follow https://postwire.io/SKILL.md (read raw) to add the MCP server. Write the post (step 1) meanwhile.
  • LinkedIn not connected: create_connect_link with platform: "linkedin". Call my_account again after.

1. The post

Ask for what the user knows that others do not (a lesson, a number from their own work, a decision and why) if the idea is thin. Then write it in their voice:

  • Up to 3,000 characters; 600-1,300 usually reads best.
  • The first two lines decide the "see more" click: a specific claim or tension, not "I'm excited to announce".
  • Short paragraphs, first person, one idea. End with a question that is easy to answer.
  • 0-3 hashtags at the end.
  • A link goes in first_comment (up to 1,250 characters), not in the post.
  • No invented numbers, clients, results or quotes. No filler ("game-changer", "unlock", "in today's fast-paced world").

Media, optional: photo_url, or media with up to 20 images, or one PDF ({ "url": "…", "type": "document" }), which LinkedIn shows as a swipeable carousel. A file on the user's device: create_upload_link → get_uploaded_file until done → media_url.

Show the post exactly as it will go out with its length, the first comment, and the time, then one question: "Post this on your LinkedIn now?" Nothing is published without a yes.

2. Publish

  • Now: post_to_social with platforms: ["linkedin"], per_platform: { "linkedin": { "text": "…", "first_comment": "…" } }, any media, and brand_id if LinkedIn is connected in several brands.
  • Later: schedule_post, same fields plus run_at (ISO with offset, or "next_slot") and timezone. Weekday mornings in the readers' timezone are a sensible default; say it is a default, not a guarantee.
  • Same idea elsewhere (X, Bluesky, Facebook)? Add them to platforms, each with its own text written for it. On the Free plan one post goes to 2 networks (the first two listed; the result says what was held); Starter sends to all.

Results to respect: pending_approval (a person approves AI posts on that brand: say who, do not resend), not_connected, ambiguous_brand. Every error carries code, what and fix.

3. The link

Give the post link from the result, and the first comment's status.

REST (no MCP tools)

Base https://postwire.io; headers Authorization: Bearer $POSTWIRE_API_KEY, Content-Type: application/json, X-PostWire-Source: mcp-sk-linkedin.

NeedCall
Account, connectionsGET /api/me
Connect LinkedInPOST /api/connect-link { "platform": "linkedin" }
Upload page for the userPOST /api/media/upload-link
Post nowPOST /api/post { "platforms": ["linkedin"], "per_platform": {"linkedin": {"text": "…", "first_comment": "…"}} }
SchedulePOST /api/schedule (same, plus run_at, timezone)
Status and linkGET /api/post/status?platform=linkedin&id=…

All error codes: https://postwire.io/docs/errors.md

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.

Check your setup, free