skills/marketing/marketplace-submit/SKILL.md
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
npx skillsauth add cwinvestments/memstack memstack-marketing-marketplace-submitInstall 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.
Step-by-step guide to submit skills, plugins, or tools to community marketplaces via pull request.
| Trigger | Status | |---------|--------| | User says "submit to marketplace" or "publish my skill" | ACTIVE | | User says "share this skill" or "list on marketplace" | ACTIVE | | User says "submit plugin" or "publish to community" | ACTIVE | | User wants to build a skill | NOT this skill — use Forge | | User wants to write plugin code | NOT this skill — use standard development |
| Marketplace | URL | Format | Submission | |-------------|-----|--------|------------| | buildwithclaude | github.com/davepoon/buildwithclaude | Skills/plugins directory | Fork + PR | | awesome-mcp-servers | github.com/punkpeye/awesome-mcp-servers | Awesome list | Fork + PR | | Smithery | smithery.ai | MCP registry | Web submission | | Glama MCP | glama.ai/mcp/servers | MCP directory | Fork + PR | | awesome-claude-code | Community repos | Various | Fork + PR |
Verify the skill/plugin is ready:
| Check | How to verify | |-------|---------------| | SKILL.md exists and is complete | Read the file, confirm frontmatter + body | | Name and description are clear | Description explains what it does in one sentence | | Trigger words are specific | No vague triggers that overlap with other skills | | No proprietary/Pro content | Confirm this is a free skill or has permission | | Works locally | User has tested it in their own CC session |
# Verify the skill file exists and has frontmatter
head -10 skills/<category>/<name>/SKILL.md
# Fork via GitHub CLI
gh repo fork <owner>/<repo> --clone
# Or fork via web UI at github.com/<owner>/<repo>/fork
cd <forked-repo>
git checkout -b add-<skill-name>
Each marketplace has its own structure. Follow the existing patterns:
For buildwithclaude (skill directory):
# Create your skill folder
mkdir -p <skill-name>
# Copy your SKILL.md
cp /path/to/your/SKILL.md <skill-name>/SKILL.md
# Add a README if required
For awesome lists (link addition):
<!-- Add to the appropriate section in README.md -->
- [Skill Name](link) - One-line description of what it does
Follow this template:
## Add [Skill Name]
### What it does
[1-2 sentences explaining the skill's purpose]
### Trigger keywords
[List the activation triggers]
### Category
[e.g., Development, Automation, Marketing]
### Testing
- [ ] Tested locally in Claude Code
- [ ] Follows repository's contribution guidelines
- [ ] No duplicate of existing entries
### Author
[Your name/handle]
# Stage and commit
git add .
git commit -m "Add <skill-name> skill"
# Push to your fork
git push origin add-<skill-name>
# Create the PR
gh pr create --title "Add <skill-name>" --body "$(cat <<'PREOF'
## Add [Skill Name]
### What it does
[description]
### Trigger keywords
[triggers]
### Testing
- [x] Tested locally in Claude Code
- [x] Follows contribution guidelines
- [x] No duplicate of existing entries
PREOF
)"
# Check PR status
gh pr status
# View PR checks
gh pr checks
Marketplace Submission Checklist:
- Target: [marketplace name]
- Skill: [skill name]
- Branch: add-[skill-name]
- PR: [URL when created]
Status: [ready to submit / submitted / merged]
For maximum visibility, submit to multiple marketplaces in sequence:
Do NOT submit proprietary or Pro skills to public marketplaces.
tools
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
development
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
development
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.
development
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.