# 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.

- Skill: `product-on-purpose/askit-init-marketplace` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add product-on-purpose/askit-init-marketplace`
- Raw SKILL.md: https://api.skillmd.com/api/skills/product-on-purpose/askit-init-marketplace/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: product-on-purpose (https://skillmd.com/u/product-on-purpose)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/product-on-purpose/askit-init-marketplace

---


# 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](references/marketplace-format.md).

## When to use
When standing up a marketplace, adding a plugin to one, or validating marketplace entries.

## create mode
1. Read the target agents and the plugin roster to catalog.
2. 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.
3. Pick the source kind that matches how the plugin is actually distributed: a bare path, `url`/`github` (with a `sha` to pin it), `npm`, `archive` (which requires a `sha256`), or `git-subdir`. The full table is in the reference.
4. If an entry has shipped under a previous name, record it in `renames` so consumers following the old name can be redirected.
5. Keep the catalog separate from any single plugin's manifest (a marketplace catalogs plugins; it is not itself a plugin).

## validate mode
1. Each entry resolves to a real plugin (its source/path exists and carries a `library.json`).
2. Versions are consistent (an entry's version matches the plugin's `library.json` version; no dangling or duplicate entries).
3. No `renames` value collides with a live entry name or with another entry's `renames`.
4. 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.