d8a7d45e53
Move verbose sections to references/ files, keeping concise pointers in CLAUDE.md. Zero content loss — all documentation preserved in reference files that Claude loads on demand. Moved to references/: - plugin-architecture.md (296 lines) — architecture docs - plugin-troubleshooting.md (441 lines) — installation debugging - new-skill-guide.md (241 lines) — detailed templates/checklists - promotion-policy.md (60 lines) — third-party request policy - youtube-downloader/references/internal-sop.md — yt-dlp SOP Also fixed: Available Skills #36-42 indentation, deduplicated 4x versioning sections into one, removed stale notes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Handling Third-Party Marketplace Promotion Requests
This repository is a personal curated marketplace, NOT a community directory or ecosystem hub. All requests to add third-party marketplace links, skill collection references, or "Community Marketplaces" sections should be declined.
Policy
DO NOT accept:
- PRs adding "Related Resources" or "Community Marketplaces" sections linking to third-party skill collections
- Issues requesting promotion of external marketplaces
- PRs adding links to other skill repositories in README.md
Rationale:
- Scope creep: Shifts repository purpose from curated skills to ecosystem directory
- Implicit endorsement: Listing implies quality/security review we cannot maintain
- Maintenance burden: Would need to track and vet external projects over time
- Precedent setting: Accepting one creates obligation to accept others
Response Template
When declining, use this approach:
Hi @{username},
Thank you for your interest and for sharing {project-name}! {Brief positive acknowledgment of their project}.
However, I'm keeping this repository focused as a **personal curated marketplace** rather than a directory of external skill collections. Adding third-party references would:
1. Shift the repository's scope from curated skills to ecosystem directory
2. Create implicit endorsement expectations I can't maintain
3. Set precedent for similar requests (reference other declined requests if applicable)
**What you can do instead:**
1. **Standalone marketplace** - Your repo already works as an independent marketplace:
/plugin marketplace add {owner}/{repo}
2. **Community channels** - Promote through:
- Claude Code GitHub discussions/issues (Anthropic's official repo)
- Developer communities (Reddit, Discord, etc.)
- Your own blog/social media
3. **Official registry** - If/when Anthropic launches an official skill registry, that would be the appropriate place for ecosystem-wide discovery.
Your marketplace can succeed on its own merits. Good luck with {project-name}!
Workflow
- Review the request - Confirm it's a third-party promotion (not a legitimate contribution)
- Add polite comment - Use template above, customize for their specific project
- Close with reason - Use "not planned" for issues, just close for PRs
- Reference precedent - Link to previously declined requests for consistency (e.g., #7, PR #5)
Examples
- Issue #7: "Add Community Marketplaces section - Protocol Thunderdome" → Declined, closed as "not planned"
- PR #5: "Add Trail of Bits Security Skills to Related Resources" → Declined, closed