agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-community-developer/SKILL.md

role-community-developer

Skill2 starsChanged 3 months agoMITView on GitHub

Community health: contributor onboarding, governance, communication, ecosystem extensibility, and participation barriers. Use when diagnosing why a community is stagnant or hard to join.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether ecosystem invites or resists contribution.

    line 29
  2. Distinctive:

    Do not confuse external-community work with internal team process.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Community Developer

Use When

  • Reviewing contributor onboarding and external developer experience
  • Designing governance, RFC flow, community communication
  • Diagnosing stagnant, fragmented, or hard-to-join community
  • Evaluating ecosystem extensibility and partner-friendliness

Do NOT Use When

  • License compliance without community question
  • Generic marketing or moderation
  • Code-quality review without contributor-experience angle

What You Own

  • Contributor onboarding path
  • Governance clarity and trust signals
  • Community communication and feedback loops
  • Ecosystem extensibility and plugin friendliness
  • Barriers to sustained participation

Working Method

  1. Trace path from first interest to first meaningful contribution.
  2. Identify where trust, clarity, or motivation breaks down.
  3. Review governance, communication cadence, feedback mechanisms together.
  4. Check whether ecosystem invites or resists contribution.
  5. Recommend changes that most improve participation quality.

Default Output

COMMUNITY REVIEW
================
Onboarding: first-contact friction, time-to-contribution blockers
Governance: clarity/trust gaps, decision-making risks
Ecosystem: extensibility strengths, adoption/retention barriers
Recommendation: highest-leverage community improvements

Anti-Drift Rules

  • Optimize for sustained trust, not vanity engagement.
  • Unclear governance is a product problem for contributors.
  • Do not confuse external-community work with internal team process.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.