Prod Telemetry
UsefulSoftwareCo/executor
Query Executor's production telemetry — Axiom traces (executor-cloud dataset), prod Postgres via PlanetScale, PostHog product analytics — through the Executor MCP.
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with…
OfficialMITAuto-check passed
Install Visualizing Change Over Time
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog-foss visualizing-change-over-time --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .claude/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .claude/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-timeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog-foss visualizing-change-over-time --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .agents/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .agents/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog-foss visualizing-change-over-time --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .cursor/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .cursor/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog-foss.git --path .agents/skills/visualizing-change-over-time--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog-foss visualizing-change-over-time --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .gemini/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .gemini/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog-foss visualizing-change-over-timeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .github/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .github/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog-foss visualizing-change-over-time --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/visualizing-change-over-time .opencode/skills/visualizing-change-over-time && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "visualizing-change-over-time" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/visualizing-change-over-time into .opencode/skills/visualizing-change-over-time/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visualizing-change-over-time", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
visualizing-change-over-time- GitHub stars
- 721
- Token cost
- ~1.5k tokens
- SKILL.md length
- 472 words
- Files
- 1
- Skills in repo
- 213
- Repo updated
- First seen
- Licence
- MIT
At a glance
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with…
- A user asks how something changed
- SKILL.md covers Pick by the shape of the change, Using the SlopeChart and Scope note
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Regressed between two points
What it does
Visualizing Change Over Time is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcpanalytics frontend, custom visualizations). Use when a user asks how something "changed", "moved", "grew", "dropped", "improved", or "regressed" between two points or periods, or mentions "before/after", "period over period", "week over week", "delta", "slope graph"…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with PostHog and Model Context Protocol. The repository describes itself as: PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and… The licence is MIT.
When your agent uses it
- A user asks how something changed
- Regressed between two points
- Mentions before/after
- Period over period
Example prompts
- “changed”
- “dropped”
- “improved”
- “/visualizing-change-over-time”
What it can do on your machine
Read from SKILL.md and the folder at commit 2c48221. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Visualizing Change Over Time loads about 1.5k tokens when it runs. Until then it costs about 180 tokens; SKILL.md has 472 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from PostHog/posthog-foss at commit 2c48221, republished under its MIT licence (© PostHog). 472 words, ~1,545 tokens.
Download SKILL.mdSave it as
.claude/skills/visualizing-change-over-time/SKILL.md (or your agent's skills folder).- name
- visualizing-change-over-time
- description
- Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcp_analytics frontend, custom visualizations). Use when a user asks how something "changed", "moved", "grew", "dropped", "improved", or "regressed" between two points or periods, or mentions "before/after", "period over period", "week over week", "delta", "slope graph", "slopegraph", or comparing many series across two snapshots. Surfaces both the `SlopeChart` quill component and the native `ChartDisplayType.SlopeGraph` insight display as options.
Visualizing change over time
When a request is about how something changed, the default reach is a line/area
trend — and that is usually right for a continuous series with many x points. But for
some change-over-time shapes a different chart reads far better. This skill is the
menu to offer, including the slope graph, when building visualizations with
@posthog/quill-charts.
Present the fitting option(s) and let the user choose — none of these is mandatory.
Pick by the shape of the change
| The change is… | Reach for | Why |
|---|---|---|
| A continuous series over many time points (a trend) | TimeSeriesLineChart / LineChart (area fill for emphasis) | The standard trend; the slope between every pair of points is visible. |
| Two points only (before → after) across several series/categories | SlopeChart | One line per entity from a left "before" to a right "after" — direction and magnitude of each entity's change, and rank flips, read at a glance. |
| Magnitude comparison at points in time (not the path between them) | BarChart / TimeSeriesBarChart | Bars compare discrete values; group/stack for sub-series. |
| A single headline number plus its change vs a prior period | MetricCard | Big number + sparkline + change pill. |
If the user is comparing exactly two snapshots (this week vs last, control vs treatment, Q1 vs Q2) and especially when there are many categories whose relative movement matters, offer the slope graph as the cleaner alternative to a grouped bar or a 2-point line chart.
Using the SlopeChart
import { SlopeChart } from '@posthog/quill-charts'
import type { Series } from '@posthog/quill-charts'
import type { SlopeSeriesMeta } from '@posthog/quill-charts'
// One series per entity; `data` is exactly [start, end].
const series: Series<SlopeSeriesMeta>[] = [
{ key: 'us', label: 'US', data: [120, 185] },
{ key: 'eu', label: 'EU', data: [200, 150] },
]
<SlopeChart
series={series}
labels={['Before', 'After']}
theme={theme}
config={{
showSeriesLabels: true, // name beside each end point; steepest line always keeps its label
legend: { show: true }, // each row shows the color, label, and the formatted change
deltaFormatter: (d) => `${d >= 0 ? '+' : ''}${d}`,
}}
/>Key options (full list in the charts docs/chart-types.md "SlopeChart" section):
showStartLabels/showEndLabels— chart-level defaults for the value labels; override per series withmeta.showStartLabel/meta.showEndLabel.showSeriesLabels— the name labels; on collision the series with the largest change (|end − start|) always keeps its label.legend: { show, position }— rows carry the per-series change (deltaFormatter).- The value axis is hidden by default — the start/end labels are the readout.
The theme comes from useChartTheme(); give the wrapper a real height. See the
charts AGENTS.md for theme wiring and sizing.
Show full SKILL.md (154 more words)Show less
Scope note
There are two ways to render a slope graph; which you reach for depends on the surface:
SlopeChart— the@posthog/quill-chartscomponent. Use it when building UI directly: dashboards, reports, themcp_analyticsfrontend, custom visualizations. It backs the Slope view toggle on Max's inline trends result card (services/mcp/src/ui-apps/components/TrendsVisualizer.tsx).ChartDisplayType.SlopeGraph— a first-class insight display (value'SlopeGraph'infrontend/src/types.ts), rendered by the backendSlopeGraphTrendsQueryRunner(products/product_analytics/backend/hogql_queries/trends/slope_graph_trends_query_runner.py). It takes aTrendsQueryand keeps the first and last bucket of the date range as the two slope points (the last segment is dashed when it's the current, still-accumulating period). Set it viatrendsFilter.display: "SlopeGraph"(trends-only).- The product insight editor includes the slope graph picker entry.
- Via the API /
posthog:insight-createMCP tool, pass aTrendsQuerywithtrendsFilter.display: "SlopeGraph". To frame a clean before-and-after, choose the date range andintervalso the first bucket is your baseline and the last is "now" (e.g. monthly buckets starting from the baseline month).
© PostHog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/visualizing-change-over-time of PostHog/posthog-foss.
Open the folder on GitHubat commit 2c48221
Compare with similar skills
Visualizing Change Over Time next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Visualizing Change Over Time this skillPostHog/posthog-foss | 721 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Prod TelemetryUsefulSoftwareCo/executor | 4.1k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Posthog Product Health Auditboardsesh/boardsesh | 163 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Exploring The WizardPostHog/wizard | 197 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Metabase Prod Queryhaacked/dotfiles | 134 | — | ~1.5k | Automated safety check: Notes | None | |
| Ops Reporthaacked/dotfiles | 134 | — | ~8k | Automated safety check: Notes | None |
Similar skills
Posthog Product Health Audit
boardsesh/boardsesh
Mine Boardsesh's PostHog telemetry (error tracking, session recordings, product analytics) with a multi-agent workflow, then file verified, deduplicated, severity-labelled GitHub issues.
- Official
Exploring The Wizard
PostHog/wizard
Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.
Metabase Prod Query
haacked/dotfiles
Query PostHog production Metabase. An agent skill from haacked/dotfiles.
Ops Report
haacked/dotfiles
Generate a 24-hour operational health report for a PostHog service by querying Grafana dashboards and Prometheus metrics.
Posthog Errors
aeonfun/aeon
Weekly cross-project error overview from PostHog - enumerates every project the OAuth grant covers, pulls the last 7 days of error-tracking issues per project, ranks them by impact, flags what's new…
More from PostHog/posthog-foss
All 213 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog-foss
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog-foss
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog-foss
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog-foss
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog-foss
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog-foss
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Questions about Visualizing Change Over Time
What does Visualizing Change Over Time do?
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with…. Visualizing Change Over Time is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcpanalytics frontend, custom visualizations).
When should I use Visualizing Change Over Time?
Visualizing Change Over Time fits situations like: A user asks how something changed; regressed between two points; mentions before/after; period over period.
How do I install Visualizing Change Over Time in Claude Code?
Run `npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a claude-code`. Or copy the skill folder (.agents/skills/visualizing-change-over-time in PostHog/posthog-foss) into .claude/skills/visualizing-change-over-time in your project. Claude Code loads it when a task matches its description.
How do I install Visualizing Change Over Time in Codex?
Run `npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a codex`. Or copy the skill folder (.agents/skills/visualizing-change-over-time in PostHog/posthog-foss) into .agents/skills/visualizing-change-over-time in your project. Codex loads it when a task matches its description.
Can I use Visualizing Change Over Time in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog-foss --skill visualizing-change-over-time -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visualizing-change-over-time, .gemini/skills/visualizing-change-over-time, .github/skills/visualizing-change-over-time and .opencode/skills/visualizing-change-over-time in your project.
What does Visualizing Change Over Time need to run?
SKILL.md names no scripts, command-line tools or credentials: Visualizing Change Over Time is instructions for the agent only.
Does Visualizing Change Over Time access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Visualizing Change Over Time safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Visualizing Change Over Time use?
Visualizing Change Over Time is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Visualizing Change Over Time use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Visualizing Change Over Time?
Skills that share tags, products or a category with Visualizing Change Over Time: Prod Telemetry (UsefulSoftwareCo/executor, 4.1k stars), Posthog Product Health Audit (boardsesh/boardsesh, 163 stars), Exploring The Wizard (PostHog/wizard, 197 stars) and Metabase Prod Query (haacked/dotfiles, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Visualizing Change Over Time?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog-foss, which has 721 GitHub stars. The repository holds 213 skills in this directory. The repository was last updated on October 7, 2026.
Source: PostHog/posthog-foss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.