skills/claude-ecosystem-promoter/SKILL.md
Marketing and promotion specialist for Claude ecosystem technology - MCP servers, skills, plugins, and agents. Expert in community engagement, registry submissions, content marketing, and developer relations. Activate on 'promote MCP', 'share skill', 'market plugin', 'launch agent', 'developer marketing', 'MCP registry'. NOT for creating MCPs/skills (use agent-creator), general marketing (use content-marketer), or SEO optimization (use seo-visibility-expert).
npx skillsauth add curiositech/windags-skills claude-ecosystem-promoterInstall 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.
Marketing specialist for Claude ecosystem technology. Transform your MCP servers, skills, plugins, and agents from hidden gems into widely-adopted tools.
Given: (Budget: low/med/high, Target: devs/business/general, Urgency: days/weeks/months)
IF Budget=low AND Target=devs:
→ Official MCP Registry + r/ClaudeAI + GitHub awesome lists
IF Budget=low AND Target=business:
→ LinkedIn + dev.to professional posts + Discord communities
IF Budget=med AND Target=devs:
→ Add: Smithery.ai + YouTube demos + Twitter threads
IF Budget=med AND Target=business:
→ Add: Medium articles + newsletter outreach + HackerNews
IF Budget=high:
→ Full multi-channel: All above + influencer outreach + paid communities
IF Urgency=days:
→ Reddit + Twitter + Discord (immediate reach)
IF Urgency=weeks:
→ Add: Registry submissions + dev.to articles
IF Urgency=months:
→ Add: SEO content + awesome list building + newsletter campaigns
IF Tool complexity = simple:
→ GIF demo + 2-minute video + Twitter thread
IF Tool complexity = moderate:
→ 5-minute tutorial + dev.to walkthrough + Reddit showcase
IF Tool complexity = advanced:
→ YouTube deep-dive + documentation site + multi-part series
IF Audience = technical:
→ Code samples + GitHub integration + technical blogs
IF Audience = business:
→ ROI examples + case studies + professional platforms
IF Tool type = MCP server:
→ Installation demo + Claude config examples + registry submissions
IF Tool type = skill:
→ Usage examples + workflow integration + skills directory
Symptoms: Tool gets 5-10 stars, no community engagement, forgotten in weeks Diagnosis: Posted once to one channel, never followed up Fix:
Symptoms: Downvoted posts, community backlash, banned from subreddits Diagnosis: Same promotional content posted to 10+ places simultaneously Fix:
Symptoms: GitHub issues asking "how to install?", high bounce rate from repos Diagnosis: README lacks clear installation, no demo video, poor examples Fix:
Symptoms: Tool not discoverable in MCP clients, low adoption despite quality Diagnosis: Never submitted to official registries, only posted on social media Fix:
Symptoms: Reddit post gets 3 upvotes, tweet gets 2 likes, no traction Diagnosis: Posted Friday evening or during major tech events Fix:
Scenario: Developer built MCP server connecting Claude to Notion API
Day -7 Pre-Launch:
Launch Day Decision Points:
Execution:
Results Week 1: 127 GitHub stars, 45 Reddit upvotes, 2.3K tweet views, featured in PulseMCP newsletter
Expert vs Novice:
Scenario: Business user created Claude skill for automated email responses
Decision Process:
Content Strategy:
Results: 45 LinkedIn shares, Medium article featured in AI newsletter, 2 enterprise inquiries
Launch Readiness Checklist:
Do NOT use this skill for:
agent-creator insteadcontent-marketer insteadseo-visibility-expert insteadtechnical-writer insteadDelegate when:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.