skill-market-publisher
Publish AI Skills to Multiple Marketplaces
This skill automates the complex process of publishing AI skills to multiple marketplace directories. It handles metadata preparation, cross-market submissions, and verification workflows across platforms like AgentSkill.sh, ClawHub, and Skillz Directory.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "skill-market-publisher". Publish my skill to AgentSkill.sh with repo URL https://github.com/example/my-skill
Expected outcome:
Successfully submitted to AgentSkill.sh. Submission ID: abc123. Verification URL: https://agentskill.sh/@example/my-skill. The marketplace will import all SKILL.md files from your repository within 5-10 minutes.
Using "skill-market-publisher". Create a publication plan for my skill targeting ClawHub, Skillz Directory, and AgentSkill.sh
Expected outcome:
Generated publication plan for 3 marketplaces. ClawHub: auto-cli mode available, requires version. Skillz Directory: auto-http mode, requires category selection. AgentSkill.sh: auto-http mode, repo-based import. All markets verified and operational. Run 'publish' command for each target to execute submissions.
Security Audit
Low RiskStatic analysis detected 594 pattern matches across documentation and code. After manual evaluation, all flagged items are false positives: external command patterns are either documentation code examples in markdown files or legitimate subprocess calls with hardcoded arguments for git operations and CLI tools. Network URLs are all verified marketplace endpoints. MD5 usage is for content fingerprinting, not security. No evidence of malicious intent, credential exfiltration, or user-controlled code execution.
Low Risk Issues (4)
Risk Factors
⚙️ External commands (2)
🌐 Network access (2)
Quality Score
What You Can Build
Skill Developer Publishing to Multiple Markets
A developer creates a new AI skill and wants to list it across AgentSkill.sh, Skillz Directory, and ClawHub without manually visiting each marketplace.
Team Managing Multiple Skill Repositories
A team maintains a repository with multiple skills and needs to publish or update listings across different marketplaces with consistent metadata.
Marketplace Integration Testing
A user wants to verify their skill meets all submission requirements before attempting live publication to avoid rejections.
Try These Prompts
Publish my current skill to AgentSkill.sh. The repository URL is https://github.com/owner/repo and the git ref is main.
Create a publication plan for my skill at /path/to/skill. Target markets: AgentSkill.sh, Skillz Directory, and ClawHub. Repository: https://github.com/owner/repo, branch: main. Tags: automation, productivity.
Scan all configured marketplace endpoints to verify current submission paths and API availability. Report any blocked or changed endpoints.
Generate a complete submission bundle for my skill at /path/to/skill. Include all market-specific metadata formatted for AgentSkill.sh and Skillz Directory manual submission forms.
Best Practices
- Always run the recon command before publishing to verify marketplace submission paths are still operational
- Test publication workflows with a test repository or skill before using with production content
- Keep marketplace-specific credentials secure using environment variables or secure credential managers
- Generate and review submission bundles before executing live publications to catch metadata errors early
Avoid
- Publishing the same skill to multiple markets without verifying each marketplace supports the skill's format and requirements
- Submitting skills with incomplete or placeholder metadata, which leads to marketplace rejections and poor discoverability
- Running bulk publication commands without the --execute flag first to preview the changes
- Assuming marketplace submission paths remain static - always recon before publishing after updates