Product Metrics Dashboard Design
phuryn/pm-skills
Designs a product metrics dashboard: a North Star and input metrics, a definition table with data sources, chart types and alert thresholds, and a screen layout.
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured.
Install Lumen Recon
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-recon --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .claude/skills/lumen-recon && 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 "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .claude/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-reconType 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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-recon --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .agents/skills/lumen-recon && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .agents/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-recon --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .cursor/skills/lumen-recon && 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 "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .cursor/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/lumen-recon--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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-recon --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .gemini/skills/lumen-recon && 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 "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .gemini/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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 jeremylongshore/tons-of-skills-marketplace lumen-reconInstalls 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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .github/skills/lumen-recon && 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 "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .github/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-recon --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-recon .opencode/skills/lumen-recon && 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 "lumen-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lumen-recon into .opencode/skills/lumen-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lumen-recon", 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
lumen-recon- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 250 words
- Files
- 2
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured.
- Works in 6 steps: Detect Environment → Inventory Analytics Stack → Inventory Events Being Tracked → …
- Asked to what are we tracking
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lumen Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in Product & Project Management, covering Product metrics and Product analytics. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Asked to what are we tracking
- Audit our analytics
- What metrics exist
- Analytics inventory
Example prompts
- “what are we tracking”
- “audit our analytics”
- “what metrics exist”
- “/lumen-recon”
Requirements
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepWebFetchWebSearchAskUserQuestion
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 bash).
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
Lumen Recon loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 250 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 250 words, ~1,057 tokens.
Download SKILL.mdSave it as
.claude/skills/lumen-recon/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- lumen-recon
- description
- Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
- allowed-tools
- Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
- version
- 0.6.4
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
Analytics Reconnaissance
You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics.
Steps
Step 0: Detect Environment
Scan for analytics and tracking indicators:
# Analytics libraries
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5
find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -5
# Tracking calls
find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" 2>/dev/null | xargs grep -l "track\|identify\|capture\|logEvent\|analytics\." 2>/dev/null | head -20
# Analytics docs
find . -name "*.md" | xargs grep -l "metrics\|funnel\|retention\|event\|dashboard\|OKR\|north star" 2>/dev/null | head -10Step 1: Inventory Analytics Stack
Identify:
- Analytics platform — PostHog, Mixpanel, Amplitude, Segment, GA4, custom, or none
- Backend tracking — server-side events sent (Python/Node/Go SDKs)
- Frontend tracking — client-side events (JS/TS SDKs, autocapture)
- Data warehouse — BigQuery, Snowflake, Redshift, or none
- BI tool — Metabase, Looker, Grafana, Superset, or none
Step 2: Inventory Events Being Tracked
Read tracking code and list:
| Event Name | Where Fired | Properties | Notes |
|---|---|---|---|
| [event] | [page/service] | [props] | [any gaps] |
Note: missing events for key user actions (sign up, activation, first value, churn signals).
Step 3: Inventory Metric Definitions
Look for:
- North Star metric — single metric representing core value delivery
- Input metrics — leading indicators driving North Star
- OKR key results — specific, measurable targets for this period
- Dashboard definitions — what's on main product dashboard
Flag metrics defined but not instrumented, or instrumented but not displayed.
Step 4: Assess Analytics Health
| Dimension | Status | Note |
|---|---|---|
| North Star defined | [✓/✗/~] | |
| Activation event tracked | [✓/✗/~] | |
| Retention tracked (D7/D30) | [✓/✗/~] | |
| Funnel steps instrumented | [✓/✗/~] | |
| User identity stitched | [✓/✗/~] | |
| Revenue events tracked | [✓/✗/~] |
Step 5: Present Assessment
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Analytics Reconnaissance
**Platform:** [tool] | **Backend tracking:** [✓/✗] | **Frontend tracking:** [✓/✗]
**Total events tracked:** [N or unknown] | **North Star:** [metric or UNDEFINED]
### Events Inventory
| Lifecycle Stage | Events | Gap |
|----------------|--------|-----|
| Acquisition | [N] | [gap or none] |
| Activation | [N] | [gap or none] |
| Retention | [N] | [gap or none] |
| Revenue | [N] | [gap or none] |
| Referral | [N] | [gap or none] |
### Metric Definitions
- **Defined and tracked:** [list]
- **Defined but not tracked:** [list]
- **Not defined:** [key metrics that should exist]
### Critical Gaps
- [RED] [missing event that blocks product understanding]
- [YELLOW] [incomplete tracking or inconsistent naming]
### Recommended Next Step
[Which instrumentation gap to close first]Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
© jeremylongshore, MIT. 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 1 other file in plugins/ai-agency/tonone/skills/lumen-recon of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- .claude-plugin/plugin.json
Open the folder on GitHubat commit cfae287
Compare with similar skills
Lumen Recon 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 |
|---|---|---|---|---|---|---|
| Lumen Recon this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Product Metrics Dashboard Designphuryn/pm-skills | 27k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Feature Analytics Instrumentation Plannermistralai/mistral-vibe | 5.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Data And Funnel Analyticsmanojbajaj95/claude-gtm-plugin | 105 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Analytics Strategyrampstackco/claude-skills | 945 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Amplitude Custom Agent Builderamplitude/builder-skills | 159 | — | ~2.5k | Automated safety check: Pass | None |
Similar skills
- 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.
Data And Funnel Analytics
manojbajaj95/claude-gtm-plugin
Analytics tracking, interpretation, funnel analysis, product metrics, and ROI measurement.
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
Amplitude Custom Agent Builder
amplitude/builder-skills
Helps an Amplitude user design a custom agent by proposing use cases that fit their role and data, shaping a spec, and returning a Global Agent link that builds it.
Analytics Interpretation
gustavscirulis/snapgrid
Interpret app metrics and make data-driven decisions. An agent skill from gustavscirulis/snapgrid.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Questions about Lumen Recon
What does Lumen Recon do?
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Lumen Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured.
When should I use Lumen Recon?
Lumen Recon fits situations like: asked to what are we tracking; audit our analytics; what metrics exist; analytics inventory.
How do I install Lumen Recon in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lumen-recon in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lumen-recon in your project. Claude Code loads it when a task matches its description.
How do I install Lumen Recon in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lumen-recon in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lumen-recon in your project. Codex loads it when a task matches its description.
Can I use Lumen Recon 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 jeremylongshore/tons-of-skills-marketplace --skill lumen-recon -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lumen-recon, .gemini/skills/lumen-recon, .github/skills/lumen-recon and .opencode/skills/lumen-recon in your project.
What does Lumen Recon need to run?
SKILL.md names no scripts, command-line tools or credentials: Lumen Recon is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.
Does Lumen Recon 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 Lumen Recon safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Lumen Recon use?
Lumen Recon is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lumen Recon use?
About 1.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.
What are the alternatives to Lumen Recon?
Skills that share tags, products or a category with Lumen Recon: Product Metrics Dashboard Design (phuryn/pm-skills, 27k stars), Feature Analytics Instrumentation Planner (mistralai/mistral-vibe, 5.1k stars), Data And Funnel Analytics (manojbajaj95/claude-gtm-plugin, 105 stars) and Analytics Strategy (rampstackco/claude-skills, 945 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lumen Recon?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.