From linkedin-maxxing
Use when user has been posting on LinkedIn at least 4 weeks and wants to know what is landing, run a quarterly content review, or diagnose dropping engagement. Trigger phrases include "analyze my LinkedIn performance," "which of my posts are working," "what should I post more of," "why is my engagement dropping," or when user uploads a LinkedIn analytics CSV.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linkedin-maxxing:analyze-performanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Most LinkedIn AI tools that claim "analytics" either show the user numbers they could see in their dashboard, or generate generic advice based on the numbers without actually reading them. This skill exists to do the analysis work: read the data carefully, group posts by what they had in common, and identify which patterns the user should do more or less of.
Most LinkedIn AI tools that claim "analytics" either show the user numbers they could see in their dashboard, or generate generic advice based on the numbers without actually reading them. This skill exists to do the analysis work: read the data carefully, group posts by what they had in common, and identify which patterns the user should do more or less of.
LinkedIn now exposes more performance data than it used to. The Creator dashboard analytics export includes impressions, unique viewers, clicks, reactions broken out by type, comments, shares, and engagement rates per post. Plus the larger LinkedIn data archive has every post's text content.
But almost nobody actually looks at this data. They glance at impression counts, get discouraged or encouraged, and keep posting. The result is that they never learn what is working. This skill exists to do the analysis the user does not do.
Trigger when:
Do NOT trigger when:
The LinkedIn analytics export. They can get this from:
If the user has only post text and no analytics, the analysis is limited; tell them so and suggest they get the analytics export from the Creator dashboard (instant download, no waiting).
Useful additional inputs:
Do not throw averages and call it analysis. Three steps:
Group posts by:
These clusters are where the insights live. An aggregate "your average engagement rate" tells the user almost nothing. "Your carousels with 8-12 slides get 3.5x the engagement of your text posts, but your text posts with confessional hooks beat the average of both" tells them what to do.
For each cluster, look at:
What you are looking for: clusters that significantly outperform or underperform the user's overall median, in ways that are repeatable.
A pattern is only a pattern if:
Two types matter:
Be honest about both. The job is to give the user signal, not to make every post look like a learning.
# Performance analysis for [user's name or "user"]
Period analyzed: [start - end]
Posts analyzed: [N]
Median engagement rate: [N]%
Overall trajectory: [growing / flat / declining]
## What is working
### Pattern 1: [name of the pattern, e.g., "Carousels on engineering management"]
Posts in this pattern: [N]
Median engagement: [N]% (vs overall median of [N]%)
Why this is working: [one paragraph on what is specific to these posts]
### Pattern 2: ...
[2-4 strongest patterns]
## What is not working
### Pattern A: [e.g., "Posts with motivational hooks"]
Posts in this pattern: [N]
Median engagement: [N]% (vs overall median of [N]%)
Why this is likely failing: [one paragraph]
### Pattern B: ...
[1-3 weakest patterns]
## Notable outliers
### Best-performing post: [date, hook]
Why this likely worked: [analysis]
### Worst-performing post: [date, hook]
Why this likely failed: [analysis]
## Recommendations
1. [Specific, actionable. "Do more carousels on engineering management with confession-style hooks." Not "Improve your engagement."]
2. [Next]
3. [Next]
[3-5 recommendations]
## What I cannot conclude from the data
[Honest note on the limits of the analysis: small sample sizes, missing dwell time data, posts where the variable changes too much to isolate, etc.]
The most dangerous outputs of content analytics are wrong patterns the user then optimizes for. Avoid:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub warpirate/linkedin-maxxing --plugin linkedin-maxxing