agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-post-autopsy/SKILL.md

linkedin-post-autopsy

Skill9 starsChanged 4 months agoMITView on GitHub

Diagnose why a LinkedIn post over- or under-performed against the seven content moves and prescribe the single highest-impact fix. Use after a post has run long enough to have real stats.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Every post is data. This skill reads the post against the moves that drive distribution, reads the engagement ratios, and tells you the one …

    line 9
  2. Distinctive:

    Read the ratios. Comments are the heaviest-weighted signal.

    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 Post Autopsy

Every post is data. This skill reads the post against the moves that drive distribution, reads the engagement ratios, and tells you the one thing to change next time.

Inputs

  • The post text and its stats (impressions, comments, reactions, saves, profile views): $ARGUMENTS
  • The brief (persona, pillars, offer, pains) loads automatically.

Do this

  1. Score the post against the seven moves, one line each, present or missing:
    • Value-lever hook (first line earns the second)
    • Status reframe (shifts how the reader sees themselves or the problem)
    • System, not tips (a repeatable mechanism, not a listicle)
    • Quantified before/after (real numbers, attributed to a post / a client / an operator)
    • Contrarian line (one claim the feed disagrees with)
    • Comment-keyword CTA (asks for a specific word, not "thoughts?")
    • Saveable asset (something worth keeping: a checklist, a teardown, a swipe)
  2. Read the ratios. Comments are the heaviest-weighted signal. An inverted ratio (more comments than reactions) is the viral fingerprint. Note reactions-to-comments, and saves and profile views as intent signals.
  3. Tie the ratio read back to the moves. Which present move drove the signal, which missing move capped it.
  4. Name the single weakest move: the one that, fixed, would have moved this post most.

Output

Return labelled: a move-by-move scorecard (seven rows, present/missing + one-line read), the ratio read (what the comments-to-reactions ratio says about distribution), and THE ONE CHANGE that would have moved it most. Hand the rewrite to /linkedin-humanizer if you redraft the hook.

Rules

  • End on one fix, not a list of five. If you can't reduce to one, you haven't finished reading the stats.
  • Ground every claim in the numbers given. No verdict the stats don't support.
  • Attribute any quoted number to a post / a client / an operator, never a named person or company.
  • No em-dashes.

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.