Codflow Update
bighadj22/codflow
Update runbook for a self-hosted CodFlow install — an AI agent following it fetches the latest code from the CodFlow GitHub repo, merges it into an EXISTING checkout, syncs the gitignored…
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
Install Li Audit
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-audit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/li-audit .claude/skills/li-audit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .claude/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-auditType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/li-audit .agents/skills/li-audit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .agents/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/li-audit .cursor/skills/li-audit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .cursor/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill.git --path skills/li-audit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/li-audit .gemini/skills/li-audit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .gemini/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-auditInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/li-audit .github/skills/li-audit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .github/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/li-audit .opencode/skills/li-audit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "li-audit" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit into .opencode/skills/li-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-audit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
li-audit- GitHub stars
- 1.7k
- Token cost
- ~854 tokens
- SKILL.md length
- 357 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
- The user pastes their LinkedIn analytics
- SKILL.md covers Input, What to actually measure, Then find the pattern and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Past posts and asks whats working
What it does
Li Audit is an agent skill from Jakeschincariol/linkedin-agent-skill. 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.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems. It works with LinkedIn. The repository describes itself as: Eleven free Claude skills that run a LinkedIn account: posts off 21 hook formulas, comments, replies, profile score, weekly plan, and a humanizer that strips the AI fingerprint… The licence is MIT.
When your agent uses it
- The user pastes their LinkedIn analytics
- Past posts and asks whats working
- Why did this flop
- Read my analytics
Example prompts
- “s working”
- “why did this flop”
- “read my analytics”
- “/li-audit”
What it can do on your machine
Read from SKILL.md and the folder at commit add2c23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Li Audit loads about 854 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 357 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/linkedin-agent-skill at commit add2c23, republished under its MIT licence (© Jakeschincariol). 357 words, ~854 tokens.
Download SKILL.mdSave it as
.claude/skills/li-audit/SKILL.md (or your agent's skills folder).- 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.
Show full SKILL.md (149 more words)Show less
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.jsonare 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.
© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/li-audit of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Li Audit this skillJakeschincariol/linkedin-agent-skill | 1.7k | — | ~854 | Automated safety check: Pass | MIT | |
| Codflow Updatebighadj22/codflow | 354 | — | ~6.2k | Automated safety check: Notes | Apache-2.0 | |
| Spike Consumer Forkedtestdouble/han | 281 | — | ~655 | Automated safety check: Pass | MIT | |
| Spike Consumer Inlinetestdouble/han | 281 | — | ~659 | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT |
Similar skills
Spike Consumer Forked
testdouble/han
OI-3 spike harness — heavy consumer skill, FORKED arm. An agent skill from testdouble/han.
Spike Consumer Inline
testdouble/han
OI-3 spike harness — heavy consumer skill, INLINE arm. An agent skill from testdouble/han.
Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
More from Jakeschincariol/linkedin-agent-skill
All 11 skills in this repoLi Carousel
Jakeschincariol/linkedin-agent-skill
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
Li Comment
Jakeschincariol/linkedin-agent-skill
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Li Dm
Jakeschincariol/linkedin-agent-skill
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.
Li Human
Jakeschincariol/linkedin-agent-skill
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out.
Li Inbox
Jakeschincariol/linkedin-agent-skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Li Plan
Jakeschincariol/linkedin-agent-skill
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
Related
Works with
Categories
Questions about Li Audit
What does Li Audit do?
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Li Audit is an agent skill from Jakeschincariol/linkedin-agent-skill. Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
When should I use Li Audit?
Li Audit fits situations like: the user pastes their LinkedIn analytics; past posts and asks whats working; why did this flop; read my analytics.
How do I install Li Audit in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a claude-code`. Or copy the skill folder (skills/li-audit in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-audit in your project. Claude Code loads it when a task matches its description.
How do I install Li Audit in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a codex`. Or copy the skill folder (skills/li-audit in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-audit in your project. Codex loads it when a task matches its description.
Can I use Li Audit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/li-audit, .gemini/skills/li-audit, .github/skills/li-audit and .opencode/skills/li-audit in your project.
What does Li Audit need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Audit is instructions for the agent only.
Does Li Audit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Li Audit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Li Audit use?
Li Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Li Audit use?
About 854 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Li Audit?
Skills that share tags, products or a category with Li Audit: Codflow Update (bighadj22/codflow, 354 stars), Spike Consumer Forked (testdouble/han, 281 stars), Spike Consumer Inline (testdouble/han, 281 stars) and Trader Memory Core (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Li Audit?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/linkedin-agent-skill, which has 1,688 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 17, 2026.
Source: Jakeschincariol/linkedin-agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.