Open-Source Pipeline
Safely open-source a private project: a 3-stage pipeline (fork, sanitize, package) that strips secrets, verifies cleanliness, and generates CLAUDE.md, setup.sh, and README.
- What
- Safely open-source a private project: a 3-stage pipeline (fork, sanitize, package) that strips secrets, verifies cleanliness, and generates CLAUDE.md, setup.sh, and README.
- Cost
- Free
- Needs
- Use "Open-Source Pipeline" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a 3-stage pipeline that takes a private project public without leaking secrets. Stage one forks the project into a staging directory and strips credentials, tokens, and private config; stage two runs the sanitizer to verify nothing sensitive survived; stage three packages the result with a generated CLAUDE.md, a setup.sh, and a README so strangers can actually use it. Commands cover the full run (/opensource fork), verify-only, package-only, plus list and status for staged projects. The protocol asks the questions that matter before touching anything: which license (MIT, Apache-2.0, GPL-3.0, BSD-3-Clause), which GitHub org or user, which repo name, and proposes a README description from analyzing the project. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: automated sanitizing catches the obvious, not the clever; always review the staged copy yourself before pushing public, and choose your license deliberately because you cannot take it back. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Open-Source Pipeline" with your Muse. Prerequisites: gh CLI authenticated (used to detect your GitHub user/org). The pipeline stages to ~/opensource-staging/. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/opensource-pipeline/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Open-source this project: [path]. License MIT." 3. Review the staged, sanitized copy in ~/opensource-staging/ yourself before anything goes public. Tip: run "/opensource verify" on an already-public repo to double-check it for leaked secrets. Safety: a skill is plain-text instructions; it runs nothing by itself. Automated sanitizing helps but is not proof; never push the staged copy public without your own review.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.