Skip to content
FunCoding

Search

Search docs, Skills and MCP

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.

数据库与数据1.5kskills/li-audit/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/jakeschincariol/linkedin-agent-skill/li-audit/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

Similar Skills

xlsx
anthropics/skills180k

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

Databases & data

deprecation-and-migration
addyosmani/agent-skills103k

deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

Databases & data

host-observer
thedotmack/claude-mem98k

host-observer

Use this when fulfilling claude-mem observer jobs on Grok Bot: reply only skip_summary or one full observation XML, never prose.

Databases & data

babysit
thedotmack/claude-mem98k

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

Databases & data

mem-search
thedotmack/claude-mem98k

mem-search

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

Databases & data

Agent Cost Report
thedotmack/claude-mem98k

Agent Cost Report

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

Databases & data