plugins/skill-creation/skills/publishing/SKILL.md
Manages Codex, Claude Code, and Cursor skill marketplaces — publishes plugin-owned skills, updates plugin groups, removes entries, packages skills for distribution, regenerates plugin manifests, and validates catalog integrity. Use when publishing a skill to the marketplace, bumping a version, removing a skill from the catalog, packaging a skill as a .skill file, regenerating marketplace files, moving a skill between plugins, or fixing marketplace validation errors.
npx skillsauth add lucasilverentand/skills publishingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
metadata.version of marketplace.jsonplugins/<old>/skills/<skill> to plugins/<new>/skills/<skill>, update plugin-groups.json, then run bun run marketplace:writescripts/package-skill.ts <path/to/skill-folder>bun run marketplace, fix any errors per references/marketplace-errors.mdplugins/<plugin>/skills/<skill-name>/SKILL.mdbun run plugins/skill-creation/skills/publishing/scripts/quick-validate.ts plugins/<plugin>/skills/<skill-name>plugin-groups.jsonbun run marketplace:write to regenerate:
plugins/<name>/.claude-plugin/plugin.jsonplugins/<name>/.codex-plugin/plugin.jsonplugins/<name>/.cursor-plugin/plugin.jsonplugins/<name>/README.md.claude-plugin/marketplace.json.cursor-plugin/marketplace.json.agents/plugins/marketplace.jsonbun run marketplace again; it must report everything up to dateFor bulk additions, update plugin-groups.json first, then regenerate once.
plugin-groups.jsonplugins/<plugin>/skills/<skill-name>/bun run marketplace:write, then bun run marketplaceTo rebuild plugin manifests and marketplaces from the plugin-owned source tree:
plugins/<plugin>/skills/plugin-groups.jsonbun run marketplace:write.claude-plugin/, .cursor-plugin/, and .agents/plugins/bun run marketplace to confirm no generated files are staleSee references/marketplace-schema.md for the full schema. Key conventions:
plugins/<name>/skills/<skill-name>/ directories are authored directlybun run marketplace:writeplugin-groups.json metadata.version tracks both marketplace versions using semver.agents/plugins/marketplace.json.claude-plugin/marketplace.json.cursor-plugin/marketplace.json (team-template layout with metadata.pluginRoot)bun run validate:cursor after regenerating Cursor artifacts|File|What it covers|
|---|---|
|references/marketplace-schema.md|Codex, Claude, and Cursor marketplace schemas, plugin manifests, and source types|
|references/marketplace-errors.md|Validation error codes and fixes|
|plugin-groups.json|Source of truth for plugin grouping and metadata|
|scripts/marketplace.ts|Regenerates both marketplaces and plugin manifests|
|scripts/quick-validate.ts|Quick SKILL.md frontmatter validation|
|scripts/package-skill.ts|Packages a skill folder into a distributable .skill zip file|
tools
Creates, audits, and updates public open-source repository documentation, including README files, CONTRIBUTING guides, SECURITY and SUPPORT docs, project badges, quickstarts, usage guidance, community links, and contributor onboarding. Use when maintaining docs for public GitHub projects, libraries, CLIs, apps, or reusable packages, especially when the user says "update this README", "write CONTRIBUTING.md", "make these docs open-source ready", or "improve the public project docs".
development
Creates, audits, and updates private or closed-source project documentation, including internal README hubs, codebase navigation guides, ownership links, Linear initiative links, onboarding notes, runbooks, and contribution guidance for teams. Use when maintaining docs for private repositories, internal apps, services, infrastructure, or company projects, especially when the user says "make this README an internal hub", "document how to navigate this repo", "add Linear links to the docs", or "write private project documentation".
development
Creates, updates, estimates, and tidies Linear issues using Luca's issue-shaping rules. Use when the user asks to create a Linear issue, write ticket-ready issue text, refine an existing issue, add acceptance criteria, set issue relationships, estimate points, audit issue hygiene, tidy a Linear project, find duplicates, fix stale blockers, or normalize labels, milestones, priorities, and issue state.
testing
Keeps an existing Linear project tidy after planning and during execution. Use when the user asks to "tidy Linear", "clean up the project", "audit issues", "find duplicates", "check stale blockers", "fix project drift", or run periodic Linear housekeeping on a project, initiative, or milestone set. Use when planning is underway or execution has started and relationships, labels, priorities, documents, and issue states need coherence without changing product scope.