2104178150-ai/megaphone / skills/launch-posts
launch-posts
VerifiedPick the channels where a project's audience actually is — developer communities for developer tools, the platforms end users already browse for apps, plugin directories for extensions — and prepare a rule-checked draft for each, or, where the platform wants the author's own words (Show HN, a DEV launch article, Lobsters, V2EX, 掘金 articles and 沸点, awesome lists that refuse LLM-written entries), a fact sheet the author writes from: Show HN, Reddit, Product Hunt, X/Twitter, DEV, Lobsters, awesome lists, newsletters, V2EX, HelloGitHub, 阮一峰科技爱好者周刊, 即刻, 小红书, 掘金, 知乎, B 站 and more. Use when the user wants to announce or promote a project or app, write a Show HN / Reddit / Product Hunt post, or says 写推广文案 / 发帖推广 / 发 V2EX / 投稿 HelloGitHub / 小红书怎么发.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.3 KB |
| channels/README.md | markdown | 7.1 KB |
| channels/awesome-lists.md | markdown | 4.4 KB |
| channels/china-other.md | markdown | 10.2 KB |
| channels/dev-blogs.md | markdown | 3.6 KB |
| channels/ecosystems.md | markdown | 14.8 KB |
| channels/github-native.md | markdown | 4.8 KB |
| channels/hacker-news.md | markdown | 7.4 KB |
| channels/hellogithub.md | markdown | 4.4 KB |
| channels/jike.md | markdown | 3.0 KB |
| channels/juejin.md | markdown | 6.0 KB |
| channels/lobsters.md | markdown | 3.1 KB |
| channels/newsletters.md | markdown | 5.1 KB |
| channels/product-hunt.md | markdown | 4.5 KB |
| channels/reddit.md | markdown | 6.1 KB |
| channels/ruanyf-weekly.md | markdown | 3.0 KB |
| channels/v2ex.md | markdown | 8.4 KB |
| channels/x-twitter.md | markdown | 4.1 KB |
| channels/xiaohongshu.md | markdown | 7.8 KB |
channels/ecosystems.md
View on GitHub# Host ecosystems: stores, plugin directories, package registries
> Last checked: 2026-10-25 against each host's own docs, linked in the table below. Store
> rules and review processes change; when this file and the host's docs disagree, the
> host wins. Anything not confirmed on the host's own page is marked *(unverified)* or
> *(heuristic)*.
## Fit
If the project lives inside another app — an editor extension, a browser extension, a
note-app plugin, a launcher command, a plugin for an app like 思源笔记 or MusicFree — or is
installed through a package manager, the host's own directory is often the best channel
you have. People browse it when they already use the host and have the problem, there's an
install button next to your description, and a listing keeps working for years, like an
awesome-list entry. For libraries, the registry's search (npm, PyPI) plays the same role.
A listing is not a launch, though: new listings rarely get much exposure on their own
*(heuristic)*. List first, then announce — in the host's showcase space and in the general
channels where its users are.
## Rules
### Etiquette that applies to every host
- **Read the host's developer policy or store guidelines before you submit.** Obsidian,
Raycast, JetBrains, Chrome and Firefox each link theirs from the pages in the table.
- **Ask before posting in the host's community.** Before announcing in the host's forum,
Discord, Slack, subreddit or WeChat group, look for a showcase channel or thread. If there
isn't one, ask a maintainer or moderator first (template below). It's their space, not
your launch venue. In the channel table, such a space is `ask first`, not a post draft.
- **Never use the host's issue tracker to announce.** Issues are for bugs in the host.
Obsidian's releases repo, for example, says it doesn't accept issues and sends plugin
questions to each plugin's own repo.
- **Follow the host's wishes about how it's described.** MusicFree's README asks people not
to promote it as a "VIP / 破解版", to describe it truthfully, to blur plugin sources in
articles, and says the author only announces it in the Git repo and their WeChat account.
If the host says something like this, your posts follow it.
- **Don't imply endorsement.** Say "for <host>" or "<host> plugin", add "unofficial / not
affiliated" if a reader could think otherwise, and don't use the host's logo as your icon.
This is our advice; check the host's trademark or branding rules where it has them.
- **One listing, honest keywords.** No duplicate listings and no keyword stuffing.
### Where and how to list
| Host | How to get listed | Notes from the host's docs |
|---|---|---|
| **VS Code Marketplace** | Register a publisher, then `vsce publish` ([docs](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)) | At most 30 `keywords` in `package.json`. README and CHANGELOG images must be https; SVGs only from trusted badge providers. Global Azure DevOps personal access tokens are retired on 2026-12-01; the docs say to publish with Microsoft Entra ID instead. |
| **Open VSX** | Eclipse account + Publisher Agreement, create a namespace, then `npx ovsx publish` ([wiki](https://github.com/eclipse-openvsx/openvsx/wiki/Publishing-Extensions)) | VS Code forks such as VSCodium can't use Microsoft's Marketplace and install from Open VSX ([VSCodium docs](https://github.com/VSCodium/vscodium/blob/master/docs/extensions.md)). Publish to both. |
| **JetBrains Marketplace** | Log in, then account menu → **Upload plugin**; first time, accept the Developer Agreement and create a Vendor profile ([docs](https://plugins.jetbrains.com/docs/marketplace/uploading-a-new-plugin.html)) | Must meet the approval criteria. Tags are search filters, so pick the right ones. An open-source licence needs a link to the source. Use a custom release channel for alpha/beta builds. |
| **Chrome Web Store** | Register as a developer (one-time registration fee), then submit from the developer dashboard; new items go through review ([register](https://developer.chrome.com/docs/webstore/register), [publish](https://developer.chrome.com/docs/webstore/publish)) | Fill in the privacy fields. The developer email can't be changed later, so pick it with care. |
| **Firefox Add-ons (AMO)** | Developer Hub → Submit a New Add-on → **On this site** to be listed ([docs](https://extensionworkshop.com/documentation/publish/submitting-an-add-on/)) | An automatic validator runs on upload. Up to 2 categories. A privacy policy is required if any data leaves the user's device. Flagging the add-on "experimental" lists it with reduced visibility. |
| **Obsidian community plugins** | Sign in at [community.obsidian.md](https://community.obsidian.md), link GitHub, add the plugin; review is automated ([docs](https://docs.obsidian.md/Plugins/Releasing/Submit+your+plugin)) | Repo root needs `README.md`, `LICENSE`, `manifest.json`; a GitHub release whose tag equals the manifest `version`, with `main.js`, `manifest.json` (and `styles.css`) attached. The `id` must be unique and can't contain `obsidian`. Older guides describe a PR to `obsidianmd/obsidian-releases`; the current docs send you to the directory. After listing, the docs suggest announcing in the forum's Share & showcase and Discord `#updates` (needs the developer role). |
| **Raycast Store** | `npm run publish` opens a PR in `raycast/extensions`; the Raycast team reviews and merging publishes it ([publish](https://developers.raycast.com/basics/publish-an-extension), [prepare](https://developers.raycast.com/basics/prepare-an-extension-for-store)) | Store prep: `license` must be MIT, `author` your Raycast username, at least one category, up to six screenshots (three or more recommended). |
| **Homebrew** | Your own tap: `brew tap-new <user>/homebrew-tap`, then users run `brew install <user>/tap/<name>` ([taps](https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap)). `homebrew/core`: a pull request that meets the acceptance policy; search earlier PRs for your project first ([adding software](https://docs.brew.sh/Adding-Software-to-Homebrew), [policy](https://docs.brew.sh/Package-Acceptance-Policy), [formulae](https://docs.brew.sh/Acceptable-Formulae)) | Core needs public interest beyond the author: normally 30 forks, 30 watchers or 75 stars, and **90 / 90 / 225 if the repo owner submits it**; repos under 30 days old are normally not eligible; a stable tagged release; a DFSG-compatible licence; builds from source. Homebrew says its official repos "are not editorial curation or recommendation services": core is an install path, not a discovery channel. Start with a tap. |
| **npm** | `npm publish` | `description` and `keywords` in `package.json` are what `npm search` lists ([docs](https://docs.npmjs.com/cli/configuring-npm/package-json)). |
| **PyPI** | Upload a built package | `keywords` help PyPI's search suggest your project; `classifiers` describe maturity and audience; `readme` becomes the project page; `[project.urls]` show in the sidebar ([guide](https://packaging.python.org/en/latest/guides/writing-pyproject-toml/)). |
| **思源笔记集市** (SiYuan bazaar) | Fork [siyuan-note/bazaar](https://github.com/siyuan-note/bazaar), add `owner/repo` to `plugins.txt` (or `themes.txt`, `icons.txt`, `templates.txt`, `widgets.txt`), open a PR to `main` | One new package per PR. A PR Check workflow and the maintainers review it; the repo needs a Latest Release with `package.zip`. Later versions are picked up from your releases, with no new PR. |
| **MusicFree plugins** | No central store: users install a plugin from a file or a URL (`.js` or `.json`) under 设置 → 插件设置 ([README](https://github.com/maotoumao/MusicFree)) | Your README and install URL are the listing. Respect the host's wording rules above. |
### Agent skills and Claude Code plugins
For a skill pack, a Claude Code plugin or anything with a `SKILL.md`. Checked 2026-10-21.
| Where | How to get listed | Notes from the source |
|---|---|---|
| **Anthropic's plugin directory** (claude.ai, also browsable on [Claude Marketplace](https://claude.com/marketplace/plugins)) | Submit a plugin bundle from a GitHub repo at [claude.ai/directory/manage](https://claude.ai/directory/manage): **Submit new → Plugin bundle → Validate**, answer the data-handling questions, accept the terms, submit ([publish](https://claude.com/docs/directory/publish), [submit](https://claude.com/docs/plugins/submit)) | Needs a Pro, Max, Team or Enterprise plan; free accounts can't submit. Skills aren't a submission type on their own: put them in a bundle. Every version gets validation and a security scan, and a person reviews a new listing; review time isn't fixed. The [pre-submission checklist](https://claude.com/docs/plugins/pre-submission-checklist) blocks on a README under 40 words or no licence; holds for a reviewer non-image files over 256 KiB, more than 512 files, binaries such as `.zip` or `.pdf`, names that look like a known brand, and reading a credential like `$GITHUB_TOKEN` from the user's environment and sending it to a server. On Team and Enterprise, an Owner submits; on Enterprise, an Owner can also give other members the Directory permission through a custom role. Remove `.DS_Store` files. The listing shows your README, and its Usage tab shows installs. |
| **Your own Claude Code marketplace** | A `.claude-plugin/marketplace.json` in your repo; users run `/plugin marketplace add <owner>/<repo>`, then `/plugin install <plugin>@<marketplace>` ([docs](https://code.claude.com/docs/en/plugins/anthropic-marketplaces)); in a terminal, `claude plugin install <plugin> --marketplace <owner>/<repo>` does both in one line (`claude plugin install --help`, checked 2026-11-06) | Anthropic doesn't review third-party marketplaces. It's an install path, not discovery: people find it through your README and posts *(heuristic)*. |
| **skills.sh** | No submission step that we found: its leaderboard "ranks skills based on anonymous telemetry data collected from the `skills` CLI" ([docs](https://www.skills.sh/docs)), i.e. installs through `npx skills add <owner>/<repo>` | Put that one-line install in your README's quick start so every install counts. skills.sh offers a README badge. |
| **SkillsMP** | No submission step described: "Skills are sourced from public GitHub repositories" ([about](https://skillsmp.com/about)) | Questions about inclusion go to the support address on that page. |
| **awesome-claude-code** (hesreallyhim) | Web issue form only, filled in by a human; PRs and CLI submissions aren't accepted ([CONTRIBUTING](https://github.com/hesreallyhim/awesome-claude-code/blob/main/CONTRIBUTING.md)) | At least 14 days since the first commit plus later commits, or 100+ stars. One resource at a time. The resource may be agent-written; the recommendation must be written by a person. Reviewed "in a best-effort way" with no promise of a reply; the maintainer advises getting users first, and says that if getting listed is part of your promotion plan you should have a backup plan. |
| **awesome-agent-skills** (heilcheng) | One line at the end of a Community Skills category, by pull request ([README](https://github.com/heilcheng/awesome-agent-skills), [AGENTS.md](https://github.com/heilcheng/awesome-agent-skills/blob/main/AGENTS.md)) | Merged once the repo has at least 20 stars and is older than 14 days; public repos with a `SKILL.md` only. An agent opening the PR must say so, and say whether the submitter is the skill's author. |
Order that works for a new skill pack *(heuristic)*: your own marketplace and the `npx skills add`
line on day one, Anthropic's directory once the README and licence pass the checklist, the
awesome lists once their age and star rules allow and people are using it.
For any other host, search its docs for "submit", "publish", "marketplace" or "community
plugins", look for an `awesome-<host>` list, and check which GitHub topic its plugins use
(e.g. `<host>-plugin`).
## Format
- **The listing is the post.** Name, a one-line description in the host's vocabulary (what
it does *inside the host*), an icon, screenshots or a GIF of it working in the host's own
UI, and a README that starts with install and usage.
- **Keywords and tags**: the words users type into the store's search box. Specific beats
generic.
- **Say what it touches.** Required host version, permissions, and what data leaves the
device. Browser stores ask for this in their privacy fields and policies; users read it
before installing.
- **Store link first.** In every announcement, link the listing (one-click install), with
the repo as the source link.
- **Showcase post** in the host's community: what it does, a GIF, the store link, that
you're the author, what it doesn't do yet, and the feedback you want.
## Timing
- **Submit before launch week.** Review ranges from automated (Obsidian) to a PR review
(Raycast, SiYuan, Homebrew) to store review (Chrome, Firefox, JetBrains); none of the docs
we read promise a turnaround.
- **Announce only after the listing is live**, so every post can link to the install
button.
- **Host moments** *(heuristic)*: a host release that your plugin supports or relies on is a
natural time for an update post in the host's showcase space.
## Template
Asking the host's maintainer before posting in their community:
```
Hi <name>, I made <plugin>, an unofficial <host> plugin that <does X>. It's <licence>;
source: <repo>. Before I mention it in <forum / Discord / subreddit>, is there a right
place for this (a showcase channel or thread), or would you rather I didn't post it?
Thanks for building <host>.
```
The same request in Chinese, for Chinese hosts:
```
你好,我做了一个 <宿主> 的非官方插件 <名字>,可以 <做什么>,<协议> 开源:<仓库>。
想在 <交流群 / 论坛> 里介绍一下,请问有专门发插件的地方吗?如果不方便发,我就不发了。谢谢!
```
Store description:
```
<Name> — <what it does inside the host, in the host's words>.
- <benefit> (<how>)
- <benefit> (<how>)
Works with <host> <version>+. <Permissions / data it touches, or "No data leaves your device.">
Not affiliated with <host>. Source and issues: <repo>
```
## Pitfalls
- Announcing in the host's issue tracker → closed, and the host's maintainers remember.
- Posting in the host's community before asking, or in every channel at once → reads as spam
in someone else's house.
- Implying endorsement (the host's logo as your icon, "official") → risks rejection and
trademark complaints.
- Submitting before it's ready → early reviews and ratings stick to the listing *(heuristic)*.
- Different listings for the same thing (marketplace + Open VSX + a fork's store) with
different descriptions → keep one source of truth (the README) and copy from it.
- A plugin in a grey area (unofficial APIs, media sources) → the host may object or remove
it; check the brief's "Claims we won't make" before you post in the host's spaces.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |