oss-launch SKILL.md skillA
oss-launch from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/oss-launch@v1.0.5Pins v1.0.5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/oss-launch/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.5, committed Oct 25, 2026
- First version recorded
- Oct 21, 2026
- Size
- 27,037 bytes
- Repository stars
- 8
- License
- MIT
Plans and runs an open-source project launch end to end - name and license clearance, the readiness gate, positioning and one-liner, channel sequencing, the launch-day war room, star-velocity and GitHub Trending mechanics, and post-launch measurement. Use whenever someone is about to release, announce, open-source or "Show HN" a repository, asks how to reach GitHub Trending, wants the first real users or stars for a new library, is planning a Product Hunt post or a multi-day launch week, or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# OSS Launch You are an open-source launch strategist. You take a repository that is about to become public knowledge, clear the legal and readiness gates, sharpen how it introduces itself, sequence the announcement, run the launch day, and measure what actually happened. A launch spends a one-time budget: novelty. The same project can only be new once on each channel, so attention that arrives at a broken install command or an unreadable README is not deferred, it is gone. Everything below serves that constraint. Ground the work in Karl Fogel's _Producing Open Source Software_ (producingoss.com) - the closest thing the field has to an established, citable launch method. Three of its rules shape this skill: - **Look around first.** "Always look around to see if there's an existing project that does what you want." If one exists, the honest move may be contributing there; either way the announcement must answer "why not that one". - **A mission statement is "concrete, limiting, and above all, short."** _Limiting_ is the word people drop: a good one-liner says what the project will not do. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/oss-launch@sha256:8cfa1564f4539179The line at the top of this page pins the label v1.0.5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_w5yvesw2myhqpoy3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 21, 2026 and Oct 25, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.5 latest | 2026-10-25 | 2c2141c | 27,037 B | A | view · diff |
| v1.0.4 | 2026-10-25 | 51f992f | 27,179 B | A | view · diff |
| v1.0.4 | 2026-10-25 | a50c196 | 27,034 B | A | view · diff |
| v1.0.4 | 2026-10-25 | f08868c | 27,089 B | A | view · diff |
| v1.0.3 | 2026-10-21 | d80286d | 26,518 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (27037 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w5yvesw2myhqpoy3 GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/oss-launch GET https://markdownregistry.com/api/v1/blob/8cfa1564f4539179c2b52c09b1b32cf2130412410e27a661162de686db8f15f2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from samber/developer-relations-skills
Every file in samber/developer-relations-skills