agentleFS
sami2919sami2919/SignalForce/skills/linkedin-content/SKILL.md

linkedin-content

Skill9 starsChanged 3 months agoMITView on GitHub

Use when writing organic LinkedIn posts to warm up prospects before outreach, when building thought leadership in your ICP's domain, or when creating content that complements cold outreach sequences

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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    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:

    Read config/gtm-context.md for brand voice, target personas, and domain terminology.

    line 14
  2. Distinctive:

    No external links in the post body (algorithm penalty — put links in first comment)

    line 46

“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

Why This Matters for Outbound

Cold outreach converts better when prospects recognize your name. Organic LinkedIn posts build credibility so that when your email arrives, you're a familiar voice — not a stranger. Use this skill to create posts that your ICP will see before they get your first email.

Before Writing

Read config/gtm-context.md for brand voice, target personas, and domain terminology. Posts should sound like you, not like marketing copy.

Post Anatomy

HOOK (first 1-2 lines)         ← Visible before "...see more"
...see more ──────────────────  ← The click gate (210 chars)
BODY (story/value)              ← Short paragraphs, 1-2 sentences each
CTA (last 1-2 lines)           ← Invite genuine discussion
#hashtags (3-5)

Hook Formulas

TypeExample
Honest admission"I've been wrong about [topic]."
Specific observation"I've noticed something in every team that [outcome]."
Contrarian opinion"Most [domain] advice optimizes for the wrong thing."
Personal story"I [did X]. Best thing that ever happened."
Direct challenge"[Common belief] is backwards. Here's why."

Retire these: "I'm excited to announce...", "In today's rapidly evolving...", "This one thing made me $X", humblebrags.

Formatting Rules

  • One sentence per line (mobile readability)
  • Blank line between paragraphs
  • Short paragraphs (1-2 sentences max)
  • Bold key phrases sparingly
  • One emoji max, if any
  • Hashtags at the very end after a line break (3-5, no inline)
  • No external links in the post body (algorithm penalty — put links in first comment)

Post Types

TypeWhen to UseStructure
Story + lessonPersonal experience relevant to ICPHook → context → tension → turning point → lesson → question
List/tipsActionable advice from your domainHook → why it matters → numbered points (3-7) → closing insight
Contrarian takeChallenge conventional wisdomPosition → common belief → your reasoning → evidence → invite discussion
ObservationIndustry pattern you've noticedWhat you observed → evidence → why it matters → question

Algorithm Signals

SignalImpactHow
Dwell timeVery HighLonger posts people read fully
CommentsVery HighAsk genuine questions, create discussion
SavesHighActionable, reference-worthy content
"See more" clicksHighStrong hook
External linksNegativePut links in comments
Editing after postingNegativeDon't edit within first hour

Content Pillars

Pick 3-5 topics you rotate through weekly. Every post should fit one pillar.

PillarWhat It Covers
ExpertiseDomain knowledge, how-tos from your ICP's world
StoriesPersonal experiences, failures, wins
OpinionsTakes on industry trends, contrarian views
Behind the scenesBuilding in public, process insights
Curated insightsData, research summaries, trend analysis

Pre-Posting Checklist

  • Would this stop MY scroll?
  • Is there ONE clear idea?
  • Does it sound like me, not "LinkedIn me"?
  • Is it scannable with short paragraphs?
  • Does it invite genuine engagement (not bait)?
  • No external links in body (moved to comment)?
  • Hook is under 210 characters?

Output

Present the post with:

  • Pillar: which content pillar this fits
  • Hook preview: first 210 characters as the reader will see them
  • Full post: formatted for LinkedIn
  • First comment: link or additional context to post as first comment
  • Best time to post: Tue-Thu, 7-8 AM or 12 PM in your audience's timezone

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.