Agent skill · alirezarezvani

linkedin-content

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.

What it needs

About 3k tokens when loaded.

What this skill does

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. 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. 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. Rules Never fabricate a number, a client, a result, or a quote. Not one, not as a placeholder. Write to the mobile fold. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills alirezarezvani/linkedin-content--45be20

View the source on GitHub

Browse the @skills marketplace