Li Audit logo

Li Audit

CommunityPopular
Jakeschincariol
li-audit

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.

Overview

PublisherJakeschincariol
Repositorylinkedin-agent-skill
Skill nameli-audit
Stars
1.3K
Forks
192
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Jakeschincariol on GitHub. Read the source before you install it.

Installation

Install the Li Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git /tmp/linkedin-agent-skill
mkdir -p .claude/skills
cp -r /tmp/linkedin-agent-skill/skills/li-audit .claude/skills/li-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Li Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Li Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Li Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

metrichowwhat it tells you
Engagement rate(reactions + comments + reposts) / impressionswhether the post earned its reach
Comment ratiocomments / reactionswhether it started something or just got a nod
Reach multipleimpressions / follower countwhether it travelled past the existing audience
Save/send rateif availablethe 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.

Frequently asked questions

What does the Li Audit AI skill do?

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.

Why use Li Audit on TypingMind?

Because you install it once and use it with any model. Li Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Li Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-audit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Li Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Li Audit?

As many as you like. As long as a model supports skills, you can use Li Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Li Audit AI skill free?

Yes. It is published on GitHub by Jakeschincariol under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