--- license: Apache-2.0 name: someclaudeskills-strategy description: Strategy for someclaudeskills.com — the skills showcase and marketplace for Claude skills. Content publishing, traffic generation, community building, monetization through free-skills-as-lead-gen for WinDAGs, and the OS/2 Warp retro design subdomain. Activate on 'someclaudeskills strategy', 'skill marketplace', 'someclaudeskills.com', 'skills website', 'OS/2 subdomain', 'skills community', 'skills distribution', 'skill lead generation'. NOT for creating individual skills (use agent-creator), SEO implementation (use seo-visibility-expert), or Claude ecosystem marketing (use claude-ecosystem-promoter). allowed-tools: Read,Write,Edit,Glob,Grep,WebSearch,WebFetch metadata: category: Product & Strategy tags: - marketplace - community - someclaudeskills - lead-generation - content-strategy - retro-computing - strategy - some-claude-skills - positioning - marketing pairs-with: - skill: windags-customer-persona reason: someclaudeskills.com is the top-of-funnel for WinDAGs adoption - skill: claude-ecosystem-promoter reason: Distribution tactics for skills through ecosystem channels - skill: seo-visibility-expert reason: SEO is the primary traffic driver for a content site --- # someclaudeskills.com Strategy Strategic decision-making for the Claude skills showcase site that converts skill discovery into WinDAGs adoption through SEO traffic and community building. ## Decision Points ### Content Publishing Priority Matrix ``` High SEO Volume + High Skill Readiness = PUBLISH NOW ├─ Skills with 1K+ monthly searches → Individual skill pages first ├─ Skills solving common dev problems → Blog posts with examples └─ Skills with viral potential → OS/2 subdomain featured skills Medium SEO Volume + High Skill Readiness = PUBLISH NEXT ├─ Category consolidation pages → Group 3-5 related skills ├─ Workflow combination posts → "Build X with these 3 skills" └─ Comparison content → "Skill Y vs manual approach" High SEO Volume + Low Skill Readiness = HOLD/IMPROVE ├─ Popular searches but weak skills → Document in backlog ├─ Trending topics with half-built skills → Finish skills first └─ Competitive keywords needing better skills → R&D priority Low SEO Volume + Any Readiness = COMMUNITY/NICHE ├─ Specialized use cases → Community submission targets ├─ Author showcase opportunities → Profile-driven content └─ OS/2 subdomain content → Pure engagement plays ``` ### Traffic Source vs Conversion Optimization ``` Organic Search Traffic ├─ High search intent → Direct skill pages with WinDAGs install CTAs ├─ Research intent → Blog posts leading to skill collections └─ Brand searches → Homepage with featured skills showcase Social/Viral Traffic (OS/2, HN, Reddit) ├─ Curiosity-driven → OS/2 subdomain with subtle main site CTAs ├─ Technical audience → Code examples and implementation details └─ Nostalgia-driven → Design deep-dives linking to skill functionality Referral Traffic (dev blogs, newsletters) ├─ Developer audience → Technical content with immediate usefulness ├─ Product managers → ROI-focused skill combinations └─ Content creators → Template and framework skills Direct Traffic (returning users) ├─ Skill catalog browsing → Category pages with internal linking ├─ Specific skill lookup → Search function prominence └─ Community engagement → Author profiles and submission flows ``` ### Monetization Phase Triggers ``` IF monthly organic traffic < 500 AND community submissions < 10 ├─ THEN: Focus only on free skills as lead gen ├─ THEN: No marketplace features, no premium tiers └─ THEN: All effort on SEO content and WinDAGs conversion IF monthly organic traffic > 2000 AND WinDAGs conversion rate > 5% ├─ THEN: Introduce skill curation badges (free vs curated) ├─ THEN: Test premium skill submissions via Google Form └─ THEN: Build community author profiles IF community submissions > 50 AND premium demand signals exist ├─ THEN: Launch limited premium skill pilot (manual processing) ├─ THEN: Implement basic ratings/reviews system └─ THEN: Consider marketplace infrastructure investment NEVER: Build payment processing before 100+ community skills exist ``` ## Failure Modes ### Schema Bloat **Symptoms:** Adding fields to skill pages that don't drive traffic or conversions **Detection Rule:** If schema change doesn't directly impact SEO ranking or WinDAGs install CTAs **Fix:** Remove unnecessary metadata; focus on search-relevant structured data only **Example:** Adding "difficulty level" or "estimated time" fields that users don't search for ### Premature Marketplace Syndrome **Symptoms:** Building seller accounts, payment processing, review systems before demand exists **Detection Rule:** If feature takes >1 week to build but serves <50 users/month **Fix:** Replace with manual processes; build marketplace features only after 200+ community submissions **Example:** Payment system for 5 premium skills vs Google Form + manual PayPal ### OS/2 Distraction Trap **Symptoms:** OS/2 subdomain getting more development time than main site optimization **Detection Rule:** If OS/2 feature work > 20% of weekly development time **Fix:** Time-box OS/2 work; treat as marketing asset, not product feature **Example:** Building OS/2 skill editor vs optimizing main site conversion funnel ### SEO Content Mills **Symptoms:** Publishing blog posts without traffic research or conversion paths **Detection Rule:** If blog post doesn't target keyword with >100 monthly searches or clear WinDAGs connection **Fix:** Kill low-value content; focus on high-search-volume skill topics with conversion CTAs **Example:** "History of AI" posts vs "Claude skill for API testing" tutorials ### Community Spam Overflow **Symptoms:** Community submissions flooding site with low-quality skills **Detection Rule:** If community submission rate > manual review capacity or quality drops **Fix:** Implement submission guidelines; require skill testing before listing **Example:** 50 "hello world" skills vs 5 tested, documented, useful skills ## Worked Examples ### Example: Launching the "security-auditor" Skill Page **SEO Research Decision:** ``` Keyword: "AI security audit tool" (450 monthly searches) Competition: Medium (mostly enterprise tools, no Claude-specific content) Search Intent: Developer looking for automated security checking Decision: High priority skill page ``` **Content Structure Decision:** ``` Primary content: What security-auditor skill detects (XSS, SQL injection, etc.) Secondary content: Example audit output on sample vulnerable code Call-to-action: "Install with: wg install security-auditor" Internal linking: Links to code-quality-auditor and penetration-tester skills ``` **Traffic Conversion Flow:** ``` Developer googles "AI security audit tool" → Lands on someclaudeskills.com/skills/security-auditor → Sees example finding real CVE in demo code → Clicks "Install with WinDAGs" → Downloads WinDAGs CLI → Runs security audit on their own code → Hits free tier limit after 3 audits → Upgrades to WinDAGs Pro ($49/month) ``` **Results after 90 days:** - Page ranks #3 for target keyword - 127 organic visitors/month to this page - 23% click-through rate on WinDAGs install CTA - 12 WinDAGs conversions attributed to this page ($588 MRR) ### Example: OS/2 Subdomain Launch Strategy **Community Targeting Decision:** ``` Primary: r/retrobattlestations (180k members, high engagement on authentic retro content) Secondary: Hacker News (retro computing nostalgia threads get 100+ comments) Timing: Weekend launch for social media optimal sharing ``` **Content Preparation:** ``` Screenshots: Side-by-side OS/2 Warp 4 vs os2.someclaudeskills.com Authenticity details: Workplace Shell icons, system fonts, dialog box styles Easter eggs: Hidden OS/2 command prompts, IBM employee references Functionality: All 197+ skills browsable, search works, install CTAs present ``` **Launch Execution:** ``` Reddit post: "I rebuilt the Claude skills catalog in OS/2 Warp's UI" Post timing: Saturday 10am EST (peak r/retrobattlestations activity) HN submission: "Show HN: Claude skills browser with authentic OS/2 UI" Twitter thread: 8 screenshots comparing real OS/2 vs recreation ``` **Traffic Results:** - 2,847 visitors to OS/2 subdomain in first week - 312 click-throughs to main someclaudeskills.com - 43 WinDAGs installs from OS/2 traffic - 8 new backlinks from retro computing blogs - Main site traffic increased 34% during launch week ## Quality Gates - [ ] Each skill page targets keyword with >50 monthly search volume - [ ] Every page has exactly one WinDAGs install CTA above the fold - [ ] Site generates >500 organic visitors/month before any premium features - [ ] OS/2 subdomain authentic to actual Workplace Shell UI standards - [ ] Blog content targets keywords with >100 monthly searches and WinDAGs connection - [ ] Community submission queue cleared within 72 hours of submission - [ ] Internal linking connects related skills (average 3+ links per skill page) - [ ] Site loads in <3 seconds on 3G connection (mobile traffic = 60%+ of users) - [ ] WinDAGs conversion rate from site traffic >3% before marketplace features - [ ] All skill pages have structured data for rich search snippets ## NOT-FOR Boundaries **NOT for individual skill creation** → Use **agent-creator** for writing SKILL.md files and skill development **NOT for technical SEO implementation** → Use **seo-visibility-expert** for keyword research, meta tags, structured data coding **NOT for Claude ecosystem evangelism** → Use **claude-ecosystem-promoter** for conference talks, community outreach, partnership development **NOT for WinDAGs product strategy** → Use **windags-customer-persona** for pricing, features, competitive positioning of the core product **NOT for venture capital or fundraising** → This skill covers organic growth strategy, not investment strategy or pitch deck development **NOT for marketplace technical architecture** → This is business strategy; use appropriate engineering skills for payment processing, user accounts, review systems