li-audit — Claude Code skill for LinkedIn post audits
li-audit is a Claude Code skill that reviews LinkedIn posts and analytics to identify patterns in stronger content and inform the next content plan.
MIT ★ 3,812 updated 2026-09-17
/plugin marketplace add Jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skillWhat li-audit does
Give it a LinkedIn analytics CSV, screenshots of post metrics, or post text with reaction counts. The skill ranks posts by engagement rate and reach relative to follower count, rather than treating impressions as the main measure. If present, it also reads ~/.claude/linkedin/log.md for the hook formula recorded for each post.
It compares top and bottom posts across hook, format, length, theme, and whether the author replied to comments within the first hour. Day and time come last. The report includes rankings, evidence-backed findings, and a confidence estimate. Six posts are too few to establish a pattern; the skill treats 30 as enough to see one. You can pass the findings to /li-plan to build the next posting plan from your own results.
What it helps with
- rank LinkedIn posts by engagement rather than impressions
- spot themes and formats in the strongest posts
- check whether posts prompt comments or mostly reactions
- identify content approaches to stop repeating
Example prompts for the agent
- Review this LinkedIn analytics export and rank my posts by engagement.
- Compare my strongest and weakest posts and explain the differences.
- Look at these posts and tell me what to carry into my next content plan.
How to install li-audit
1Plugin marketplace
/plugin marketplace add Jakeschincariol/linkedin-agent-skill/plugin install linkedin-agent@linkedin-agent-skillThis installs the whole linkedin-agent plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a claude-code3Manually: put the files in place
~/.claude/skills/li-audit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/li-audit/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a codex2Manually: put the files in place
.agents/skills/li-audit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a cursor2Manually: put the files in place
.cursor/skills/li-audit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/linkedin-agent-skill skills/li-audit2Manually: put the files in place
.github/skills/li-audit/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill --path skills/li-auditManually: put the files in place
.devin/skills/li-audit/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about li-audit
How do I install li-audit in Claude Code?
Add the marketplace with /plugin marketplace add Jakeschincariol/linkedin-agent-skill, then install the plugin with /plugin install linkedin-agent@linkedin-agent-skill.
What does li-audit do?
It reviews LinkedIn posts using engagement and reach measures, then compares stronger and weaker posts to find patterns in their content.
What should I provide for an audit?
Use a LinkedIn analytics CSV, screenshots of post metrics, or post text with reaction counts. Six posts are not enough to establish a pattern; the skill uses 30 as a useful basis for spotting one.
Source text
SKILL.md · MIT
--- name: li-audit description: >- Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Use when the user pastes their LinkedIn analytics or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to double down on. --- # li-audit The only honest source of what works for an account is that account. Every rule in every LinkedIn guide, including the ones in this pack, is a prior. The user's own last 30 posts are the evidence. ## Input Ask for whichever the user has: - The post analytics export (LinkedIn: Analytics -> Content -> Export). CSV. - Or a screenshot per post with impressions, reactions, comments, reposts. - Or just the posts and their reaction counts, which is enough for a first pass. Also read `~/.claude/linkedin/log.md` if it exists, since it records which hook formula each post used. ## What to actually measure Raw impressions are the least useful number on the page, because they are mostly a function of how many people already follow the user. Compute these instead, and show the working: | metric | how | what it tells you | | --- | --- | --- | | **Engagement rate** | (reactions + comments + reposts) / impressions | whether the post earned its reach | | **Comment ratio** | comments / reactions | whether it started something or just got a nod | | **Reach multiple** | impressions / follower count | whether it travelled past the existing audience | | **Save/send rate** | if available | the strongest single predictor of future reach | Rank by engagement rate and reach multiple, not impressions. A post with 900 impressions and 40 comments beat the one with 12,000 impressions and 6. ## Then find the pattern With the top 5 and bottom 5 side by side, look for what actually separates them, and be willing to conclude something the user will not like: - Hook formula. Which numbers from `hooks.json` are in the top 5? - Format. Text, document, image, video. - Length. - Theme. - Day and time - check this **last**, and only if the other four show nothing. It is almost never the cause, and it is where people want it to be. - First-hour comments. Posts the user replied to inside an hour versus not. State the finding as a claim with the evidence attached, and say how confident it is. With 30 posts you can see a pattern; with 6 you cannot, and you should say that instead of inventing one. ## Output ``` AUDIT · 31 posts · Jun 12 - Sep 5 TOP 5 BY ENGAGEMENT RATE 8.1% #3 Mistake "$18,000 is what no contract cost me" 1,940 imp 6.4% #20 Walk-Away "I fired my highest-paying client" 2,210 imp ... BOTTOM 5 0.4% #5 List "7 tools every founder needs" 11,400 imp ... WHAT THE DATA SAYS 1. Posts where you were the one who looked bad: mean 6.2% vs 1.1% for everything else. n=6. This is your strongest signal and it is not close. 2. Tool listicles get impressions and nothing else. High reach, no comments, no leads. Three of your bottom five. 3. Day of week shows nothing. Your Tuesday mean and your Friday mean are inside the noise. Stop optimising it. STOP: listicles about tools. DO MORE: the ones with a cost you paid, and a number. ``` Then hand the conclusions to `/li-plan` so next week's plan is built on the user's own evidence rather than on defaults.
© Jake Schincariol · MIT · Jakeschincariol/linkedin-agent-skill