open-source-publisherlisted

# open-source-publisher Use this skill to audit whether an OSS repository is ready to publish, then help only with missing or weak pieces: recognizable icon, shareable social image, GitHub Pages site, standardized README, CI/CD hygiene, release readiness, and optional donation links. ## Workflow 1. Inspect the repository before editing: - package/tooling files: `go.mod`, `package.json`, `pyproject.toml`, `Cargo.toml`, `Makefile`, etc. - current README, docs, website files, images, workflows, releases, license, funding files - existing product purpose, author, install paths, examples, and public URLs 2. Produce a readiness audit before asking for changes: - `Ready`: publish-critical pieces that already exist and look usable - `Weak`: existing pieces that are present but incomplete, stale, broken, inconsistent, or below the house standard - `Missing`: publish-critical pieces that do not exist - `Optional`: nice-to-have pieces such as donations or extra badges 3. Classify the repository type before recommending changes: - `library`, `CLI`, `web app`, `framework`, `docs site`, or `other` - use the type to decide whether governance, packaging, or presentation work should come first 4. Identify maintainer identity and public home information when they affect publishing: - Ask for the GitHub handle or org name if the repo will have a public owner/maintainer identity, funding links, release notes, or badges - Ask for a canonical website/homepage UR