devrel-metrics skill (samber): build a developer relations measurement framework

Builds a DevRel measurement framework: five to eight metrics with an attribution rule, baselines, owners and actions.

Installs: 12.5K; on skills.sh
Stars: 7; on GitHub
Files: 4; besides SKILL.md
Updated: Nov 2026; last repo commit

devrel-metrics makes your agent decide which numbers a DevRel program reports and what each is allowed to claim. It picks a measurement spine, shortlists metrics on a five-tier ladder, writes the attribution rule before any target, and attaches an owner and an action to every threshold.

It triggers on how to measure DevRel, which KPIs matter, proving DevRel value to an exec, or when stars, impressions and event counts fail to convince leadership. It decides the metrics; it does not build tracking or the exec report. The folder holds SKILL.md and three reference files and bundles no scripts.

Good for

DevRel leads whose VP asked what stars and event counts are for
Teams defending a DevRel budget who need claims they can support
Open-source projects with nothing to sell that need metrics other than stars

Install devrel-metrics

Claude Code

Copy this prompt.

Install the devrel-metrics skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-relations-skills
/plugin install developer-relations-skills@developer-relations-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The README recommends installing the whole collection because its skills reference each other, and devrel-metrics names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.

From the project README. Source.

What's in the skill

When it loads

Builds a developer relations measurement framework - a handful of metrics tiered from reach to product and business impact, each with a written attribution rule, a baseline-derived target, an owner and an action, and vanity metrics cut. Use whenever someone asks how to measure DevRel, which devrel KPIs matter, which numbers can prove devrel value or ROI to an exec, what belongs in a devrel scorecard, why their numbers look good but leadership stays unconvinced, or reports only stars, impressions and event counts - even if they never say "metrics". Do NOT use for tracking instrumentation and dashboards - use samber/developer-relations-skills@devrel-analytics. Not the exec report itself (samber/developer-relations-skills@devrel-exec-reporting), community-only health, or one event's ROI.

Sections in SKILL.md

Route before measuring
Interview
Workflow
Brainstorm the spine before choosing metrics
The tier ladder
Which tier to build first
Attribution realism
Anti-vanity guardrails
B2B versus individual adoption versus open source
Sourced, self-set, or folklore
Set the thresholds
Write it down, run it, prune it
Invocation examples
Output
Pass threshold
Common failure modes

Key facts

Author: Samuel Berthe (samber)
License: MIT (LICENSE file, SKILL.md, plugin.json and README all say MIT)
Installs on skills.sh: 12,508 (as of Nov 2, 2026)
GitHub stars: 8 for the whole collection repo (Nov 2, 2026)
Last commit: Nov 1, 2026 (whole repo)
skills.sh audits: Gen Agent Trust Hub pass, Socket pass, Snyk pass
What is inside: 5 files including SKILL.md: 3 reference files and evals/evals.json
Version in SKILL.md: 1.0.3
Needs: SKILL.md lists nothing to install. The agent works from data you have, such as product analytics, CRM, forge data or docs analytics
Works in: Claude Code, Claude.ai (plugin marketplace), Codex, Cursor, Gemini CLI and other Agent Skills-compatible tools
Part of: The developer-relations-skills plugin (one plugin in marketplace.json)
Collection size: 93 skills in the repo (counted from the git tree)

What it includes

Sends instrumentation, community health and exec reports to other skills.
It also hands strategy to devrel-strategy first if the program has no named driver; the answer "all of them" is treated as a sponsor problem.
Route before measuring
Asks ten questions one at a time; answers 7, 8 and 10 re-rank the tier ladder.
No engineering days deletes any metric that needs a new event; no sales-ops cooperation deletes influenced pipeline.
Interview
Offers two or three whole spines and never stacks two.
Driver-anchored, journey-stage and function-split.
Brainstorm the spine
Shortlists metrics across five tiers and sets the primary at enablement by default.
Reach, engagement, enablement, product impact and business impact. At least one metric must come from product or business impact.
The tier ladder
Writes the attribution rule before the period starts, choosing among four methods.
Self-reported attribution, tagged links with last-touch analytics, influenced pipeline against a written touch rule, and pre/post lift or a holdout.
Attribution realism
Cuts any metric that fails a monotonic, "so what" or ownership test.
Incentivised volume metrics are paired with a counter-metric, and a metric that changed no decision in two cycles is removed.
Anti-vanity guardrails
Uses three prior periods as a baseline and sets ranges for the first two cycles.
Every threshold is labelled sourced, baseline or hypothesis.
Set the thresholds
Writes a six-section document and checks it against nine pass criteria.
Driver and goals, metric sheet, attribution rule, reporting, known blind spots and review.
Try: “We are an open-source project with nothing to sell. What do we measure instead of stars?”
Measurement framework

From the official docs

Permissions

Low risk

The agent can save notes about your company or project to a file called devrel-context.md, so check that file before you commit or share the folder.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Internal numbers may end up in the notes file
SKILL.md says to store the metric sheet with its baselines and thresholds. Our advice: check devrel-context.md for numbers you do not want shared before you commit it. github.com
The plugin route installs the whole collection
The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	SKILL.md describes no read-only mode.
Scopes	May store the metric sheet, baselines and attribution rule in devrel-context.md when its memory lives in a file

Questions

How do I install devrel-metrics?

The README says to install every skill in the collection, because its skills reference each other. In Claude Code that is the plugin route in the install box above, which adds all 93 skills in the repo. The skills CLI can add just this one. Our advice: pick one route per agent.

What do I get at the end?

A measurement framework with six sections and five to eight metrics. Each metric has a definition, source, baseline, threshold, owner and action, and the framework carries a written attribution rule and a blind-spots section.

devrel-metrics vs devrel-analytics?

This skill decides which metrics matter, and devrel-analytics makes them collectable. SKILL.md says "Do NOT use for tracking instrumentation", and the README describes devrel-analytics as the tracking plan behind these metrics.

Will it give me benchmark numbers to hit?

It will not. SKILL.md labels thresholds as sourced, self-set baselines or folklore, treats numbers like a 24-hour response or 40% seven-day retention as hypotheses, and says to compare the program with its own past.

How should I treat open-source projects?

SKILL.md anchors on the CHAOSS Starter Project Health set (time to first response, change-request closure ratio, contributor absence factor, release frequency) and notes CHAOSS sets no target for any of them. It prefers downloads and dependents to stars.

Does devrel-metrics need an API key, and where does it work?

SKILL.md names no API key, account or environment variable. The README documents installs for Claude Code, Claude.ai (add the repo as a plugin marketplace), Codex, Cursor, Gemini CLI and any Agent Skills-compatible tool through the skills CLI. The install box has the steps for each.

Is devrel-metrics safe to install?

It is instructions plus three reference files, and the folder bundles no scripts. SKILL.md tells the agent to keep your driver, metric sheet, baselines and attribution rule in memory, with devrel-context.md as the file when memory is a file. Our advice: baselines may be sensitive, so keep that file out of a public repo.

Information

updated Nov 2, 2026

Repository: samber/developer-relations-skills
Folder: skills/devrel-metrics

samber/developer-relations-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2

developer-relations-skills README · github.com
devrel-metrics SKILL.md · github.com