agentleFS
Sign inStart free
content-millcontent-mill/claude-plugin-linkedin/skills/draft-post/SKILL.md

draft-post

Skill0 starsChanged 19 days agoMITView on GitHub

Write a LinkedIn post and save it as a draft in Content Mill. Use when the user wants to draft, write, rework or save a LinkedIn post without publishing it yet.

5 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Call list_social_accounts and use only accounts whose status is Connected.

    line 15
  2. Very specific:

    Call get_platform_limits before writing so the text and media fit.

    line 16
  3. Very specific:

    Write the post to fit, then call create_draft with content, account_ids and any media_urls.

    line 18

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

/content-mill-linkedin:draft-post

Saves a LinkedIn post as a draft. A draft is never published; the user reviews it in Content Mill or asks you to publish it later with /content-mill-linkedin:publish-post.

Arguments passed: $ARGUMENTS (the idea or text for the post; ask if it is empty).

Steps

  1. Call list_social_accounts and use only accounts whose status is Connected. If more than one LinkedIn account is connected and it is unclear which the user means, ask.
  2. Call get_platform_limits before writing so the text and media fit. A LinkedIn post is at most 3,000 characters, with up to 9 images or one video (never mixed); media is optional.
  3. Media, if the user wants any: call upload_media_from_url with a public https link, or create_media_upload then finish_media_upload for a file that has no link. Never put file contents in a tool argument.
  4. Write the post to fit, then call create_draft with content, account_ids and any media_urls. Give it a short display_name if it helps the user find it later (it is never sent to LinkedIn).
  5. Tell the user the draft was saved and what it says. To change it later use update_draft; say what will change first, because it overwrites the draft and keeps no earlier version.

Nothing in this skill publishes anything.

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