open-source-best-practices

Automate GitHub project readiness for open-source release.

9|1|Updated Jan 24, 2026

Search Tags:#templates #security #governance #contributing #licensing #open-source #maintainers

Ready to run

npx skills add https://github.com/AndreaGriffiths11/open-source-best-practices --skill open-source-best-practices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-source-best-practices
Source: https://github.com/AndreaGriffiths11/open-source-best-practices/tree/main
Command: npx skills add https://github.com/AndreaGriffiths11/open-source-best-practices --skill open-source-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open Source Best Practices guides teams to prepare GitHub projects for sustainable open-source release by ensuring security, governance, and contributor readiness before going public.

Core Features & Use Cases

Security-first readiness: guides cleaning secrets, setting up vulnerability reporting, and secure onboarding.
Governance & licensing: provides templates and checks for governance, MAINTAINERS, and license decisions.
Documentation templates: provides README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY docs and example workflows for contributors.

Quick Start

Read SKILL.md to begin Phase 1 and run through the 8-phase workflow to ready a project for public launch.

Frequently Asked Questions about open-source-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prepare a private GitHub project for open-source release?▼

To prepare a private GitHub project for open-source release, you must clean security secrets, establish governance, finalize licensing, and set contributor onboarding documentation. This ensures sustainable public launch readiness.

What governance and licensing templates do I need for open-source maintainers?▼

Open-source maintainers need governance documents, MAINTAINERS files, and clear licensing decisions. Providing README, CONTRIBUTING, and CODE_OF_CONDUCT templates ensures proper project governance and licensing compliance.

How do I set up security reporting and clean secrets before going open source?▼

Security reporting and secret cleaning before going open source involves setting up vulnerability reporting protocols and auditing code for hidden credentials. This secure onboarding prevents sensitive data exposure in public repos.

What is the best way to create contributing guidelines and onboarding documentation for public repos?▼

The best way to create contributing guidelines for public repos is using standardized documentation templates. Providing README, CONTRIBUTING, and CODE_OF_CONDUCT docs streamlines contributor onboarding and sets clear expectations.

Can I use an automated workflow to validate project readiness for open-source launch?▼

You can validate project readiness for open-source launch by running an automated 8-phase workflow. This validates SKILL.md structure, checks governance templates, and ensures essential documentation exists before public release.