launch-kit
Skill0 starsChanged 16 days agoMITView on GitHub
Trigger: launch kit, prepare a launch, launch assets, taglines, gallery images. Build the asset kit every launch channel reads from.
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- omnigami-ai/pro-skillstheir own version, first seen Nov 16, 2026
- miraya-dev/launch-kittheir own version, first seen Nov 8, 2026
- thanatchon36/skillstheir own version, first seen Oct 15, 2026
- Barbhuiya12/launch-kittheir own version, first seen Sep 22, 2026
- chaoz23/agent-native-launch-kittheir own version, first seen Jul 17, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- chaoz23/agent-native-launch-kit★ 1same name
- miraya-dev/launch-kit★ 1same name
- Barbhuiya12/launch-kit★ 0same name
- omnigami-ai/pro-skills★ 0same name
- thanatchon36/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- launch-community-draftsSkill
- launch-cross-postSkill
- launch-directoriesSkill
- launch-listsSkill
- launch-trackerSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use before launching a tool, or when another launch skill finds docs/launch/<slug>/kit.md missing or incomplete.
- Distinctive: line 16
Every fact comes from the project: README, code, release notes, the canonical post.
- Distinctive: line 17
Do not write the problem or comparison in a voice the maker has not used.
- Distinctive: line 18
Never claim a competitor's price, license or status without a source.
- Distinctive: line 34
Read the README, release notes, license, the canonical post and existing launch notes.
- Distinctive: line 37
Verify the canonical URL and every public asset URL.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Activation Contract
Use before launching a tool, or when another launch skill finds docs/launch/<slug>/kit.md missing or incomplete.
Hard Rules
- Every fact comes from the project: README, code, release notes, the canonical post. Mark anything inferred (assumption) and ask about it.
- Do not write the problem or comparison in a voice the maker has not used. Quote or adapt their own text (README, post); if there is none, leave a draft and flag it for rewriting.
- Never claim a competitor's price, license or status without a source; put the source next to the claim.
- The canonical post URL must not redirect: check with
curl -sILand record the final URL. - Public asset URLs must load without a login: check each with
curl -sI.
Decision Gates
| Situation | Action |
| No kit yet | Copy assets/kit-template.md to docs/launch/<slug>/kit.md |
| Source images exist | Run scripts/make-assets.sh (ImageMagick 7) into docs/launch/<slug>/assets/ |
No magick | Ask the user to install it (brew install imagemagick); list the sizes needed meanwhile |
| Repo has no topics | Propose them; set with gh repo edit <repo> --add-topic a,b only after a yes |
| A required fact is unknown | Leave it under Gaps; do not guess |
Execution Steps
- Read the README, release notes, license, the canonical post and existing launch notes.
- Fill Identity and Copy; keep the tagline under 60 characters and the short description to one sentence ending with a period.
- Generate images:
scripts/make-assets.sh --out docs/launch/<slug>/assets --icon <1024px icon> --cover <cover> <screenshots in display order>. Put the screenshot that shows the tool in action first. - Verify the canonical URL and every public asset URL.
- List Gaps: missing assets, unverified claims, gates the maker must clear.
Output Contract
Return the kit path, the generated files with their sizes, the verified URLs, and the gaps.
References
../../references/launch-folder.md: where launch files live.../../references/channels.md: asset sizes per channel.scripts/make-assets.sh: image generation;--helpfor options.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

