agentleFS
HemanthMChakravarthyHemanthMChakravarthy/linkedin-agent-skills/skills/li-audit/SKILL.md

li-audit

Skill2 starsChanged 43 days agoMITView on GitHub

Post-mortem on the user's published LinkedIn posts: rank by engagement rate and reach multiple, not impressions, and turn the results into next week's plan inputs. Use when the user asks "audit my posts", "what worked", pastes post stats, or wants a performance review. Reads the log file; diagnoses; prescribes.

7 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

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the history: ~/.agents/linkedin/log.md (then the Claude/Copilot fallbacks), which li-post appends to on every approved post.

    line 18
  2. Distinctive:

    Do not recommend posting more as the fix for low engagement.

    line 69
  3. Distinctive:

    If a post the user loved flopped, say so kindly and say why.

    line 71
  4. Very specific:

    Write the prescription into the next li-plan run.

    line 73

“Common” is measured: kept by at least 6 in 10 of the 7 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

li-audit

What already went out, judged honestly. Ranks by the metrics that matter, finds the pattern, and feeds the result straight into next week's li-plan.

Before you audit

  1. Read the history: ~/.agents/linkedin/log.md (then the Claude/Copilot fallbacks), which li-post appends to on every approved post. If the log is empty or missing, ask the user to paste their recent posts with stats.
  2. Get the numbers per post: impressions, reactions, comments, reposts, and ideally profile follows or DMs attributed. Work with what exists; mark missing metrics as unknown rather than inferring them.

The metrics that matter

Compute per post, and rank by these, not by raw impressions:

  • Engagement rate = (reactions + comments + reposts) / impressions. The headline metric. Above 3% is strong for most niches.
  • Reach multiple = impressions / follower count. Above 3x means the algorithm carried it beyond the audience.
  • Comment quality. Count substantive comments separately from congratulations. Ten "great post"s lose to two real questions.
  • Conversion. Profile visits, follows, DMs, leads. Self-reported; take the user's word.

Show the ranking table with all four columns. Then say what the table means in two sentences. Tables do not interpret themselves.

The diagnosis

Find the pattern across the top 3 and bottom 3:

  • Hook family: which of the 21 formulas won? (Cross-check with hooks.json.)
  • Format: text vs carousel vs repurposed.
  • Pillar: which content pillar is carrying the account?
  • Topic: what subject, specifically, not "AI content".
  • Length and structure: did the winners share a shape?

Then the prescription, as inputs to li-plan:

AUDIT
posts reviewed: 12 (4 weeks)
top:     "The proposal story" - 4.1% engagement, 6.2x reach (hook #17, story)
bottom:  "AI trends 2026" - 0.8% engagement, 1.1x reach (generic take)
pattern: stories with numbers travel; generic takes die
prescribe: 2 story posts next week, kill the trends pillar, test carousel
           for the framework post

Rules

  • Judge the post, not the person. "This post failed" is useful; "your writing is weak" is not.
  • Small samples lie. Under 8 posts, present findings as hypotheses with "test:" labels, not conclusions.
  • Do not recommend posting more as the fix for low engagement. The fix is almost always sharper ideas or better hooks, not volume.
  • If a post the user loved flopped, say so kindly and say why. The audit is the one skill allowed to disagree with the user's taste.
  • Write the prescription into the next li-plan run. An audit nobody acts on is entertainment.

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.