PlugWiki

developer-community-health Skill (samber): Health Metrics

Makes Claude build a metric set to measure the health of a developer community and write a report that ends in decisions.

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

developer-community-health routes your question first, then interviews you and builds a metric sheet that covers four pillars: activity, responsiveness, contributor funnel and sentiment. It labels each number as sourced, self-set or folklore, sets baselines before thresholds, and ends with a health report. A diagnosis mode starts from a symptom such as a quiet community.

SKILL.md says not to use it for launching a community or company-wide DevRel KPIs. It bundles one shell script, scripts/contributor-absence-factor.sh, that Claude can run on a local git repository.

Good for

  • Community managers asking whether a Discord, Slack or forum is dying
  • DevRel leads who need a community KPI set or a contributor funnel
  • OSS maintainers judging whether a project is healthy enough to depend on

Install developer-community-health

Claude Code

  1. 1

    Copy this prompt.

    Install the developer-community-health 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. 2

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

Install the whole set, not one skill: the README says the skills reference each other, so picking one leaves those pointers going nowhere. The repo tree holds 93 skill folders. Fourteen of them bundle .py or .sh files; developer-community-health bundles one, scripts/contributor-absence-factor.sh. The tree holds no hooks, agents or MCP config files.

From the project README. Source.

What's in the skill

When it loads

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).

Sections in SKILL.md

  1. Route before measuring
  2. Interview
  3. Workflow
  4. The four pillars
  5. Sourced, self-set, folklore
  6. Thresholds and baselines
  7. Instrumentation reality check
  8. B2B versus individual-adoption communities
  9. Diagnosis mode
  10. Invocation examples
  11. Output
  12. Pass threshold
  13. Failure modes
  14. Memory
  15. References

Key facts

Installs on skills.sh
12,326 (Nov 2, 2026)
Last repo commit
Nov 1, 2026

What it includes

  • Checks what you actually need before building anything

    Read · Route before measuring

  • One question at a time until the metric sheet can be filled

    Read · Interview

  • Starts from one primary outcome, then builds the metric sheet

    Write · Workflow

  • Covers activity, responsiveness, contributor funnel and sentiment

    Write · Four pillars

  • Labels where each number or threshold came from

    Write · Sourced, self-set, folklore

  • Matches the mechanism to how many periods of history you have

    Write · Thresholds and baselines

  • Works from a symptom to the pillar before building the full sheet

    Read · Diagnosis mode

  • Report template with a worked example and a negative example

    The format is in references/health-report-template.md.

    Write · Health report

  • Counts how few people produce half the commits in a local git repository

    Run with --help for options; it takes a repo path, a since-date, a percent and an author-exclude pattern.

    Runs code · contributor-absence-factor.sh

From the official docs

Permissions

Low risk

developer-community-health is planning instructions plus one script, and it may save notes to devrel-context.md. Our advice: check that file before you commit it.

What it can do

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

Watch out for

  • It may save notes to devrel-context.md

    SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com

  • It can run a shell script on your git repo

    The bundled script runs git log on the repository you name and pipes author names through grep, sort, uniq and awk, then prints a count. Its header lists bash, git, grep, sort, uniq and awk as requirements. github.com

  • The whole-set install adds 93 skills, 14 with scripts

    The README says to install every skill. The git tree has 93 skill folders and 14 of them hold .py or .sh files. The tree holds no hooks, agents or MCP config files. github.com

Technical details
Turning on read-onlySKILL.md describes no read-only mode.
Sign-in and keysSKILL.md names no account, key or token.
Scopes
  • Claude writes the plan or report in the conversation

  • May save notes to devrel-context.md when memory lives in a file

  • Can run bash scripts/contributor-absence-factor.sh against a local git repository

Questions

What does developer-community-health do?

It makes Claude turn "how is the community doing?" into a small set of metrics you can collect and read against a baseline. It covers activity, responsiveness, contributor funnel and sentiment.

How do I install it?

Use the install box at the top. The README says to install every skill in the repo because the skills point to each other, so the box shows whole-set routes.

Is my community dying?

It has a diagnosis mode for exactly that. It starts from the symptom, such as a quiet Slack, checks the activity pillar first, then the rest of the sheet.

Does it need scripts or tools?

No. The one script, contributor-absence-factor.sh, is an optional helper; SKILL.md says to compute the figure by hand from a contributor ranking if you cannot run scripts.

How is it different from devrel-metrics?

SKILL.md says not to use this skill for company-wide DevRel KPIs, and names devrel-metrics for that. This skill is about the community only.

Is it safe to install?

Claude can run one shell script that calls git on a repository you point it at. Claude may also save notes to a devrel-context.md file. See the permissions section for the script details.

Information

updated Nov 2, 2026

Folder
skills/developer-community-health

samber/developer-relations-skillsskills.sh

Sources

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

Show all 7
  1. README · github.com
  2. marketplace.json · github.com
  3. plugin.json · github.com
  4. developer-community-health SKILL.md · github.com
  5. LICENSE · github.com
  6. skills.sh listing · skills.sh
  7. developer-community-health scripts/contributor-absence-factor.sh · github.com

Updated Nov 2, 2026.