What it does
Designs and runs a developer community health measurement framework: activity, responsiveness, contributor-funnel and sentiment metrics, honest instrumentation, baseline-derived thresholds, and a report that ends in decisions
Skills ZICQ category:Design developer-community-health
Designs and runs a developer community health measurement framework: activity, responsiveness, contributor-funnel and sentiment metrics, honest instrumentation, baseline-derived thresholds, and a report that ends in decisions. Use whenever someone asks how to measure their developer community, which community health metrics to track, whether their Discord, Slack or forum is dying, why the community feels quiet, or wants a community health dashboard, contributor funnel, community KPI set or engagement report - even if they only say "is our community doing OK". Do NOT use for launching a community (samber/developer-relations-skills@developer-community-launch) or company-wide devrel KPIs (samber/developer-relations-skills@devrel-metrics).
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Designs and runs a developer community health measurement framework: activity, responsiveness, contributor-funnel and sentiment metrics, honest instrumentation, baseline-derived thresholds, and a report that ends in decisions
ever someone asks how to measure their developer community, which community health metrics to track, whether their Discord, Slack or forum is dying, why the community feels quiet, or wants a community health dashboard, contributor funnel, community KPI set or engagement report -
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Developer Community Health; Route before measuring; Interview; Workflow; The four pillars; Sourced, self-set, folklore. It includes spec-recommended sections: step-by-step instructions, input/output examples.
File analysis: besides SKILL.md, the body references references/metric-catalog.md, references/survey-instruments.md, scripts/contributor-absence-factor.sh, references/health-report-template.md. Those resources load on demand.
Developer Community HealthRoute before measuringInterviewWorkflowThe four pillarsSourced, self-set, folkloreThresholds and baselinesInstrumentation reality checkB2B versus individual-adoption communitiesDiagnosis modeInvocation examplesOutput
· License:MIT
Source category:skills.sh agent-skill
namedeveloper-community-healthdescriptionreferences/metric-catalog.mdreferences/survey-instruments.mdscripts/contributor-absence-factor.shreferences/health-report-template.mdThese paths are extracted from the text. Check the upstream package to verify the files exist.
Invocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "developer-community-health" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-9d1dfaee95f44d04-Developer-Community-Health.html Save it as .cursor/skills/developer-community-health/SKILL.md or .claude/skills/developer-community-health/SKILL.md and keep the frontmatter name and description exactly as-is. This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/samber/developer-relations-skills instead of creating only a SKILL.md.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/samber/developer-relations-skills' --list
npx skills add 'https://github.com/samber/developer-relations-skills' --skill 'developer-community-health'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
You are a community measurement analyst. Turn "how is the community doing?" into a small set of metrics the team can actually collect, read against a baseline, and act on.
Community dashboards fail in one of two ways:
A good framework is short, instrumentable with the access the team has today, and wired to a decision.
Check what the user actually needs:
samber/developer-relations-skills@developer-community-launch.samber/developer-relations-skills@developer-community-moderation.samber/developer-relations-skills@oss-issue-triage.samber/developer-relations-skills@oss-contributor-onboarding.samber/developer-relations-skills@developer-champions.samber/developer-relations-skills@devrel-metrics.samber/developer-relations-skills@devrel-analytics. Define community metrics here. Instrument them there.This skill measures a community that already exists - a chat/forum space, an open-source contributor base, or both. Say which skill fits and stop if it is not this one.
Ask one question at a time, multiple-choice when the options are knowable. Stop once you can fill the metric sheet. Do not run the list mechanically.
Questions 5, 10 and 12 are not the same question:
Ask all three. Skip one and the framework dies at instrumentation or at legal.
Answers to 7, 8 and 9 re-rank the two menus below, and say which moved what:
If the user arrives with a symptom ("nobody posts anymore") rather than a mandate, run the workflow in diagnosis order: measure the pillar the symptom points at first, then fill the rest.
Two rules shape the work before it starts. CMX's own instruction for the SPACES model is to "just focus on one objective." Hence a single primary outcome in step 2.
Steps 5-8 are one pass over the same artifact, the metric sheet: a row is finished when it carries a formula, a baseline, a labeled threshold and an owned action - the same parts the Pass threshold checks.
Cover all four before publishing a sheet. A community can look busy and be dying, or look quiet and be perfectly healthy for its size - one pillar alone never tells you which. The order below is which pillar earns its first metric first when the hours arrive one at a time, not permission to drop the last one.
Rank the pillars by decisions bought per hour of collection, not by how easy each is to pull:
The three-way compliance tie is genuine and not an evasion: none of those three collects anything a member did not already post in the open, so none triggers a review. Sentiment is alone on that axis because it creates data that did not exist before you asked.
| Pillar | Question it answers | Metrics, most decisions per hour first | | ------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Responsiveness | Does a person who shows up get an answer? | median time to first human response, % of questions with zero replies, change-request closure ratio | | Contributor funnel | Do newcomers become regulars? | contributor absence factor, first-time participants per period, second-contribution rate within 90 days (a self-set window), active-member retention by join cohort | | Activity | Is anything happening, and who makes it happen? | share of activity from non-staff, active contributors/posters per period, burstiness vs steady trend, channel concentration | | Sentiment | Do people want to be here, and are the load-bearing people still standing? | burnout signals on maintainers, recommendability (NPS-style survey item), newcomer welcome items |
Efficiency starves sentiment: it is the only pillar high on value and high on effort, so it loses every round and a sheet built on the ratio alone never asks anyone anything. Promote it to first anyway when the worry behind the request is about people rather than volume - a maintainer showing burnout signals, a newcomer complaining, or a quiet room whose activity numbers look fine. That case is exactly the one the numbers cannot reach.
This order is a default, not a law: it assumes a code-centric community whose forge is readable and whose team is small. Re-rank it against what the interview already surfaced:
See ./references/metric-catalog.md for each metric's definition, formula, data source and the published guidance behind it. See ./references/survey-instruments.md for the sentiment side: question bank, cadence, sampling and privacy limits.
Keep only metrics that survive the "so what" test: if the number moved 20% next month, would anyone do anything differently? If not, it is not a health metric for this community.
Name the funnel stages with one vocabulary and keep it. Orbit's explorer → participant → contributor → advocate ladder is a published option (the model is no longer actively developed - cite it as a stable framework), and a core/regular/casual split is another. Two vocabularies in one sheet make every cohort definition ambiguous.
Every number in a health report arrived by one of three roads, and a table cell hides which. A published figure, your own working convention and an unsourced threshold all look identical on the page - until someone defends the wrong one in the next budget meeting. Label the origin every time.
| Kind | Examples in this skill | How to present it | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Published and attributable | 90-9-1 participation inequality (Nielsen, 2006); VMware's guideline that every PR gets a human response within two business days, quoted inside the CHAOSS Starter Project Health model; the contributor absence factor definition and its worked example | name the source and its scope - VMware's line is one company's internal rule, not an industry standard | | Self-set baseline | this community's trailing median over three periods; the eight-metric ceiling; the ~30-event small-N floor; the 90-day second-contribution window; monthly review cadence; the hour-a-month instrumentation bar | say it is a working convention and what evidence would change it | | Folklore | 24-hour response, 20% monthly-active ratio, 40% seven-day new-member retention, 30% staff share of messages | quote only as a hypothesis, marked unsourced, and replace it with the community's own trailing median after three periods |
CHAOSS's Starter Project Health model - the vendor-neutral reference set most of this field quotes - publishes no numeric cutoff of its own. It says the opposite: "it's important not just to look at the numbers, but also at the trends", and "we do not compare projects against each other, but instead, we expect teams to use their metrics to make improvements". So when someone hands you an "industry-standard" community benchmark, it did not come from the reference set - ask where it did come from, and label it accordingly.
Thresholds mature with history. Match the mechanism to how many periods the community has:
Two reading rules apply at every stage:
Rank each candidate metric by what its data source returns per hour spent collecting it, not by what the source costs. The two orderings only coincide when the community lives on a forge:
Default rung: 1, plus 2 when the community is not code-centric. Move up one only when the metric you actually need is uncomputable below, never because the higher rung looks more rigorous.
Delete a rung the interview ruled out instead of leaving it as future work: a team with no budget and no pipeline owner has no rung 3, and a chat-only community has no rung 1. A ruled-out rung parked at the bottom of the sheet comes back as scope at the next review.
Four traps silently corrupt the numbers:
Privacy is a hard gate, not a footnote. Health measurement can create real privacy and compliance exposure.
Optional helper: scripts/contributor-absence-factor.sh computes the contributor absence factor from a local git repository when a shell and git are available. Run bash scripts/contributor-absence-factor.sh --help for usage. Compute it by hand from any contributor ranking if you cannot run scripts.
The pillars hold for both. The units and the reading change.
B2B (members belong to customer accounts). The unit is the account, not the person. Count how many customer accounts have at least one active member, and whether the accounts you care about are represented.
Low volume is normal: a 40-account community produces small-N numbers everywhere. Lean on the raw list and on named-account conversations rather than rates - a sentiment survey with six responses tells you less than three interviews. Deflection and expansion signals matter more than raw growth.
Individual adoption and open source. Volume makes the funnel and the lurker ratios readable, so cohort retention, second-contribution rate and concentration measures do real work here. Sentiment comes from surveys with honest response-rate caveats. A high one-and-done contributor rate is normal in open source - it becomes a finding only when it moves after a change you made.
Same for both:
When the user arrives with a symptom, work from the symptom to the pillar rather than building the full sheet first.
| Symptom | Measure first | Causes to check first | | --------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | "It has gone quiet" | activity trend by month, staff vs member share, burstiness | the spike was an event, not growth; staff stopped seeding; the audience moved venue | | "People ask but nobody answers" | time to first response, % questions with zero replies | too few answerers awake in the asker's timezone; questions land in the wrong channel; experts left | | "Newcomers never come back" | join-cohort retention, second-contribution rate, newcomer survey items | first answer took too long; onboarding path unclear; the room reads as staff-only | | "One person carries everything" | contributor absence factor, maintainer burnout signals | genuine bus-factor risk; delegation never happened | | "Leadership wants proof of value" | the primary-outcome metric plus one funnel metric | the community was never tied to a stated outcome |
State plainly when the honest answer is that the community should be folded back into a smaller surface. Keeping a dead room open costs trust every time a newcomer posts into silence.
Typical openings, and what each one should produce:
Expected output shape, in order:
Produce a community health report. Structure, worked example and a negative example: ./references/health-report-template.md.
Cadence follows the audience: a monthly working read for the people who run the community, a quarterly roll-up for whoever funds it. Do not build a real-time dashboard for a community that reviews its numbers once a month.
The framework is done when the metric sheet scores 100% on this check. Iterate until it does.
Every metric has all five:
Plus: at most 8 metrics, at least one per pillar, and no metric that fails the "so what" test.
If your harness has persistent memory, store the primary outcome, the final metric sheet, baselines and thresholds after the user validates them. The next review then starts from the recorded baseline instead of re-deriving it, and a threshold change becomes visible as a decision rather than a silent edit.
Design
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to autom…
Design
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, info…
Design
Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.
Design
Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queu…