devrel-analytics skill (samber): write the tracking plan for developer relations

Builds the tracking plan for developer-relations surfaces: events, identity, link tags and funnel views, written as a document.

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

devrel-analytics makes your agent write a tracking plan for docs, blog, repositories, package registries, community venues and off-web appearances. It starts from the decisions the data must change, builds a surface register, corrects for developers blocking client-side analytics, and orders what to build first.

It triggers on a devrel tracking plan, UTM discipline, an event taxonomy for docs, numbers that disagree between tools, or joining docs traffic to signups. It produces a document, not a dashboard or a metric framework. The folder holds SKILL.md and four reference files and bundles no scripts.

Good for

DevRel and docs teams who need to instrument the developer funnel
Teams whose GitHub, registry and analytics numbers do not match
Anyone who wants to know which blog posts or talks drive signups

Install devrel-analytics

Claude Code

Copy this prompt.

Install the devrel-analytics 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-analytics 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 the tracking plan that instruments developer-relations surfaces - docs, blog, repositories, package registries, community venues, and off-web appearances - with an event taxonomy, an identity spine, link-tagging discipline, source-confidence labelling, and funnel views. Use when the user says "devrel tracking plan", "docs analytics", "utm discipline", "event taxonomy for our docs", "our GitHub numbers don't match analytics", "how do we instrument the developer funnel", "join docs traffic to signups", or wants to know why devrel numbers disagree between tools. Instrumentation layer only - which KPIs deserve a target belongs to samber/developer-relations-skills@devrel-metrics.

Sections in SKILL.md

Which numbers you may cite
Interview
Workflow
The blocked-analytics correction
Which instrumentation to build first
Recording how you know
Event taxonomy
Link tagging
Quality gate
Invocation examples
Failure modes
Privacy gate
Reference

Key facts

Author: Samuel Berthe (samber)
License: MIT (LICENSE file, SKILL.md, plugin.json and README all say MIT)
Installs on skills.sh: 12,484 (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 warn
What is inside: 6 files including SKILL.md: 4 reference files and evals/evals.json
Version in SKILL.md: 1.0.2
Needs: SKILL.md lists nothing to install. The plan is written for the web, docs or data team that implements it
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

Asks ten questions one at a time and stops once it can name the surfaces and decisions.
A spreadsheet-and-monthly-export ceiling deletes log analysis, product-side events and CLI telemetry from the plan.
Interview
Starts with one line per decision the data should change.
Every event in the plan must trace to a line here; an event with no decision is deleted.
Write the decision list
Records owner, data source, retention window, bias and what to collect per surface.
It notes that repository traffic history is kept for only 14 days.
Build the surface register
Treats third-party scripts as missing much of a developer audience.
It cites a Plausible study of 58% of a tech audience blocking Google Analytics, and favours ratios within one source over absolutes across sources.
The blocked-analytics correction
Ranks eight things to build by value per hour and deletes what your ceiling rules out.
Tagging vocabulary, snapshot jobs, self-reported source field, docs event collection, identity spine, log analysis, product-side events and CLI/SDK telemetry.
Order the instrumentation
Defines the identity IDs, an Object-Action event taxonomy and a link-tag vocabulary.
It records source, source_basis and source_confidence on each conversion and fails closed when a merge is ambiguous.
Identity spine, events and link tags
Asks for an end-to-end trace on each surface and baselines taken before instrumenting.
It names the surfaces that expire their own history and says to start snapshotting first.
Verify and baseline
Ships a plan with eleven parts and four quality-gate checks.
Decisions, surface register, build order, identity spine, event table, property registry, tagging vocabulary, funnel views, baselines, quality-gate results and known gaps.
Try: “Which blog posts drive signups?”
Tracking plan document

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

Community and contributor data is person-level
SKILL.md has a privacy gate: aggregate person-level data, keep PII out of properties, publish no per-member leaderboard without consent, and check a venue's terms before bulk-exporting content. Our advice: follow it, and ask your privacy owner about retention and deletion on any store you create. github.com
It may keep notes in devrel-context.md
SKILL.md tells the agent to store a few details about the current task or project, and to use a file called devrel-context.md when its memory lives in a file. Our advice: open that file before you commit or share the folder. 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	Asks for an end-to-end trace on each surface and scheduled exports of expiring data May store the surface register and event list in devrel-context.md when its memory lives in a file

Questions

How do I install devrel-analytics?

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?

One markdown tracking plan with eleven parts, from the decision list to known gaps. It carries a version, an owner and a review trigger, and reports the four quality-gate checks alongside it.

devrel-analytics vs devrel-metrics?

This skill builds the instrumentation plan, and devrel-metrics decides which KPIs deserve a target. SKILL.md says instrumentation layer only, and the README describes devrel-metrics as a framework tiered from reach to business impact.

Will it set a docs conversion target for me?

It will not. SKILL.md refuses to set a target borrowed from another company's funnel, routes target-setting to devrel-metrics and offers the baseline-capture plan that would produce a real target.

Why do my registry downloads and docs traffic disagree?

SKILL.md lists causes: a client-side script blocked by the audience, and CI, mirrors and bots counted as installs. It says to refuse to sum two tools and to publish both numbers with their definitions.

Does devrel-analytics 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-analytics safe to install?

It is instructions plus four reference files, and the folder bundles no scripts. The plan asks you to trace each surface end to end and to schedule exports of expiring data, and SKILL.md includes a privacy gate: no PII in event properties, no per-member leaderboard without consent, and a check of a venue's terms before bulk-exporting. Our advice: have whoever owns your consent banner review the plan before it ships.

Information

updated Nov 2, 2026

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

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-analytics SKILL.md · github.com