Skip to content
Marketing
Skill

/analyze-performance

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

From plugin
linkedin-maxxing
417 skills17 commands
Install
$ npx -y skills add warpirate/linkedin-maxxing --skill analyze-performance --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/analyze-performance

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

analyze-performance.SKILL.md
name: analyze-performance
description: |
  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.
license: MIT

Analyze performance

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.

Why this skill exists

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.

When to use this skill

Trigger when:

  • The user has been posting consistently for at least 4 weeks (otherwise the sample is too small)
  • The user wants a quarterly content review
  • The user notices engagement dropping and wants to know why
  • The user is about to commit to a posting cadence and wants to make sure they are pointed at the right pillars
  • The user uploaded an analytics CSV

Do NOT trigger when:

  • The user wants to know about one specific post. Send to review-post.
  • The user has been posting for less than 4 weeks. Tell them honestly: the sample is too small to draw conclusions. Wait.

What you need from the user

The LinkedIn analytics export. They can get this from:

  • LinkedIn Creator dashboard → Content → Export (per-post metrics)
  • LinkedIn data export → larger archive (includes post text)

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:

  • The user's content-plan.md if plan-content has been run (so analysis can group by pillar)
  • The user's voice-profile.md (less important here, but useful for noting voice-related patterns)

How to analyze

Do not throw averages and call it analysis. Three steps:

Step 1: Cluster the posts

Group posts by:

  • **Pillar** (if plan-content was run; otherwise infer 3-5 topical clusters from the data)
  • **Format** (text, carousel, video, article, image)
  • **Hook type** (number, confession, contrarian claim, story, fact, change of mind)
  • **Length** (short < 800 chars, medium 800-1500, long 1500+)
  • **Closing pattern** (question, single sentence, list, CTA)

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.

Step 2: Find the patterns

For each cluster, look at:

  • **Median engagement rate** (use median, not mean; outliers skew means badly)
  • **Dwell-time signal** (when available; otherwise use comments + reactions as proxy)
  • **Comment quality** (count of comments above a substantive threshold, not all comments equal)
  • **Audience signal** (who is engaging: peers, prospects, strangers; visible in the Followers analytics)

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:

  • It shows up at least 3 times
  • The effect size is meaningful (>50% above or below the median, ideally)
  • It is repeatable (not a one-off post that went viral for unrelated reasons)

Step 3: Identify the outliers

Two types matter:

  • **Outperforming outliers:** posts that did far better than the user's median. What did they have in common? This is what the user should do more of.
  • **Underperforming outliers:** posts that did far worse than the user's median. What did they have in common? This is what the user should drop.

Be honest about both. The job is to give the user signal, not to make every post look like a learning.

What to output

# 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.]

A note on what NOT to conclude

The most dangerous outputs of con

Read more
Ships withlinkedin-maxxing

17 Claude Code skills + slash commands for substance-first LinkedIn growth. Profile audit, content drafting (posts, carousels, longform, video, DMs, comments), performance analysis, and a Wikipedia-based humanizer. Anti-template, anti-slop, open source, MIT.

Get the whole plugin

Other skills on linkedin-maxxing.