open-source
/open-source
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish", "make project open source", "prepare for open source" DO NOT USE FOR: Git workflow and branching - use git-workflow skill, Code quality and linting - use qa-expert agent, CI/CD pipeline design - use devops-expert agent
- Author
- claude-dev-suite ↗
- Repository
- claude-dev-suite ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish", "make project open source", "prepare for open source" DO NOT USE FOR: Git workflow and branching - use git-workflow skill, Code quality and linting - use qa-expert agent, CI/CD pipeline design - use devops-expert agent
Triggers from the description
Original author description
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish", "make project open source", "prepare for open source" DO NOT USE FOR: Git workflow and branching - use git-workflow skill, Code quality and linting - use qa-expert agent, CI/CD pipeline design - use devops-expert agent
How it works
- When NOT to Use This Skill
- Essential Files Checklist
- Quick Reference Guides
- Decision Flowchart
- License Quick Decision
- Common Anti-Patterns
SKILL.md preview
---
name: open-source
description: |
Open source readiness best practices. Covers licensing, documentation,
community health, CI/CD, compliance, legal, and packaging.
USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT",
"CHANGELOG", "open source readiness", "community health", "OSS compliance",
"SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish",
"make project open source", "prepare for open source"
DO NOT USE FOR: Git workflow and branching - use git-workflow skill,
Code quality and linting - use qa-expert agent,
CI/CD pipeline design - use devops-expert agent
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---
# Open Source Readiness - Core Knowledge
> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `git-workflow` for Git-specific documentation.
## When NOT to Use This Skill
This skill focuses on open source project setup and compliance. Do NOT use for:
- **Git commands and branching** - Use `git-workflow` skill
- **Code quality and static analysis** - Use `qa-expert` agent
- **CI/CD pipeline architecture** - Use `devops-expert` agent
- **Package development (library code)** - Use language-specific skills
## Essential Files Checklist
| File | Purpose | Priority |
|------|---------|----------|
| `LICENSE` | Legal terms for use and distribution | Required |
| `README.md` | Project overview, install, usage, badges | Required |
| `CONTRIBUTING.md` | How to contribute (setup, PR process, style) | Required |
| `CODE_OF_CONDUCT.md` | Community behavior expectations | Required |
| `SECURITY.md` | Responsible disclosure process | Required |
| `CHANGELOG.md` | Version history (Keep a Changelog) | Recommended |
| `GOVERNANCE.md` | Decision-making process | Recommended |
| `.github/CODEOWNERS` | Auto-assign reviewers by path | Recommended |
| `.github/FUNDING.yml` | Sponsorship links | Optional |
| `CITATION.cff` | Academic citation metadata | Optional |
| `NOTICE` | Third-party attributions (Apache 2.0) | Conditional |
## Quick Reference Guides
| Topic | Guide | Covers |
|-------|-------|--------|
| Licensing | [licensing.md](quick-ref/licensing.md) | License selection, SPDX, CLA/DCO, compatibility |
| Documentation | [documentation.md](quick-ref/documentation.md) | README, CONTRIBUTING, CHANGELOG, ADR templates |
| Community and Governance | [community-governance.md](quick-ref/community-governance.md) | Governance models, maintainer path, communication |
| Repository Setup | [repository-setup.md](quick-ref/repository-setup.md) | .github/, templates, CODEOWNERS, branch rules |
| CI/CD and Automation | [ci-cd-automation.md](quick-ref/ci-cd-automation.md) | GitHub Actions, releases, dependency updates |
| Compliance | [security-compliance.md](quick-ref/security-compliance.md) | OpenSSF Scorecard, SBOM, supply chain |
| Legal and Packaging | [legal-packaging.md](quick-ref/legal-packaging.md) | License headers, NOTICE, publishing, signing |
| Metrics and Inclusivity | [metrics-inclusivity.md](quick-ref/metrics-inclusivity.md) | CHAOSS metrics, inclusive language, badges |
## Decision Flowchart
```
Project needs open source setup?
- Just starting? -> Run full Tier 1 setup
- Choose license -> licensing.md
- Create docs -> documentation.md
- Setup repo -> repository-setup.md
- Add CI -> ci-cd-automation.md
- Already has basics? -> Run audit, fill gaps
- Missing compliance files? -> security-compliance.md
- No community docs? -> community-governance.md
- No release process? -> ci-cd-automation.md
- Publishing a package? -> legal-packaging.md
- Growing community? -> community-governance.md + metrics-inclusivity.md
- Compliance audit? -> security-compliance.md + legal-packaging.md
```
## License Quick Decision
| If you want... | Choose |
|-----------------|--------|
| Maximum freedom, simple | MIT |
| Patent protection included | Apache 2.0 |
| Copyleft (derivatives must be open) | GPL v3 |
| Copyleft for libraries only | LGPL v3 |
| File-level copyleft (compromise) | MPL 2.0 |
| Network copyleft (SaaS must share) | AGPL v3 |
| Public domain equivalent | Unlicense or 0BSD |
## Common Anti-Patterns
| Anti-Pattern | Why It Is Bad | Best Practice |
|--------------|---------------|---------------|
| No LICENSE file | Code is NOT open source without one | Always include LICENSE |
| LICENSE in README only | Not legally clear | Separate LICENSE file |
| No CONTRIBUTING.md | Contributors do not know how to help | Clear contribution guide |
| No CODE_OF_CONDUCT | Unwelcoming community signal | Adopt Contributor Covenant |
| Hardcoded secrets | Credential exposure risk | Use environment variables |
| No .gitignore | Accidental binary commits | Comprehensive .gitignore |
| No CI pipeline | Untested contributions | GitHub Actions CI |
| No issue templates | Low-quality bug reports | Structured YAML templates |
| Manual releases | Error-prone, inconsistent | Automated release pipeline |
| No SECURITY.md | Issues reported publicly | Private disclosure process |
Files in this package (9)
- SKILL.md 5 KB
- quick-ref/ci-cd-automation.md 11 KB
- quick-ref/community-governance.md 8 KB
- quick-ref/documentation.md 10 KB
- quick-ref/legal-packaging.md 10 KB
- quick-ref/licensing.md 7 KB
- quick-ref/metrics-inclusivity.md 10 KB
- quick-ref/repository-setup.md 11 KB
- quick-ref/security-compliance.md 10 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · claude-dev-suite/claude-dev-suite | 100 | MIT |
| browser-use/browser-use | 100 | MIT |
Database snapshot: 13.11.2026 · package version 961549ce9599 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100open-sourcing
This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch.… - 100license-compliance
Open source license compliance and SPDX standards. Covers license types, compatibility, auditing with license-checker, and SBOM generation. USE WHEN: user mentions "license", "SPDX", "GPL", "MIT", "Apache", asks about "license compatibility", "license-checker", "copyleft",… - 100community-health-files
Generates and configures open-source project files including README, CONTRIBUTING, LICENSE, CODE_OF_CONDUCT, SECURITY, and CITATION.cff, and sets up GitHub issue/PR templates following community best practices. Use when the user asks about setting up a new open-source project,… - 100oss-license-strategy
Chooses an open-source project's license and contribution policy as one decision - permissive vs weak, strong or network copyleft, dependency-driven compatibility constraints, DCO vs CLA vs nothing, dual licensing and open core, source-available options (BUSL, FSL, Elastic… - 90open-source-contribution
Use when preparing or reviewing an upstream open-source contribution: reproduce an issue, follow maintainer rules, run exact-head checks, prepare a focused PR and reconcile review feedback. Covers fork identity, DCO/CLA gates and local evidence. - 100contributing-to-major-open-source-projects
Use this skill when navigating developer contribution guidelines, signed CLAs/DCOs, and governance in large open-source projects.