askit-init-marketplace
Creates and validates a marketplace index that catalogs plugins for Claude Code and Codex, checking each entry, its plugin reference, and version consistency. Use when standing up a marketplace, adding a plugin to a marketplace, or validating marketplace entries.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- askit-init-marketplace
- metadata
- { "tier": "universal", "version": "0.2.0", "audience": "advanced" }
- description
- Creates and validates a marketplace index that catalogs plugins for Claude Code and Codex, checking each entry, its plugin reference, and version consistency. Use when standing up a marketplace, adding a plugin to a marketplace, or validating marketplace entries.
02 资源文件 2
- 参考文档README.md541 B
- 参考文档references/marketplace-format.md3.8 KB
03 SKILL.md 正文
askit-init-marketplace
Purpose
Scaffold and validate a distribution index that catalogs plugins, in each target's native format. create scaffolds the marketplace index per target; validate checks that every entry resolves to a real plugin and that versions are consistent. The two native formats and the entry shape are in references/marketplace-format.md.
When to use
When standing up a marketplace, adding a plugin to one, or validating marketplace entries.
create mode
- Read the target agents and the plugin roster to catalog.
- Scaffold the index per target: Claude Code
.claude-plugin/marketplace.json; Codex.agents/plugins/marketplace.json(Standard sec 12). Each entry names the plugin, its source or path, and its version. - Pick the source kind that matches how the plugin is actually distributed: a bare path,
url/github(with ashato pin it),npm,archive(which requires asha256), orgit-subdir. The full table is in the reference. - If an entry has shipped under a previous name, record it in
renamesso consumers following the old name can be redirected. - Keep the catalog separate from any single plugin's manifest (a marketplace catalogs plugins; it is not itself a plugin).
validate mode
- Each entry resolves to a real plugin (its source/path exists and carries a
library.json). - Versions are consistent (an entry's version matches the plugin's
library.jsonversion; no dangling or duplicate entries). - No
renamesvalue collides with a live entry name or with another entry'srenames. - For a whole-catalogue grade, run
node scripts/evaluate.mjs <catalogue-root>(marketplace scope). It grades every locally-resolvable member at its own declared tier and its own Standard pin, and reports the cross-member defects no per-plugin run can see: colliding skill and command names, a catalogue entry that resolves to nothing, and a registry version disagreeing with the member's own manifest.
Scope
A marketplace catalogs plugins for distribution; it is a separate artifact from the plugins it lists (the marketplace-vs-plugin separation rule). The Standard registers a plugin at its first tagged release, not before (sec 12); the toolkit additionally reserves its own marketplace debut for its Gold v1.0.0 tag (Decision C, a product choice, not the normative rule). This skill scaffolds and validates the index at any tier; publishing an entry waits for that first tagged release. askit-init-plugin scaffolds a plugin; this skill scaffolds the marketplace that lists plugins.
04 同仓库更多 Skills
fx-demo
A fixture skill that exists so the re-derived manifest has a component list to compare. Use only from tests/unit/self-consistency.test.mjs.
fx-demo
A fixture skill that exists so the re-derived manifest has a component list to compare. Use only from tests/unit/self-consistency.test.mjs.
fx-demo
A fixture skill that exists so the re-derived manifest has a component list to compare. Use only from tests/unit/self-consistency.test.mjs.
sf-caller
Calls the worker subagent to do a thing. Use when delegating work to sf-worker.
sf-do-thing
Converts CSV input into a formatted summary. Use when the user asks to summarize or tabulate spreadsheet data.
root-skill-plugin
Summarizes a changelog section into one release-note sentence. Use when the user asks to condense a list of changelog bullets into a single announcement line.