Deck No. 10 · Project

Open-Source Release

From a private repository to a public one people can build, trust and join.

The first public release of a library or tool that lived in a private repository: history checked for secrets, licence and docs in place, a README that shows the thing working, and a tagged release with notes.

Who it's forMaintainers about to make a repository public, alone or for a small team. You need git, bash and the GitHub CLI signed in, plus Node.js and Chrome for the diagram and the recording. Settle the licence with whoever owns the code before you start. The deck prepares the release; switching the repository to public stays with you.
npx skills add trailofbits/skills@149d7b21f4067765b82e67029730b42d228ef4b4 --skill open-sourcing -g -y && \
npx skills add getsentry/skills@a582c51ee29d0f35e6ac321340796f77d43da733 --skill find-bugs agents-md -g -y && \
npx skills add tt-a1i/archify@8509a3d63e763b4d454ea9aafa1f939545fcb1ea --skill archify -g -y && \
npx skills add vercel-labs/webreel@1504682685514107e48a1696490666eb9ed7da14 --skill webreel -g -y && \
npx skills add mitsuhiko/agent-stuff@0865c849befd2021490679f96a8dee58c84ac857 --skill update-changelog -g -y

Fetches 6 skills from 5 author repos, each pinned to the version we reviewed. Nothing is mirrored. Uses the open-source skills CLI; needs Node.js 22.20 or newer.

What's inside

6 skills. Each card links to its author's repository at the exact version we reviewed.

  1. Open-sourcing a repository 1/6 Release readiness Needs app Takes a private repository to a public release in order: a secrets audit of the full history first, then licence, README, SECURITY.md, CI hardening, branch protection and releases. @trailofbits CC BY-SA 4.0

    Open-sourcing a repository

    The checklist in the right order. Secrets in the git history come first, because that is the one mistake you cannot fix after publication, then licence, docs, CI and releases.

    Needs an app or CLI Community · Trail of Bits CC BY-SA 4.0
    Source trailofbits/skills at 149d7b2
  2. Find bugs 2/6 Code review Reviews every changed line on your branch for bugs and security holes against a fixed checklist, verifies each suspicion, then reports findings without editing code. @getsentry Apache-2.0

    Find bugs

    A last review of the release branch before strangers read it. Every changed line is checked for bugs and security holes, and findings are reported without edits.

    Community · Sentry Apache-2.0
    Source getsentry/skills at a582c51
  3. AGENTS.md maintainer 3/6 Agent instructions Ready Writes and trims AGENTS.md so it stays under 60 lines: verified commands, non-obvious conventions and links to existing docs instead of copied prose. @getsentry Apache-2.0

    AGENTS.md maintainer

    Contributors now arrive with agents. A short AGENTS.md with verified build and test commands is the first file those agents read.

    Works right away Community · Sentry Apache-2.0
    Source getsentry/skills at a582c51
  4. Archify 4/6 Diagrams Needs app Turns a system description or a real codebase into a checked, standalone HTML diagram you can click through: architecture, workflow, sequence, data flow, ERD and more. @tt-a1i Apache-2.0

    Archify

    A clickable architecture diagram drawn from the code, as one HTML file for the docs, so a newcomer sees how the parts connect before reading source.

    Needs an app or CLI Community · tt-a1i Apache-2.0
    Source tt-a1i/archify at 8509a3d
  5. webreel 5/6 Official Browser recording Needs app Records scripted browser demos from a JSON config: clicks, typing and scrolling with an animated cursor and a keystroke overlay, exported as MP4, GIF or WebM. @vercel-labs Apache-2.0

    webreel

    The README GIF, if your project has a web interface. A scripted recording you can run again after every change, with no account and no editor.

    Needs an app or CLI Official · Vercel Labs Apache-2.0
    Source vercel-labs/webreel at 1504682
  6. Update changelog 6/6 Release notes Ready Adds what changed since the last release tag to the Unreleased section of your changelog: only notable user-facing changes, in the file's own style, with pull request numbers. @mitsuhiko Apache-2.0

    Update changelog

    Release notes for the first tag and every one after it: the notable user-facing changes since the last tag, written in your changelog's own style.

    Works right away Community · Armin Ronacher Apache-2.0
    Source mitsuhiko/agent-stuff at 0865c84

Good to know

What you bring

  • git and bash for the two bundled check scripts
  • Optional: gitleaks or trufflehog for the history scan
  • GitHub CLI (gh), signed in to your GitHub account
  • Node.js 18 or newer
  • Chrome, Chromium or Edge for the browser check
  • Node.js with npm

Pick one, not both

  • README: open-sourcing checks what a README must explain but brings no template. crafting-effective-readmes from softaworks/agent-toolkit has templates by project type. That repository has had no commit since March 2026.
  • Licence of the skill: open-sourcing is published under CC BY-SA 4.0, a share-alike licence. That applies to the skill text, not to your project.
  • Plugin: in Claude Code, open-sourcing also installs as a plugin from the Trail of Bits marketplace. Use the plugin or the skill, not both.
  • Review: find-bugs reports on a branch. review-swarm by Thomas Ricouard reviews a diff with four subagents in parallel. Add one, not both.
  • Recording: webreel records a browser. For a command-line tool, record the terminal with a tool of your choice. No card here does that.
  • Pull requests: once contributions arrive, pr-writer and iterate-pr in the Pro Developer pack handle your own pull requests.
  • Announcement: the launch skill in the Marketer pack plans the announcement, and the Product Launch deck covers a full launch day.
Review slipDeck No. 10
  • Every skill file read in full
  • Pinned to a reviewed version
  • Author and licence on every card
  • Requirements and costs disclosed
  • No sponsored skills inside
Last reviewed
Nov 2026
Reviewed