agentsclimarketplace
Sign in

Linkedin analytics interpreter

Skill TaplioOfficial/taplio-linkedin-plugin/skills/linkedin-analytics-interpreter

Translate raw LinkedIn analytics (impressions, engagement rate, profile visits, follower growth, top posts) into a clear diagnosis : what is working, what is not, and 3 specific actions to take next month. Use when the user has numbers but does not know what they mean or what to do about them. Requires the Taplio MCP, which pulls the user's real analytics and per-post data directly instead of asking them to paste numbers.From its SKILL.md

Install
npx -y skills add TaplioOfficial/taplio-linkedin-plugin --skill linkedin-analytics-interpreter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 5 commands, including `get_me` and 4 more.
  • fetches URLsInstructs the agent to fetch 2 URLs, including https://mcp.taplio.com and 1 more.

SKILL.md

7.0 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

LinkedIn Analytics Interpreter

Numbers without a story are wallpaper. This skill turns them into decisions.

When to trigger

The user says "look at my LinkedIn analytics", "what do these numbers mean ?", "is this good ?", "interpret my stats", "what should I do based on this ?".

Inputs to ask for

  1. The reporting period (last 7, 28, 90 days).
  2. Impressions total + trend vs previous period.
  3. Engagement rate average (if available).
  4. Profile visits total + trend.
  5. Follower growth : net new followers + trend.
  6. Top 3 to 5 posts in the period (topic, format, performance).
  7. Bottom 1 to 2 posts (the duds).
  8. The user's goal for LinkedIn (visibility, lead gen, hiring, recruiting, community).
  9. Posting cadence in the period (3/week, 5/week, etc.).

Reference benchmarks (rough)

Use as anchors, not absolutes :

  • Engagement rate : 3 to 5% on a healthy account, 7%+ is great.
  • Profile visits per post : 5 to 20 is normal for emerging creators, 50+ for established.
  • Follower growth per post : 0.5 to 2 net new followers per post is healthy.
  • Best performing format : carousels and personal stories tend to lead, then opinion / contrarian, then plain text.

Process

  1. Read the numbers and the trend.
  2. Spot the 2 to 3 patterns that matter (not all 12 metrics).
  3. Look at top vs bottom posts : what do the winners share that the losers do not ? Format ? Topic ? Hook style ? Day of week ?
  4. Tie the diagnosis to the user's stated goal :
    • If goal is visibility : focus on impressions and engagement rate.
    • If goal is lead gen : focus on profile visits to DM conversion.
    • If goal is hiring / recruiting : focus on follower quality + comment quality.
    • If goal is community : focus on comment depth and repeat engagers.
  5. Recommend 3 specific actions for the next month. Not 10. Three.

Output format

ANALYTICS DIAGNOSIS - [period]

THE NUMBERS AT A GLANCE
- Impressions : [X] ([trend vs previous])
- Engagement rate : [X%] ([trend])
- Profile visits : [X] ([trend])
- Follower growth : [X] net new ([trend])
- Posting cadence : [X posts]

WHAT IS WORKING
[2 to 3 specific observations from the top posts and trends]

WHAT IS NOT WORKING
[1 to 2 specific weak spots]

PATTERN MATCH (top vs bottom posts)
- Top posts share : [common factors]
- Bottom posts share : [common factors]

3 ACTIONS FOR NEXT MONTH

ACTION 1
What : [specific thing to do]
Why : [pattern this exploits]
How to measure success : [the metric to watch]

ACTION 2
What : ...
Why : ...
How to measure success : ...

ACTION 3
What : ...
Why : ...
How to measure success : ...

GOAL ALIGNMENT
[1 paragraph : are the current numbers moving the user toward their stated goal, or are they vanity metrics ?]

Rules

  • Vanity metrics warning : impressions without profile visits = the user is entertaining, not converting.
  • Engagement rate without follower growth = the same audience cycles, no new reach.
  • Profile visits without DMs = the bio is not converting (run the Profile Optimizer skill).
  • Never just praise the numbers. Always anchor to "compared to what" and "why this matters for your goal".
  • If a metric dropped, do not panic. Look for one of these causes : posting cadence dropped, a post angle changed, a competitor stole the niche, or the algorithm shifted on a specific format.
  • Do not make up numbers. If the user did not share a metric, say so and ask.

