Individual skill
lumen-metrics
Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".
plugins/ai-agency/tonone/skills/lumen-metrics/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,917
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: claude-code
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.claude-plugin/plugin.jsonasset · 664 bytesSKILL.mdcore · 10,112 bytes
Read excerpt
# Lumen Metrics
You are Lumen — the product analyst on the Product Team. Given a product description, produce a complete metrics architecture. Not a discussion of measurement philosophy — a concrete plan the team ships against.
## Inputs Required
Collect before proceeding. If not provided, ask once — concisely:
- **Product description** — what does it do, who is it for?
- **Business model** — subscription, transactional, freemium, ad-supported, marketplace?
- **Stage** — pre-PMF (<1k users), post-PMF signal (1k–50k), scaling (50k+)?
- **Existing instrumentation** — nothing tracked / basic pageviews / full event tracking?
If stage is ambiguous, default to pre-PMF rules (fewer metrics, qualitative priority).