Cross-Project Analytics Agent Skill

Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost…

Context cost
17.7k tokensestimated from the bundle, loaded when it triggers
Bundle
16 files · 70.9 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—v2.1.0
Servers it uses
Noneruns standalone

What it does

Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs, or understanding usage patterns.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

agentsanalyticsdata-visualizationhooksmetricsskillsteamsusage

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md10.8 kB · preview
--- name: analytics license: MIT compatibility: "Claude Code 2.1.277+." argument-hint: "[agents|models|skills|hooks|teams|session|cost|trends|summary]" context: inherit user-invocable: false allowed-tools: "Bash Read Grep Glob AskUserQuestion" effort: low model: haiku metadata: category: document-asset-creation version: "2.1.0" author: "OrchestKit" complexity: "low" tags: "analytics, metrics, usage, teams, agents, skills, hooks, data-visualization, dashboard, recharts, charts, widgets, session, cost, tokens, model-delegation" ---
20# Cross-Project Analytics
21
22Query local analytics data from ~/.claude/analytics/. All data is local-only, privacy-safe (hashed project IDs, no PII).
23
24Answer usage questions from the local files, never from guesswork: agent usage (which agents and how often — not which model, see the caveats) lives in ~/.claude/analytics/agent-usage.jsonl; hook performance and failures live in ~/.claude/analytics/hook-timing.jsonl; token and cost totals live in ~/.claude/stats-cache.json. Query them with jq one-liners (below) and present real counts, not pointers to dashboards.
25
26## Subcommands
27
28Parse the user's argument to determine which report to show. If no argument provided, use AskUserQuestion to let them pick.
29
30| Subcommand | Description | Data Source | Reference |
31|------------|-------------|-------------|-----------|
32| agents | Top agents by frequency and success rate (duration/model unavailable — #3034) | agent-usage.jsonl | references/jq-queries.md |
33| models | Model delegation from **token totals** in stats-cache.json. Per-spawn attribution is unavailable (#3034) | stats-cache.json | references/jq-queries.md |
34| skills | Top skills by invocation count | skill-usage.jsonl | references/jq-queries.md |
35| hooks | Slowest hooks and failure rates | hook-timing.jsonl | references/jq-queries.md |
36| teams | Team spawn counts, idle time, task completions | team-activity.jsonl | references/jq-queries.md |
37| session | Replay a session timeline with tools, tokens, timing | CC session JSONL | references/session-replay.md |
38| cost | Token cost estimation with cache savings | stats-cache.json | references/cost-estimation.md |
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,428 words
Files16
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈230
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
17,495
on trigger
The instruction body and 15 supporting files, read only when the skill fires.
8.9%
of a 200k window
Ten skills this size would take about 89% of the window before you open a file.
050k100k150k200k context window

17.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md asks for Bash, which can write files and reach the network alike, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

The allowed-tools line of this skill’s own SKILL.md asks for Bash, which could do either, so neither is ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

16 files, 70.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md10.8 kB
  • test-cases.json7.6 kB
  • references/cost-estimation.md6.6 kB
  • references/data-locations.md2.4 kB
  • references/jq-queries.md5.8 kB
  • references/otel-fields.md13.6 kB
  • references/otel-gateway-source.md4.3 kB
  • references/session-replay.md3.3 kB
  • references/trends-analysis.md2.1 kB
  • rules/_sections.md1.0 kB
  • rules/_template.md0.3 kB
  • rules/cost-calculation.md1.9 kB
  • rules/data-privacy.md1.6 kB
  • rules/large-file-streaming.md1.8 kB
  • rules/visualization-dashboards.md3.9 kB
  • rules/visualization-recharts.md3.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 16 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Cross-Project Analytics · 17.7k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/cross-project-analytics/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/cross-project-analytics" ] && { [ ! -e .claude/skills/cross-project-analytics ] || { mv .claude/skills/cross-project-analytics "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/cross-project-analytics" .claude/skills/ && echo "Installed .claude/skills/cross-project-analytics"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add yonatangross/cross-project-analytics

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/cross-project-analytics/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/cross-project-analytics/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/cross-project-analytics" ] && { [ ! -e ~/.claude/skills/cross-project-analytics ] || { mv ~/.claude/skills/cross-project-analytics "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/cross-project-analytics" ~/.claude/skills/ && echo "Installed ~/.claude/skills/cross-project-analytics" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/cross-project-analytics/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as analytics in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, cross-project-analytics.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version2.1.0
Publishedno release date on file
PriceFree
Referenceyonatangross/cross-project-analytics

Versions

v2.1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v2.1.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v2.1.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers1
Claim this skill