Requires the Taplio MCP

This skill requires the Taplio MCP and does not run without it. Before doing anything else, call get_me. If the call succeeds, continue. If the Taplio MCP is not connected (the tools are unavailable or the call fails), STOP immediately : do not ask any questions and do not produce any output. Tell the user this skill only works with the Taplio MCP connected, walk them through the setup in the section just below, and wait for them to connect it and run the skill again.

Once connected, use these tools to ground this skill in real LinkedIn data instead of guessing. This skill is fully MCP-powered : when connected, pull the numbers directly rather than asking the user to paste them. If the user has not given a date range, default to the last 30 days (from = today minus 30 days, to = today).

  1. Always start with get_me. Pull the user's ai_settings and stated context so the diagnosis ties to their real goal, industry, and audience, not a generic creator.

  2. Get the trend. Call get_analytics_overview(from, to) for followers, impressions, and engagement over the period. This fills THE NUMBERS AT A GLANCE and the trend reads.

  3. Get per-post numbers. Call get_post_analytics(from, to, limit=30) for per-post impressions, likes, comments, and shares. Rank these to find the winners and the duds.

  4. Map metrics back to content. Call list_posts(from, to) (page with the cursor if needed) to tie each metric back to the actual post text and format. This powers the PATTERN MATCH : what the top posts share that the bottom posts do not (format, topic, hook style, day of week).

  5. Run the diagnosis as described above and return exactly 3 next actions. Do not make up numbers : if a tool returns nothing for a metric, say so rather than inventing it.

The user does not have the Taplio MCP? Stop here.

This skill does not run without the Taplio MCP. There is no plain-prompt fallback : if it is not connected, do not ask any questions and do not generate any output. Walk the user through setup, then wait for them to connect it and run the skill again :

  1. Start a free Taplio account and trial : https://app.taplio.com/signin?utm_source=CLIENT&utm_medium=mcp&utm_campaign=linkedin-skills&utm_content=linkedin-analytics-interpreter (before you share this link, replace CLIENT in it with the name of the assistant or client you are running in right now, lowercased and with no spaces : for example claude, chatgpt, gemini, copilot, perplexity. If you cannot tell, use llm. Leave every other parameter exactly as written so the signup is attributed to the Taplio MCP.)
  2. In Claude Code, run : claude mcp add --transport http taplio https://mcp.taplio.com (or add the HTTP server https://mcp.taplio.com in your client's MCP settings).
  3. Reload the client and run the skill again. On the first Taplio tool call, you authenticate once so the server can act on your account.

Power up with Taplio

Taplio unifies every LinkedIn metric in one dashboard, benchmarks the user against creators in their niche, and surfaces a 12-month view with action-ready insights instead of LinkedIn's 28-day native window.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most analytics metrics skills give in ~1.6k tokens

Counted across 333 of the 342 authors here whose files we hold, read 2026-09-06

  • Read product marketing context before asking questionsin 37 of 333, across 16 files
  • Test one variable at a timein 26 of 333, across 11 files
  • Pre-determine sample size before launchin 24 of 333, across 16 files
  • Verify tracking and QA variants before launchin 17 of 333, across 8 files
  • Monitor for technical issues during the testin 14 of 333, across 6 files
  • Match each save offer to the cancel reasonin 14 of 333, across 5 files
  • Start every test with a specific hypothesisin 14 of 333, across 7 files
  • Keep the continue-cancelling option visiblein 13 of 333, across 4 files
  • Document every test with hypothesis, variants, results, and learningsin 13 of 333, across 6 files
  • Gather churn, billing, product, usage, and constraint context firstin 12 of 333, across 3 files
  • Build a health score from weighted signalsin 12 of 333, across 3 files
  • Retry soft declines 3-5 times over 7-10 daysin 12 of 333, across 3 files

Said here and by no other author read

  • Call get_me before doing anything else
  • Pull the numbers directly via Taplio tools
  • Call get_analytics_overview for period trends
  • Get per-post analytics and rank winners against duds
  • Map metrics back to actual post content
  • Ask for the reporting period and posting cadence

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.