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.
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-metrics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lens-metrics --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/lens-metrics .claude/skills/lens-metrics && 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 "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .claude/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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/lens-metricsType 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 lens-metrics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lens-metrics --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/lens-metrics .agents/skills/lens-metrics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .agents/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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 lens-metrics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lens-metrics --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/lens-metrics .cursor/skills/lens-metrics && 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 "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .cursor/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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/lens-metrics--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 lens-metrics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lens-metrics --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/lens-metrics .gemini/skills/lens-metrics && 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 "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .gemini/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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 lens-metricsInstalls 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 lens-metrics -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/lens-metrics .github/skills/lens-metrics && 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 "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .github/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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 lens-metrics -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 lens-metrics --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/lens-metrics .opencode/skills/lens-metrics && 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 "lens-metrics" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/lens-metrics into .opencode/skills/lens-metrics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lens-metrics", 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.
lens-metricsProduce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like.
Lens Metrics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".
Its SKILL.md is about 2.8k 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, OKRs and executive reporting and Product analytics. It works with SQL and dbt. 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.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWrite…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are sql).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Lens Metrics loads about 2.8k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 474 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestionAutomated 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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 474 words, ~2,804 tokens.
.claude/skills/lens-metrics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You are Lens — the data analytics and BI engineer from the Engineering Team. A metric without a precise definition is a guess. A metric nobody acts on is noise.
Write the metrics spec. Write the SQL. Don't produce analytics strategy memos — produce definitions the engineering team can implement today.
Scan workspace for data infrastructure:
dbt_project.yml — dbt metrics layerIdentify what data is available, what schema exists, and what's already tracked.
Before defining any metric, answer for each candidate:
Cut any metric where the honest answer is "interesting." Need a decision, not curiosity.
The ONE metric that best captures whether product delivers value to users.
Write in this exact format:
North Star: [Metric Name]
Definition: [Precise definition — what counts, what doesn't, what time window]
Formula: [count / rate / ratio — expressed unambiguously]
Data source: [table.column or event name]
Why this: [how it connects to actual product value delivered]
Target: [what "good" looks like — absolute or growth rate]
Alert: [what value triggers investigation]Example:
North Star: Weekly Active Projects
Definition: Count of distinct projects with at least one edit, comment, or publish
event in the last 7 rolling days. Excludes projects owned by internal
test accounts (domain: @company.com).
Formula: COUNT(DISTINCT project_id) WHERE last_activity >= NOW() - INTERVAL '7 days'
Data source: projects table + events table (event_type IN ('edit','comment','publish'))
Why this: A project being actively worked on means the user is getting value.
Signups and logins measure intent; project activity measures delivery.
Target: 15% week-over-week growth in first 6 months
Alert: < -5% week-over-week for 2 consecutive weeksLevers that explain why the north star moves. Each one in full:
Metric: [Name]
Definition: [Precise — no wiggle room. "Active" must specify exactly what active means.]
Formula: [Exact calculation]
Data source: [table(s) and columns]
Segment by: [dimensions that matter — plan, cohort, channel, geography, device]
Leading/lagging: [leading = predicts future | lagging = confirms past]
Good: [threshold — what triggers positive action]
Bad: [threshold — what triggers investigation]
Owner: [team or role responsible for moving this]
SQL: [see Step 4]Common KPI categories for product:
Write production-quality SQL for each metric. Each query:
Retention curve (D1/D7/D30):
-- User Retention by Signup Cohort
-- For each weekly cohort, % of users still active at D1, D7, D30
-- "Active" = any event in the events table (not just login)
WITH cohorts AS (
SELECT
user_id,
DATE_TRUNC('week', created_at) AS cohort_week
FROM users
WHERE created_at >= NOW() - INTERVAL '90 days'
),
activity AS (
SELECT DISTINCT
e.user_id,
DATE_TRUNC('day', e.created_at) AS active_day
FROM events e
WHERE e.created_at >= NOW() - INTERVAL '90 days'
)
SELECT
c.cohort_week,
COUNT(DISTINCT c.user_id) AS cohort_size,
COUNT(DISTINCT CASE
WHEN a.active_day BETWEEN
(MIN(u.created_at)::date + 1) AND
(MIN(u.created_at)::date + 1)
THEN a.user_id END) AS retained_d1,
COUNT(DISTINCT CASE
WHEN a.active_day BETWEEN
(MIN(u.created_at)::date + 7) AND
(MIN(u.created_at)::date + 7)
THEN a.user_id END) AS retained_d7,
COUNT(DISTINCT CASE
WHEN a.active_day BETWEEN
(MIN(u.created_at)::date + 30) AND
(MIN(u.created_at)::date + 30)
THEN a.user_id END) AS retained_d30,
ROUND(COUNT(DISTINCT CASE WHEN a.active_day =
MIN(u.created_at)::date + 1 THEN a.user_id END)
::numeric / NULLIF(COUNT(DISTINCT c.user_id), 0) * 100, 1) AS d1_pct,
ROUND(COUNT(DISTINCT CASE WHEN a.active_day =
MIN(u.created_at)::date + 7 THEN a.user_id END)
::numeric / NULLIF(COUNT(DISTINCT c.user_id), 0) * 100, 1) AS d7_pct,
ROUND(COUNT(DISTINCT CASE WHEN a.active_day =
MIN(u.created_at)::date + 30 THEN a.user_id END)
::numeric / NULLIF(COUNT(DISTINCT c.user_id), 0) * 100, 1) AS d30_pct
FROM cohorts c
JOIN users u ON u.user_id = c.user_id
LEFT JOIN activity a ON a.user_id = c.user_id
GROUP BY 1
ORDER BY 1 DESC;Activation rate:
-- Activation Rate
-- Definition: % of users who reach "activated" state within 7 days of signup
-- "Activated" = completed onboarding + created at least 1 project
-- Why 7 days: users who don't activate within a week rarely return
WITH signups AS (
SELECT user_id, created_at AS signed_up_at
FROM users
WHERE created_at >= NOW() - INTERVAL '30 days'
),
activations AS (
SELECT DISTINCT user_id
FROM events
WHERE event_type = 'project_created'
),
onboarded AS (
SELECT DISTINCT user_id
FROM events
WHERE event_type = 'onboarding_complete'
)
SELECT
COUNT(DISTINCT s.user_id) AS signups,
COUNT(DISTINCT a.user_id) AS activated,
ROUND(
COUNT(DISTINCT a.user_id)::numeric /
NULLIF(COUNT(DISTINCT s.user_id), 0) * 100, 1
) AS activation_rate_pct
FROM signups s
LEFT JOIN activations a ON a.user_id = s.user_id
LEFT JOIN onboarded ob ON ob.user_id = s.user_id;Weekly engagement ratio (DAU/WAU):
-- Engagement Ratio: DAU / WAU
-- Measures stickiness — how often weekly actives return daily
-- Benchmark: consumer apps target > 20%, B2B SaaS > 15%
WITH dau AS (
SELECT COUNT(DISTINCT user_id) AS value
FROM events
WHERE created_at::date = CURRENT_DATE - 1 -- yesterday
),
wau AS (
SELECT COUNT(DISTINCT user_id) AS value
FROM events
WHERE created_at >= CURRENT_DATE - 7
)
SELECT
dau.value AS dau,
wau.value AS wau,
ROUND(dau.value::numeric / NULLIF(wau.value, 0) * 100, 1) AS engagement_ratio_pct
FROM dau, wau;For each metric requiring instrumented events (Mixpanel, Amplitude, PostHog, GA4), write tracking spec:
Event: project_created
Trigger: user clicks "Create Project" and the project is successfully saved
Properties:
- project_id: string (UUID)
- project_type: enum ['blank', 'template', 'imported']
- user_id: string (UUID)
- org_id: string (UUID)
- plan: enum ['free', 'pro', 'enterprise']
- created_at: ISO 8601 timestamp
Do NOT fire: on project duplication (use project_duplicated event instead)
Owner: [team responsible for instrumentation]Create SQL view file for each metric so any BI tool can query it directly:
-- metrics/activation_rate.sql
CREATE OR REPLACE VIEW metrics.activation_rate AS
SELECT
DATE_TRUNC('week', u.created_at) AS cohort_week,
COUNT(DISTINCT u.user_id) AS signups,
COUNT(DISTINCT e.user_id) AS activated,
ROUND(
COUNT(DISTINCT e.user_id)::numeric /
NULLIF(COUNT(DISTINCT u.user_id), 0) * 100,
1) AS activation_rate_pct
FROM users u
LEFT JOIN events e
ON e.user_id = u.user_id
AND e.event_type = 'project_created'
AND e.created_at <= u.created_at + INTERVAL '7 days'
GROUP BY 1
ORDER BY 1 DESC;Output complete metrics definition document. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
┌─ Metrics Spec: [Product Area] ─────────────────────────┐
│ Stage: [early/growth/mature] Data source: [stack] │
└────────────────────────────────────────────────────────┘
NORTH STAR
[Metric Name]
[Definition in one sentence]
Target: [value] Alert: [threshold]
KPIS (3–5)
──────────────────────────────────────────────────────────
Metric Definition Target Owner
────────────────── ────────────────────── ──────── ─────
[name] [precise definition] [value] [who]
[name] [precise definition] [value] [who]
IMPLEMENTED
[N] SQL views → [location]
[N] Event specs → [tracking plan location]
Metrics doc → [path]
MISSING DATA
[any metric that requires instrumentation not yet in place]
RULE
Every metric has: precise definition, SQL query, target, owner.
Missing any one of those? It's not a metric — it's a guess.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
SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/lens-metrics of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Lens Metrics 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 |
|---|---|---|---|---|---|---|
| Lens Metrics this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Product Metrics Dashboard Designphuryn/pm-skills | 27k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Analytics Engineerborghei/Claude-Skills | 891 | — | ~3.4k | Automated safety check: Pass | MIT | |
| dbt Snowflake to BigQuery Translatorgoogle/skills | 21k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Monte Carlo Validation Notebooksickn33/agentic-awesome-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Snowflake Developmentsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | MIT |
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.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
google/skills
Translates Snowflake dbt SQL models into standardized BigQuery SQL, keeping Jinja constructs and tracking progress in a migration tasks file.
sickn33/agentic-awesome-skills
Generates SQL validation notebooks for dbt PR changes with before/after comparison queries.
sickn33/agentic-awesome-skills
Comprehensive Snowflake development assistant covering SQL best practices, data pipeline design (Dynamic Tables, Streams, Tasks, Snowpipe), Cortex AI functions, Cortex Agents, Snowpark Python, dbt…
alirezarezvani/claude-skills
A skill your agent uses when writing Snowflake SQL, building data pipelines with Dynamic Tables or Streams/Tasks, using Cortex AI functions, creating Cortex Agents, writing Snowpark Python…
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Lens Metrics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like.
Lens Metrics fits situations like: asked to define KPIs; metrics framework; what should we measure; north star metric.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-metrics -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lens-metrics in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lens-metrics in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-metrics -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lens-metrics in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lens-metrics in your project. Codex loads it when a task matches its description.
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 lens-metrics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lens-metrics, .gemini/skills/lens-metrics, .github/skills/lens-metrics and .opencode/skills/lens-metrics in your project.
SKILL.md names no scripts, command-line tools or credentials: Lens Metrics is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
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.
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.
Lens Metrics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Lens Metrics: Product Metrics Dashboard Design (phuryn/pm-skills, 27k stars), Analytics Engineer (borghei/Claude-Skills, 891 stars), dbt Snowflake to BigQuery Translator (google/skills, 21k stars) and Monte Carlo Validation Notebook (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.