mcpField
P
publish-to-all-skill-stores

publish-to-all-skill-stores

Local
github.com/xixi048Developer Tools0Updated today

About publish-to-all-skill-stores

An agent skill for publishing existing `SKILL.md` projects to agent-skill marketplaces. It documents different submission routes and provides workflows for checking readiness and building packages.

Key features

  1. 01Catalog skill stores and submission routes
  2. 02Explain submission steps by channel
  3. 03Check skill submission readiness
  4. 04Build store-specific package shapes
  5. 05Document verification and common pitfalls

Use cases

  1. 01Submit an existing skill to multiple stores
  2. 02Check skill files and layout before submission
  3. 03Build packages for different marketplaces

MCP support

Exposes a store registry, readiness check, and skill package builder over stdio for MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbpublish-to-all-skill-stores-2.0.1.mcpb2.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

publish-to-all-skill-stores

License: MIT

同时上架所有 Skill 商店 · an agent skill for pushing an existing SKILL.md skill to agent-skill marketplaces — at home and abroad, free and paid — without wasting a week rediscovering how each one actually accepts a submission.

中文说明见下。

What it is

A playbook, not a wrapper. It tells an agent how each class of store actually works, so no time is wasted on the ones that will never accept a file drop:

FormSubmission actionExamples
Auto-indexed from GitHubfix the repo (path + topics + README)skills.sh, SkillsMP, claude-plugins.dev
Public submit APIone HTTP POSTskillstore.io, skillsmd.dev, skillbay.sh
GitHub PRfork → add file → PRbuildwithclaude, awesome lists
Login-gated CLI / OAuth formlog in firstClawHub, Tank, Cow Skill Hub, agentskill.sh
Platform-hostedport the skill — a different projectCoze, AgentMore, GPT Store

What's new in v2

  • channel registry 24 → 36 (adds LobeHub, agentskills.in, XFYUN Astron, the MCP-side directories, official repos, the CN second tier, and the /.well-known/agent-skills/index.json discovery endpoint)
  • a named rule for whether a store is real: no receipt id and no PR means it did not happen
  • paid research: payment depends on form, not on channel — Tencent SkillPay is 0-cut but only accepts backend-backed "Pay Skill"

Install

npx skills add xixi048/publish-to-all-skill-stores
/plugin marketplace add xixi048/publish-to-all-skill-stores

What's inside

skills/publish-to-all-skill-stores/
├── SKILL.md                       the decision-first workflow
├── references/
│   ├── store-registry.md          24 channels: region, pricing, form, verification level
│   ├── submission-recipes.md      6 recipes + SPA recon + mirror/token push
│   ├── paid-channels.md           revenue splits, skillbay field table, price tiers
│   └── pitfalls.md                20+ "symptom → cause → fix" entries
└── scripts/
    ├── preflight.py               readiness check (layout, license, danger calls, network)
    ├── build_package.py           build the shapes each store wants
    └── submit_all.py              batch submitter (--registry for the full table)

Quick start

# 1. readiness check — ERROR means don't submit yet
python skills/publish-to-all-skill-stores/scripts/preflight.py <repo>/skills/<name>

# 2. build the package shapes
python skills/publish-to-all-skill-stores/scripts/build_package.py <repo> skills/<name> --out dist

# 3. see every channel and its submission form
python skills/publish-to-all-skill-stores/scripts/submit_all.py --registry

# 4. batch submit the ones that need no login
python skills/publish-to-all-skill-stores/scripts/submit_all.py --all --repo <github-url>

The one rule that pays for itself

Directory sites only index skills/<name>/SKILL.md. A skill sitting at the repo root is never discovered and never errors — it simply stays invisible. Move it, fix the relative paths, re-submit.

Use as an MCP server

The same three tools are exposed over MCP (stdio, zero dependencies), so any MCP-capable agent can call them directly:

{
  "mcpServers": {
    "publish-to-all-skill-stores": {
      "command": "python",
      "args": ["C:/path/to/publish-to-all-skill-stores/mcp/server.py"]
    }
  }
}

Tools: skill_store_registry (36 channels), skill_preflight (readiness check), skill_build_package (zip shape stores ask for).

Machine-discoverable index

docs/.well-known/agent-skills/index.json is published on GitHub Pages so agents that honour the /.well-known/agent-skills/index.json convention can find these skills without any store:

https://xixi048.github.io/publish-to-all-skill-stores/.well-known/agent-skills/index.json

Requirements

Python 3.8+, standard library only. No network calls from the scripts except the public endpoints you ask for.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.