agentleFS
darkweb19darkweb19/skills/linkedin-content/SKILL.md

linkedin-content

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on "write a LinkedIn post", "is this hook any good", "review my post", "turn this into LinkedIn posts", "carousel", "what format should this be". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use content-repurposing.

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.
  • vivy-yiSkill

    content-repurposing

    Use when repurposing Xiaohongshu content, recycling existing posts, adapting content for different formats, maximizing content value, or creating content variations from core material

    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, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    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:

    1. Check the brief exists: If there is no positioning brief, offer linkedin-strategy first as a question.

    line 20
  2. Distinctive:

    Never fabricate a number, a client, a result, or a quote: Not one, not as a placeholder.

    line 63
  3. Distinctive:

    No engagement bait: Ask the question the post actually earned.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 9 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 Content — format, draft, lint

The post is not the deliverable; the specific thing only this person can say is. The scripts handle format choice, mechanical faults, and de-duplication. The interesting part — what actually happened and what it cost — comes from the user, and cannot be generated.

Workflow

1. Check the brief exists. If there is no positioning brief, offer linkedin-strategy first as a question. Posts without pillars are noise. Never chain silently.

2. Pick the format from the material, not from fashion.

python3 scripts/format_picker.py --goal authority --material data --material tutorial \
  --minutes 120 --output human

Exit 0 recommends / 2 asks when the top two are within a point (tie-break on which one they would enjoy making — the one they repeat beats the one that scores higher once) / 3 no fit, go get material. It refuses video with no camera and no footage, and a poll with no real decision behind it.

3. Draft. Interview for specifics before writing a line: the number, the mistake, the sentence someone said. Then write to the fold — the first ~140 characters are the whole post for most readers, and a sentence must complete inside them.

4. Lint before it ships.

python3 scripts/post_linter.py --input draft.md --has-image --output human

Exit 0 SHIP / 2 REVISE (or any blocking finding) / 3 REWRITE. Blocking findings have named consequences: over the 3,000-character cap; engagement bait, named as demoted content in the Professional Community Policies; Unicode pseudo-bold, which screen readers announce as mathematical symbols and search does not index as words. Two passes is normal; the stop condition is exit 0 or a stated decision to accept a warning.

5. Repurposing. Split a source and keep the ledger — it prevents the specific recurring failure of the same idea going out three times over eight months. Commit it alongside the source; it is project state, not a cache. Every unit is source material, not a post: add the sentence only the author can write — what it cost, or what they would do differently.

python3 scripts/repurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human
python3 scripts/repurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25

Rules

  • Never fabricate a number, a client, a result, or a quote. Not one, not as a placeholder.
  • Write to the mobile fold. A sentence completes before character 140.
  • Links in the first comment, and say so in the post.
  • No Unicode pseudo-bold, ever. It is an accessibility failure, not a style choice.
  • Alt text on every image; captions on every video. LinkedIn does not add them for you.
  • No engagement bait. Ask the question the post actually earned.
  • The author reads every line before it ships. They are the author of record.

Scripts

ScriptRole
scripts/post_linter.py0-100 across mechanics / hook / integrity / accessibility; blocking findings for the cap, bait, and pseudo-bold.
scripts/format_picker.pyRanks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls.
scripts/repurpose_splitter.pySplits a source into standalone units, scores them, and skips anything already in the reuse ledger.

References and assets

  • references/hook_and_fold_mechanics.md — the first 140 characters, and the openers to delete on sight (7 sources)
  • references/post_formats_canon.md — what each native format is good at, and the carousel trap (7 sources)
  • references/repurposing_discipline.md — standalone units, the reuse ledger, source types and their risks (7 sources)
  • references/accessibility_and_inclusion.md — pseudo-bold, alt text, captions, and why they are blocking (7 sources)
  • assets/post_templates.md — five worked post shapes with the hook already doing its job
  • assets/example_post.md — a post that passes the linter, annotated

Distinct from

  • linkedin-strategy — decides what the posts are about. This writes them.
  • linkedin-engagement — comments and DMs. A comment is a different craft with a different budget; it lives there.
  • marketing-skill/copywriting / content-humanizer — general copy and de-AI passes. Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.

Version: 1.0.0

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.