- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill open-sourcing -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill open-sourcing -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill open-sourcing -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add trailofbits/skills --skill open-sourcing -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/trailofbits/skills/tree/HEAD/plugins/open-sourcing/skills/open-sourcing게시자 제공
Prepare a repository for public release so that an outsider with no prior context can build, use, and contribute to it — and so that nothing sensitive ships with it. Work through the steps in order; the secrets audit comes first because its outcome (keeping vs. recreating the repository) affects everything after it.
bash {baseDir}/scripts/detect_org.sh
The script inspects git remotes and recent committer emails, and prints a
profile name. If it prints trailofbits, read
references/trailofbits.md now and apply its
license policy, publishing accounts, and process notes throughout the
remaining steps. If it prints generic, proceed with the generic guidance
alone. If the user says the detection is wrong, trust the user.
A repository that has ever contained secrets (API keys, credentials, client data) should not be flipped public. History rewriting is error-prone and does not reach forks, caches, or CI artifacts. The reliable fix is a fresh repository: copy the current tree over, commit, and archive the old repository privately.
gitleaks git . or trufflehog git file://. — rather than eyeballing.Reject these rationalizations — this is the one step that cannot be fixed after publication:
bash {baseDir}/scripts/check_readiness.sh
The script prints a checklist of presence indicators (README, LICENSE, CONTRIBUTING, SECURITY.md, CI, tests, semver tags, ...) and warns about tracked files that commonly contain secrets. Treat unchecked items as discussion prompts, not hard failures — a research prototype does not need everything a flagship library needs. Walk through the gaps with the user and fix the ones that matter for this project.
The README is the project's front door. Confirm it explains:
CONTRIBUTING.mdAlso add:
SECURITY.md with vulnerability-reporting instructions (a contact
address or GitHub private vulnerability reporting). For security tooling
this is table stakes.No license means not open source, regardless of visibility. Read references/licensing.md for selection criteria and mechanics. The short version:
LICENSE file, set SPDX identifiers in package metadata, state
the license in the README, and verify all three agree.github-actions so pins stay current.permissions: blocks (start from permissions: {}).zizmor .github/workflows/ and lint with actionlint..editorconfig so contributors' editors agree on whitespace basics.C: component, P: platform). See
blight's labels for a
worked example.vX.Y.Z, following semver; use
-rc.N / -pre.N suffixes for release candidates and prereleases.git tag vX.Y.Z && git push origin vX.Y.Z.Identify the project's languages from its marker files and read the matching reference for packaging, publishing, and quality tooling:
For other ecosystems, apply the cross-cutting principles: reproducible builds from a fresh clone, CI-driven releases, trusted publishing or organization-owned accounts, and license metadata in the package manifest.
Before the visibility switch is flipped, verify from an outsider's perspective:
{baseDir}/scripts/check_readiness.sh and confirm the remaining
gaps are deliberate choices, stated to the user.Making the repository public is then a repository-settings change. Pair the release with an announcement where the organization has a process for one.
scripts/detect_org.sh — prints the organization profile
(trailofbits or generic) from git remotes and committer emailsscripts/check_readiness.sh — prints presence indicators for
release-readiness files and flags tracked files that commonly hold secretsThis 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
---name: open-sourcingdescription: This skill should be used when the user asks to "open source this project", "prepare this repository for…---# plugins/open-sourcing/skills/open-sourcing/SKILL.md개요
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. Provides a release-readiness workflow covering secrets hygiene, licensing, documentation, CI, and language-specific packaging.
FAQ
게시자에게서 plugins/open-sourcing/skills/open-sourcing/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/trailofbits/skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.