Agent skill · marketing growth · aiskillstore
skill-market-publisher
Publish, submit, and verify local skills across public skill marketplaces, directories, and registries. Use when an agent needs to take a skill folder or skill repository, confirm current submission paths, prepare cross-market metadata, run verified live adapters, or generate manual submission bundles for markets such as AgentSkill.sh, Skillstore, SkillNet, agent-skills.md, SkillsMD, SkillHub, SkillHQ, and related registries.
Why this skill is useful
Adds executable scripts for publishing skills to multiple marketplaces, which the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Skill Market Publisher Overview Use this skill to turn one local skill folder into a reusable market release plan. Keep the skill itself timeless: document current submission surfaces, verification patterns, and adapter logic, but keep one-off submission IDs, sample URLs, and dated field logs outside the reusable skill folder. Quick Start 1. Re-check live market surfaces before making claims about support: 2. Inspect one skill and build a market readiness plan: 3. Generate a review bundle before any live submission: 4. Publish one wrapped live target at a time. Live submission requires --execute. 5. Verify the result using the market-specific checks in references/verification-playbook.md. 6. When a market still needs browser-side login or form interaction, open the tracked submit pages and use the printed checklist: Workflow 1. Normalize the Release Unit Treat the publishable unit as one skill folder containing SKILL.md. If the repository contains many skills, publish each skill separately. If the repository is a pack, split markets into: pack importers that should ingest the public repo once per-skill submitters that should receive a folder URL or raw SKILL.md content If a market works at repository scope, make sure the chosen public repository layout matches that market before submitting. 2. Detect Repository Layout Run inspect or plan first. The bundled CLI classifies the current repository as: single-skill-repo root-pack skills-subdir-pack nested-skill-dir standalone-skill-dir Some markets accept any repository URL. Others currently prefer a repository with a top-level skills/ directory. When layout and market expectations conflict, create a mirror or release repository instead of reshaping the source repository for one listing. Treat submit-page copy as a hint, not proof. Some live backends accept root-pack repositories even when the visible page copy talks about a repo-root skills/ directory. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/skill-market-publisher