agentleFS
postproxypostproxy/postproxy-claude-plugin/skills/publish/SKILL.md

publish

Skill0 starsChanged 2 months agoMITView on GitHub

Create and publish a social media post via Postproxy. Use when the user wants to post, schedule, queue, draft, edit, thread, or delete content across social media platforms.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create, render and 9 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.
  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • suxrobGMSkill

    render

    Generate raster images (PNG, JPEG, WebP) from natural language prompts using Python rendering engines. Covers graphics, charts, layouts, and procedural art. Not for SVG output.

    Also in 3 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 6 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 4 projects that use this

  • GoogleSkill

    translate

    Translates a common phrase into one or more languages.

    Also in 3 projects that use this

  • aakash-dharSkill

    optimize

    Analyzes code for performance issues including slow algorithms, memory leaks, unnecessary re-renders, database query problems, and resource bottlenecks. Use when the user says "this is slow", "optimize this", "performance issue", "why is this taking so long?", or "make this faster".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If profiles aren't known, call profiles_list.

    line 7
  2. Distinctive:

    Ask which profiles to post to and for the content.

    line 8
  3. Very specific:

    Use require_confirmation: true for a dry run.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 49 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

Guide the user through publishing a post.

  1. If profiles aren't known, call profiles_list. profiles accepts profile hashids or bare platform names (linkedin, instagram, twitter, …). For a specific page/org/board/channel/location, resolve it via profiles_placements.
  2. Ask which profiles to post to and for the content. Watch platform limits: X plain text ≤ 280 chars (a URL costs 50 credits); Bluesky ≤ 300 graphemes; Telegram 4,096 / 1,024 with media; Google Business ≤ 1,500 chars, 1 image, no video.
  3. Media: pass URLs or local file paths in media. In a sandboxed/remote environment, use upload_create to get a temporary upload URL, POST the file bytes to it, then pass the returned URL in media.
  4. Choose timing:
    • Now — post_publish with profiles + content.
    • Draft — post_publish with draft: true (activate later with post_publish_draft).
    • Scheduled — post_publish with schedule (ISO 8601).
    • Queue — queues_list, then post_publish with queue_id (+ optional queue_priority high/medium/low). Don't combine queue_id with schedule.
  5. Threads (X, Threads, Bluesky only) go in the thread array. Per-network options (YouTube privacy_status/title, TikTok flags, Pinterest board_id, Telegram chat_id/parse_mode, Google Business cta_action_type) go in a platforms object.
  6. Use require_confirmation: true for a dry run. Show the returned post ID + status; suggest /postproxy:history to track it.

Editing — post_update (drafts, or scheduled 5+ min out). Only send changed fields; profiles/media/thread are full replacements, platforms merges.

Deleting — post_delete (add delete_on_platform: true to also remove from platforms), or post_delete_on_platform to remove from platforms while keeping the Postproxy record (Facebook/Threads/X/LinkedIn/Pinterest/YouTube only — not Instagram/TikTok). Confirm first.

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.