What is linkedin-post-analytics?

A read-only tool that copies analytics from your own LinkedIn posts into a networking record. LinkedIn is a professional social network, and post analytics describe how your posts performed.

Use it to record LinkedIn post analytics for networking review or scheduled tracking.

It gives you a saved history of post performance without manually transferring the numbers. It requires approved browser access and an already signed-in LinkedIn account.

linkedin-post-analytics — Skill for Claude Code by tmargolis

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tmargolis/career-navigator --skill linkedin-post-analytics

Clone the repo

git clone --depth 1 https://github.com/tmargolis/career-navigator

Made for: Claude Code.

Or install career-navigator, the plugin that ships this one along with the rest of its 46 skills, 3 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tmargolis/career-navigator/linkedin-post-analytics/github.svg)](https://agentmods.dev/skills/tmargolis/career-navigator/linkedin-post-analytics)

Your own site

<a href="https://agentmods.dev/skills/tmargolis/career-navigator/linkedin-post-analytics"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/linkedin-post-analytics/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tmargolis/career-navigator/linkedin-post-analytics"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/linkedin-post-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,363 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.01363
Opus 5.5	$0.00016	$0.00545
Sonnet 5.5	$0.00008	$0.00273
Haiku 4.5	$0.00004	$0.00136

Measured 1mo ago against content hash 14550878475f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linkedin-post-analytics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/linkedin-post-analytics/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Gate (run first)

Pattern: CONNECTORS.md three-step for this integration: Discover — no standard LinkedIn MCP here; Configure — user logged into LinkedIn in the host browser (they sign in); Browser access — ask Claude in Chrome and/or computer use (neither / one / both). If neither or no tooling, stop—do not scrape without read-only approval for the chosen mode(s).
{user_dir}: Resolve the job-search folder; networking data is {user_dir}/CareerNavigator/networking.json.
Scheduled unattended runs: If this invocation came from /schedule (or user asked for unattended), do not ask interactive browser/tooling questions. Continue only when prior consent is already saved in {user_dir}/CareerNavigator/profile.md under ## LinkedIn:
- LinkedIn slug: <value>
- LinkedIn analytics permission: granted
- LinkedIn analytics mode: chrome | computer | either If any of these are missing, stop with a concise setup message telling the user to run one interactive setup once.

Tool-call guidance

Preferred order: for interactive runs, use the user-approved mode (chrome, computer, or either). If mode is either, try Claude in Chrome first, then computer.

Claude in Chrome path (strict, typed params):

First try tabs_context_mcp with correctly typed values (for example, createIfEmpty must be the boolean true, not the string "true").
If context initialization still fails, call tabs_create_mcp, then retry tabs_context_mcp once.
Then call navigate to the LinkedIn URL.
If navigate fails because tabId is typed incorrectly, retry once with a numeric tabId (integer, not quoted).
If still failing, stop with: "Claude in Chrome couldn't initialize a valid tab context. Open Chrome, confirm you're signed into LinkedIn, and rerun linkedin-post-analytics."

No circular fallback loops:

At most one retry per failing step.
Do not bounce between tools repeatedly.
If chosen mode fails, only try the alternate mode when the saved/approved mode is either.

Read the full file on GitHub · 74 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 74 lines · 39 tokens per session scan A 14550878475f

Subscribe to this mod's changes

linkedin-post-analytics is a skill published in the GitHub repository tmargolis/career-navigator (16 stars, last pushed 27d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,363 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics Marketing and SEO

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens