agentleFS
PostLakePostLake/postlake-mcp/skills/postlake-publish/SKILL.md

postlake-publish

Skill2 starsChanged 2 months agoMITView on GitHub

Publish a social media post right now to one or more connected accounts (X, LinkedIn, Instagram, TikTok, Facebook, Threads, Bluesky, YouTube, Pinterest) through PostLake. Use when the user wants to post immediately.

  • Reads credentials
  • Sends data out

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Idempotency: always send a unique Idempotency-Key header so a retry replays the same result instead of double-posting.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

PostLake: publish a post now

Publishes one caption to as many connected accounts as you like, in one call. Each platform is attempted independently and the response reports per-platform state and url.

Auth

Authorization: Bearer $POSTLAKE_API_KEY

Base URL https://api.postlake.dev.

Choosing where to post

Two ways to say which accounts a post goes to: pick whichever is simpler:

  • By profile (simplest): a profile is a named group of connected accounts (a brand, a client, "me"). Pass "profile": "my-brand" and it posts to every account in it. Add "platforms": ["bluesky","linkedin"] to narrow it to certain networks. No id lookup needed.
  • By account id (precise): pass "accounts": ["acc_…"] for exact accounts. Get the ids from the postlake-accounts skill (GET /v1/social-accounts).

Provide profile, accounts, or both. At least one is required.

Publish

# Simplest: post to a whole profile.
curl -X POST https://api.postlake.dev/v1/posts \
 -H "Authorization: Bearer $POSTLAKE_API_KEY" \
 -H "Content-Type: application/json" \
 -H "Idempotency-Key: $(uuidgen)" \
 -d '{
  "text": "Shipping something new today 🚀",
  "profile": "my-brand"
 }'

To hit specific networks in that profile add "platforms": ["bluesky"]; to target exact accounts use "accounts": ["acc_84a4…","acc_e553…"] instead.

Response (normalised: reason over targets):

{
 "id": "post_…",
 "state": "published",
 "targets": [
  { "platform": "bluesky", "state": "published", "url": "https://bsky.app/profile/…/post/…" },
  { "platform": "linkedin", "state": "published", "url": "https://www.linkedin.com/feed/update/…" }
 ]
}

state per target is one of published, processing (async platforms like TikTok/YouTube: poll GET /v1/posts/{id} until final), failed (see target.error), or scheduled.

Options

  • Attach media: upload first with the postlake-media skill, then pass the ids: "media": ["med_…"] (with optional "mediaAlt": ["alt text"]).
  • Per-platform captions: "textOverrides": { "x": "shorter for X", "linkedin": "…" }.
  • Platform-specific settings: "platformOptions": { "pinterest": { "boardId": "…" }, "youtube": { "title": "…", "privacyStatus": "private" } }.

Rules to respect

  • Idempotency: always send a unique Idempotency-Key header so a retry replays the same result instead of double-posting.
  • X: needs a paid plan (X is the only network that charges). On a free plan an X target returns error.type: "entitlement_exceeded": other platforms still go out. Don't treat that as a total failure.
  • Media-required platforms: Instagram, TikTok, YouTube, Pinterest need media. a text-only post to them fails with invalid_input.
  • A failed target never sinks the others; report which went out and which didn't.

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.