agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/team-open-source/SKILL.md

team-open-source

Skill2 starsChanged 3 months agoMITView on GitHub

Open source readiness team: licensing, security, contributor experience, and strategic alignment for public collaboration.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Do not conflate community engagement with code readiness.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Open Source Team

Purpose

Decide whether a project is ready to live in public and whether an existing open source surface is healthy enough to scale.

Composition

  • role-open-source-engineer: licensing, dependency hygiene, release process, supply-chain
  • role-community-developer: contributor onboarding, governance, ecosystem health
  • role-security-engineer: attack surface, disclosure readiness, security risk
  • role-technical-product-manager: strategy, roadmap fit, operational cost of openness
  • Synthesis: Devil's Advocate pressure, acceptance

Use When

  • Preparing to open source a project
  • Reviewing health of existing open source project
  • Accepting external contributions at scale
  • Evaluating high-impact dependency or governance change

Do NOT Use When

  • Routine internal code review
  • Live security incident
  • Community moderation with no code-surface question
  • Generic marketing

Workflow

  1. Load truth sources: licenses, dependencies, release process, governance, contributor path.
  2. Review compliance, security, contributor experience, strategy together.
  3. Surface conflicts: openness vs risk, community demand vs product direction.
  4. Synthesize single release or rework recommendation.

Default Output

OPEN SOURCE TEAM REVIEW
=======================
Readiness: release blockers, licensing/dependency blockers
Security: exposure risks, disclosure/supply-chain concerns
Community: onboarding friction, governance/transparency gaps
Strategy: why public now or not, maintenance obligations
Verdict: Ready / Rework / Not Yet, required next actions

Conflict Resolution

  • Open Source Engineer owns compliance and release process. Security Engineer can block on exposure risk.
  • Community Developer flags onboarding friction but cannot override security or compliance blockers.
  • TPM owns strategic fit and operational cost assessment.

Anti-Drift Rules

  • "It compiles" != "safe to publish." Transitive dependencies are part of the release surface.
  • Do not conflate community engagement with code readiness.
  • Maintenance burden is part of the go/no-go decision, not an afterthought.

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.