PostHog CLI Queries
debugtheworldbot/keyStats
Runs HogQL queries against this project's PostHog data from the terminal using posthog-cli, with bundled scripts for dashboard metadata the CLI itself has no command for.
Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying…
Install Measure Dashboard Requirements
$ npx skills add product-on-purpose/pm-skills --skill measure-dashboard-requirements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills measure-dashboard-requirements --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/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/measure-dashboard-requirements .claude/skills/measure-dashboard-requirements && 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 "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .claude/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirementsType 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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills measure-dashboard-requirements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/measure-dashboard-requirements .agents/skills/measure-dashboard-requirements && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .agents/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills measure-dashboard-requirements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/measure-dashboard-requirements .cursor/skills/measure-dashboard-requirements && 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 "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .cursor/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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/product-on-purpose/pm-skills.git --path skills/measure-dashboard-requirements--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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills measure-dashboard-requirements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/measure-dashboard-requirements .gemini/skills/measure-dashboard-requirements && 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 "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .gemini/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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 product-on-purpose/pm-skills measure-dashboard-requirementsInstalls 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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/measure-dashboard-requirements .github/skills/measure-dashboard-requirements && 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 "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .github/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills measure-dashboard-requirements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/measure-dashboard-requirements .opencode/skills/measure-dashboard-requirements && 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 "measure-dashboard-requirements" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/measure-dashboard-requirements into .opencode/skills/measure-dashboard-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "measure-dashboard-requirements", 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
measure-dashboard-requirements- GitHub stars
- 716
- Token cost
- ~1k tokens
- SKILL.md length
- 450 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying…
- Works in 7 steps: Define the Purpose → Identify the Audience → Specify Key Metrics → …
- Requesting a dashboard
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Measure Dashboard Requirements is an agent skill from product-on-purpose/pm-skills. Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying numbers. Use when requesting a dashboard or formalizing ad-hoc reporting. For the event tracking that feeds the dashboard, use measure-instrumentation-spec instead; instrument first, visualize second.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Data & Analytics, covering Product analytics. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Requesting a dashboard
- Formalizing ad-hoc reporting
Example prompts
- “Use the measure-dashboard-requirements skill to specify what questions a dashboard must answer and the metrics, visualizations, filters, and data…”
- “/measure-dashboard-requirements”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Define the Purpose
- Identify the Audience
- Specify Key Metrics
- Design Visualizations
- Define Filters and Segments
- Document Data Sources
- Set Permissions and Access
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. 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.
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
Measure Dashboard Requirements loads about 1k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 450 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 product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 450 words, ~1,045 tokens.
Download SKILL.mdSave it as
.claude/skills/measure-dashboard-requirements/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- measure-dashboard-requirements
- description
- Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying numbers. Use when requesting a dashboard or formalizing ad-hoc reporting. For the event tracking that feeds the dashboard, use measure-instrumentation-spec instead; instrument first, visualize second.
- license
- Apache-2.0
- metadata.phase
- measure
- metadata.version
- 2.2.0
- metadata.updated
- 2026-07-04
- metadata.category
- validation
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->Dashboard Requirements
A dashboard requirements document specifies what questions a dashboard should answer, what metrics it displays, and how data should be visualized. Clear requirements help data teams build dashboards that actually inform decisions rather than just displaying numbers.
When to Use
- When requesting a new dashboard from data/analytics teams
- To define KPI tracking for a product, feature, or team
- When formalizing ad-hoc reporting into a persistent dashboard
- Before quarterly planning to specify what visibility you need
- When onboarding stakeholders who need self-serve analytics
When NOT to Use
- You need the event tracking that feeds dashboards -> use
measure-instrumentation-spec; instrument first, visualize second - You are designing an experiment readout, not a standing dashboard -> use
measure-experiment-designandmeasure-experiment-results - You want OKR progress scored at cycle close -> use
measure-okr-grader - The questions the dashboard should answer are not yet agreed -> frame outcomes first with
foundation-okr-writerordefine-problem-statement
Instructions
When asked to specify dashboard requirements, follow these steps:
Define the Purpose Start with the questions this dashboard should answer, not the charts it should show. What decisions will this dashboard inform? A dashboard without clear purpose becomes a vanity metrics display.
Identify the Audience Specify who will use this dashboard, how often, and in what context. An executive weekly review has different needs than a team's daily standup board.
Specify Key Metrics For each metric, document: name, business definition (in plain language), calculation formula, data source, and baseline/target values. Ambiguous metrics lead to misaligned dashboards.
Design Visualizations Recommend chart types based on what the data should communicate. Time trends need line charts; comparisons need bar charts; compositions need pie/treemaps. Include dimension breakdowns.
Define Filters and Segments Specify what drill-downs users need: date ranges, user segments, product areas, geographic regions. Anticipate the "slice and dice" questions users will ask.
Document Data Sources Identify where data comes from and any known data quality issues. Note latency requirements.does the dashboard need real-time data or is daily refresh sufficient?
Set Permissions and Access Determine who can view what. Some metrics may need restricted access. Consider both security requirements and organizational politics.
Show full SKILL.md (101 more words)Show less
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete spec fills every template section: Overview; Purpose and Questions; Audience; Key Metrics; Visualization Specifications; Filters and Segments; Data Sources; Access and Permissions; Alerts and Thresholds; Acceptance Criteria; Open Questions; and Appendix.
Quality Checklist
Before finalizing, verify:
- Purpose is framed as questions to answer, not charts to build
- All metrics have clear definitions and calculation formulas
- Data sources are identified and accessible
- Visualization choices match the type of insight needed
- Filters enable the drill-downs users will want
- Refresh frequency matches decision-making cadence
Examples
See references/EXAMPLE.md for a completed example.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/measure-dashboard-requirements of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Measure Dashboard Requirements 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 |
|---|---|---|---|---|---|---|
| Measure Dashboard Requirements this skillproduct-on-purpose/pm-skills | 716 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| PostHog CLI Queriesdebugtheworldbot/keyStats | 1.5k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Retentioneering Contributingretentioneering/retentioneering-tools | 927 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Retentioneering Product Analyticsretentioneering/retentioneering-tools | 927 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Feature Analytics Instrumentation Plannermistralai/mistral-vibe | 5.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Funnel Analysisliangdabiao/claude-data-analysis-ultra-main | 290 | 1 repos | ~781 | Automated safety check: Notes | None |
Similar skills
Retentioneering Contributing
retentioneering/retentioneering-tools
Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal…
Retentioneering Product Analytics
retentioneering/retentioneering-tools
Analyze event logs, clickstreams, user paths, product funnels, retention, behavioral segments, transition graphs, step matrices, sequence patterns, and customer journeys using Retentioneering.
- Official
Feature Analytics Instrumentation Planner
mistralai/mistral-vibe
Plans which analytics events and properties a new feature needs, checks them against the existing event registry, and verifies them per environment.
Funnel Analysis
liangdabiao/claude-data-analysis-ultra-main
Analyze user conversion funnels, calculate step-by-step conversion rates, create interactive visualizations, and identify optimization opportunities.
Event Tracking
linuxfoundation/insights
Add event tracking calls to Vue/Nuxt components in the Insights app using the useTrackEvent composable.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Related
Categories
Questions about Measure Dashboard Requirements
What does Measure Dashboard Requirements do?
Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying…. Measure Dashboard Requirements is an agent skill from product-on-purpose/pm-skills. Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying numbers.
When should I use Measure Dashboard Requirements?
Measure Dashboard Requirements fits situations like: requesting a dashboard; formalizing ad-hoc reporting.
How do I install Measure Dashboard Requirements in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill measure-dashboard-requirements -a claude-code`. Or copy the skill folder (skills/measure-dashboard-requirements in product-on-purpose/pm-skills) into .claude/skills/measure-dashboard-requirements in your project. Claude Code loads it when a task matches its description.
How do I install Measure Dashboard Requirements in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill measure-dashboard-requirements -a codex`. Or copy the skill folder (skills/measure-dashboard-requirements in product-on-purpose/pm-skills) into .agents/skills/measure-dashboard-requirements in your project. Codex loads it when a task matches its description.
Can I use Measure Dashboard Requirements 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 product-on-purpose/pm-skills --skill measure-dashboard-requirements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/measure-dashboard-requirements, .gemini/skills/measure-dashboard-requirements, .github/skills/measure-dashboard-requirements and .opencode/skills/measure-dashboard-requirements in your project.
What does Measure Dashboard Requirements need to run?
SKILL.md names no scripts, command-line tools or credentials: Measure Dashboard Requirements is instructions for the agent only.
Does Measure Dashboard Requirements 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 Measure Dashboard Requirements 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 Measure Dashboard Requirements use?
Measure Dashboard Requirements is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Measure Dashboard Requirements use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.7k tokens, read only when the agent opens those files.
What are the alternatives to Measure Dashboard Requirements?
Skills that share tags, products or a category with Measure Dashboard Requirements: PostHog CLI Queries (debugtheworldbot/keyStats, 1.5k stars), Retentioneering Contributing (retentioneering/retentioneering-tools, 927 stars), Retentioneering Product Analytics (retentioneering/retentioneering-tools, 927 stars) and Feature Analytics Instrumentation Planner (mistralai/mistral-vibe, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Measure Dashboard Requirements?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.