agentleFS
coolxeocoolxeo/grok-bot-skills/skills/writing/social-copywriting/SKILL.md

social-copywriting

Skill8 starsChanged 3 days agoMITView on GitHub

Use this when writing or adapting copy for X or LinkedIn so it matches the platform instead of sounding like a press release.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Write posts that read native to X or LinkedIn.

    line 9
  2. Distinctive:

    Look for the detail a careful reader would stop for and a press release would bury: the mechanism, the constraint, the number that moved, …

    line 17
  3. Distinctive:

    No links in the body. Write "Link in comments."

    line 35
  4. Distinctive:

    No hyphens in the body. Rephrase around them.

    line 36
  5. Distinctive:

    No engagement bait ("like if you agree", "comment YES").

    line 43
  6. Distinctive:

    No trailing period on the last line.

    line 45
  7. Distinctive:

    When fixing an existing post: name its job, its reader, its strongest line, and what must stay.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Social copywriting

Write posts that read native to X or LinkedIn. Use it once the idea exists; finish with no-ai-slop.

Before writing

Settle four things, asking only for what's missing: platform, format (single post, thread, carousel text), the one thing the reader should take away, and the proof you have for it (a number, a screenshot, a link, a story). No proof means the post is an opinion; write it as one.

Find the angle

Look for the detail a careful reader would stop for and a press release would bury: the mechanism, the constraint, the number that moved, the thing that changes how someone builds. Don't recap the announcement.

Hook

The first line decides everything. If it's weak, change where the post starts instead of polishing the words. Strong openings name a specific pain, result, image, or mechanism. Weak ones restate the topic, start too wide, or tease ("you won't believe..."). Rotate how you open (a number, a quote, a flat fact, a moment mid-scene) so posts don't share a template.

X

  • What the ranker rewards is conversation. Its published weights count a reply far above a like, a reply the author answers higher still, and "show less" or a report as heavy negatives. Write something worth answering, then answer.
  • Links in the body cost reach; put the link in a reply.
  • Single post: one idea. On long posts, the point lands before the "show more" cut.
  • Thread: 5-12 posts. Post 1 is the hook and stands alone. Each post earns the next. The last one asks a real question or just stops.
  • 0-2 hashtags, never mid-thread. Never paste LinkedIn copy onto X.

LinkedIn

  • The hook has to work before "see more" (about 140 characters on mobile).
  • LinkedIn ranks partly on dwell time and pushes down posts people skip, so the body has to reward reading. Around 1,200-1,600 characters for a normal post.
  • No links in the body. Write "Link in comments."
  • No hyphens in the body. Rephrase around them.
  • Up to four hashtags, at the very end.
  • Include one honest note in the middle: a limit, a weak result, something not yet tested.

Both

  • Real units only: spend, views, files, minutes. Never invent a figure, quote, or date.
  • No engagement bait ("like if you agree", "comment YES").
  • Vary the post shape from the last one: straight prose, numbered teardown, one-line post, quote and react, changed-my-mind.
  • No trailing period on the last line. No em dashes.
  • Deliver the post in a code block, then two lines: the angle you picked and what you left out.

Critique before rewrite

When fixing an existing post: name its job, its reader, its strongest line, and what must stay. Then rewrite.

Inspired by

  • Jules Sauvajol, Copywriting-skill (social-copywriting) (MIT). Does well: platform limits, the see-more fold, thread structure, and a critique-before-rewrite habit. Missing: reach figures with no sources (such as links cutting LinkedIn reach by 30-50%), hook templates that are themselves AI tells ("It's not what you think"), and advice to swap conjunctions for dashes.
  • X heavy ranker README, twitter/the-algorithm-ml. Does well: the real published weights (April 2023): reply 13.5, reply answered by the author 75, like 0.5, "show less" -74, report -369. Missing: a 2023 snapshot that X can change at any time, and no writing advice.
  • LinkedIn Engineering, Understanding feed dwell time. Does well: shows dwell time is measured once half a post is visible and that predicted skips lower a post's score. Missing: no thresholds in seconds and no posting advice.

What this version adds

  • Ranking advice tied to published sources instead of folklore numbers.
  • Dani's LinkedIn rules: no hyphens, four hashtags max, one honest note, link in comments.
  • Shape and opening rotation so a feed of posts doesn't read like one template.
  • Code-block delivery with an angle note, and hooks that pass no-ai-slop.

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.