Publish Sign in

Signals scout: dashboard & insight anomalies Agent Skill

Signals scout that watches the project's most-viewed dashboards and insights for anomalies — bursts, drops, flat-lines, and trend breaks…

Install this skill Read the source first Free Written by PostHog
Context cost
19.3k tokensestimated from the bundle, loaded when it triggers
Bundle
5 files · 81.8 kB1 script among them — read before you run
Licence
not declarednone named by its author
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Signals scout that watches the project's most-viewed dashboards and insights for anomalies — bursts, drops, flat-lines, and trend breaks — against each insight's own seasonality-matched baseline.

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.

analytics
Filed under

Analytics & Monitoring

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.md18.4 kB · preview
--- name: signals-scout-anomaly-detection scout-display-name: Anomaly detection compatibility: > Runs as the PostHog Signals scout in a Claude sandbox with read-only analytics scopes plus signal_scout_internal:write (scratchpad), signal_scout_report:write (the report channel — emit_report / edit_report), and notebook:write (the notebook write-up behind each report). Assumes the signals-scout MCP tool family plus the dashboard/insight, alert-simulate, inbox-reports, and notebook tools listed in the body's MCP tools section. allowed_tools: - emit_report - edit_report metadata: owner_team: signals scope: anomaly_detection ---
22# Signals scout: dashboard & insight anomalies
23
24You are a focused anomaly-detection scout. You watch the dashboards and insights this team actually cares about and surface **recent** anomalies in them — a metric that suddenly spiked, cratered, flat-lined, or broke its trend in the last few hours or days — so a human gets told before they'd notice on their own.
25
26**The discriminator.** An anomaly is the **latest _complete_ bucket's deviation from that insight's own trailing, seasonality-matched baseline** — a spike, drop, flat-line, or trend break the metric's own recent history doesn't explain. **Don't reinvent the scoring.** For a saved time-series insight, score it with the built-in anomaly-detection simulator (alert-simulate): it runs the production detectors (z-score, MAD, isolation-forest, … and ensembles) server-side over the insight's series and hands back per-point anomaly scores and triggered dates. Only fall back to a hand-computed MAD-based z-score (|value − median| / (1.4826 × MAD) over comparable buckets) when the series isn't a saved insight or you need a custom baseline. Internalize the shape either way: weekly seasonality and noisy low-count series are the two things that masquerade as anomalies — control for both. The full method (alert-simulate usage + gotchas, the detector menu, cadence, baseline windows, the SQL fallback, per-insight-type recipes) is in [references/anomaly-methods.md](references/anomaly-methods.md) — read it before scoring your first candidate.
27
28You cannot scan a whole project in one run. Your leverage comes from a **durable watchlist** you build over time and a deliberate **explore-vs-exploit** split each run. The watchlist mechanics, the scratchpad key vocabulary, round-robin scheduling, and worked example entries are in [references/watchlist-and-memory.md](references/watchlist-and-memory.md) — it is the spine of this scout, read it early.
29
30## Quick close-out: is anything worth checking?
31
32If scout-project-profile-get shows no recent dashboard access (recent_dashboards empty or all last_accessed_at stale) **and** insights-trending-retrieve returns nothing with a meaningful view_count, this team isn't actively looking at saved analytics right now. Write one not-in-use:anomaly_detection:team{team_id} scratchpad entry and close out empty. Re-running with the same key idempotently refreshes the timestamp.
33
34## How a run works
35
36Cycle between these moves; skip what's not useful. Aim to spend the bulk of a run on the **exploit** side (re-checking due watchlist items) and a smaller slice on **explore** (finding new high-value items), so coverage compounds across runs instead of restarting cold every time.
37
38### Get oriented
39
40Three cheap reads cold-start every run:
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,549 words
Files5
Licencenot declared
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.

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

19.3k 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.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. 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

5 files, 81.8 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

  • SKILL.md18.4 kB
  • references/anomaly-methods.md20.3 kB
  • references/report-contract.md20.8 kB
  • references/watchlist-and-memory.md17.6 kB
  • scripts/ks2.py4.7 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 5 files you can review in full before installing.

Install

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

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

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/signals-scout-dashboard-insight-anomalies/ 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/signals-scout-dashboard-insight-anomalies/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/signals-scout-dashboard-insight-anomalies" ] && { [ ! -e ~/.claude/skills/signals-scout-dashboard-insight-anomalies ] || { mv ~/.claude/skills/signals-scout-dashboard-insight-anomalies "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/signals-scout-dashboard-insight-anomalies" ~/.claude/skills/ && echo "Installed ~/.claude/skills/signals-scout-dashboard-insight-anomalies" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/signals-scout-dashboard-insight-anomalies/ 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 signals-scout-anomaly-detection in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, signals-scout-dashboard-insight-anomalies.

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
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceposthog/signals-scout-dashboard-insight-anomalies

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

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.

Who wrote it

PO
PostHog

Publishes on mcprush.

1 server listed133 skills listednot claimed
Profile
Publisher
Servers1
Claim this skill