agentleFS
Sign inStart free
VercelKnown publishervercel-labs/eve-content-agent-template/agent/skills/linkedin-style/SKILL.md

linkedin-style

Skill28 starsChanged 21 days agoApache-2.0View on GitHub

Use when drafting or editing a LinkedIn post in the house voice.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing or editing a LinkedIn post:

    line 7
  2. Distinctive:

    Hook first: Only ~200 characters show on mobile before "…see more" — the first line decides whether anyone expands the post.

    line 9
  3. Distinctive:

    One idea per post: If you have two, write two posts.

    line 12
  4. Distinctive:

    Links suppress reach: When a post needs a link, put it in the first comment and say "link in the comments" — don't put it in the body.

    line 24

≈ “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

LinkedIn voice & style

When writing or editing a LinkedIn post:

  • Hook first. Only ~200 characters show on mobile before "…see more" — the first line decides whether anyone expands the post. Open on the surprising stat, the bold claim, an open loop, or a one-line story setup. No throat-clearing, no "A few thoughts on…".
  • One idea per post. If you have two, write two posts. How-tos and concrete lists land best.
  • Short lines and single-sentence paragraphs, with white space between them — it's read on a phone, and the gaps keep it scannable.
  • Concrete and specific: a number, a result, a before/after, a moment. No vague inspiration.
  • Deliver the value in the feed. Self-contained text is what people engage with — don't make the reader leave to get the point.
  • End with a genuine question or a clear takeaway, not a "thoughts? 👇" prompt. A real question earns comments, and comments move the post further than likes.
  • At most one emoji, and only if it earns its place. 3–5 relevant hashtags max, grouped at the end, CamelCase and specific (#BusinessWriting, not #Business) — they're topic signals, not a discovery feed.
  • No "I'm humbled to announce", no engagement-bait, no "Agree?" closers or reaction-poll chains.
  • Links suppress reach. When a post needs a link, put it in the first comment and say "link in the comments" — don't put it in the body.

Structure

  1. Hook — the surprising claim or the moment, line one (before the fold).
  2. Turn — the tension, or the thing most people get wrong.
  3. Payoff — what you learned, with a concrete detail.
  4. Close — one question or one takeaway.

References

  • references/best-practices.md — researched tactics as a pre-flight checklist (hook, links, hashtags, formats).
  • references/post-specs.md — character limits and document/carousel specs for quick lookup.
  • references/banned-words.json — words to avoid. Read it once up front for awareness, then run the lint_against_style tool (surface linkedin) on your draft to check it against this file before proposing the draft to the writer.

Shared references

Shared global references for all skills in the content agent. These apply regardless of the content type.

  • references/ai-phrases-to-avoid.md — AI-tell words, phrases, and punctuation to avoid.
  • references/plain-english-alternatives.md — plain-English swaps for bloated or vague wording.

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