Skip to main content
ClaudeWave
Skill608 estrellas del repoactualizado 4d ago

directory-submission

**directory-submission** prepares platform-specific copy for submitting products and apps to directories, launch platforms, app stores, and curated lists. Use when a user needs tailored descriptions, submission guidance, or listings across multiple platforms like Product Hunt, Taaft, G2, or app stores. The skill reads project context when available and adapts copy to each platform's requirements and audience expectations.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/directory-submission && cp -r /tmp/directory-submission/skills/channels/community/directory-submission ~/.claude/skills/directory-submission
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Channels: Directory Submission

Guides submitting products, tools, or apps to directories and launch platforms.

**On each invocation**: On **first use** in the conversation, output the complete response (Introduction, Importance, Methods, Collaboration Channels, Rules, Avoid, Action). On **subsequent use** or when the user asks to skip (e.g., "just do it", "skip intro", "I already know"), go directly to Action.

Directory submission is a core channel for cold start—see **cold-start-strategy** for full launch planning. Directories offer more than listings: free/paid listings, ad placements, newsletter features, social promotion, and marketing campaigns. Platform types: AI tools (e.g. Taaft), product launch (e.g. Product Hunt), review platforms (e.g. G2), app stores, niche directories.

## Why Directory Submission Matters

*Platform examples are illustrative only. No affiliation, partnership, or endorsement implied.*

| Benefit | Description |
|---------|--------------|
| **Backlinks** | Quality directories pass link equity; improve domain authority and rankings. Focus on high-authority directories (DA 50+); avoid low-quality link farms. |
| **Real traffic & conversion** | Referral traffic from directories converts. ~42% of businesses report increased referral traffic after submission; referral conversion ~1.8% (B2C), 1.1% (B2B), 1.3% (SaaS). Use UTM to track; proper attribution can improve measured conversion by ~23%. |
| **Social proof for brand search** | When users search your brand name, directory listings (e.g. Product Hunt, G2, Taaft) often dominate SERP. Third-party presence signals legitimacy; consumers check 5-7 sources before deciding. Verified badges and consistent NAP across directories boost trust. See **serp-features** for SERP feature types. |

## Current Best Practices

**Quality over quantity.** Mass submission to hundreds of low-quality directories can harm rankings; strategic placement in 10-15 high-quality directories typically yields 15-25% improvement in indexing speed and branded search visibility.

| Practice | Why |
|----------|-----|
| **Prioritize DA/DR 50+** | High-authority directories pass link equity; low-quality link farms risk penalties |
| **Editorial review preferred** | Human-curated directories (vs. automated) carry more weight; Google's Helpful Content Update favors editorially-curated listings |
| **Niche over generic** | Industry-specific directories deliver faster results (30-60 days) and better topical relevance than generic sites (60-120 days) |
| **NAP consistency** | Name, Address, Phone identical across all listings--critical for local SEO |
| **Track submissions** | Document where you submitted, approval status, canonical topics |

**Budget reference**: Small businesses $300-500/mo; enterprises $1,500-3,000/mo for comprehensive programs. Results typically 30-60 days from high-authority directories.

## Initial Assessment

**Read project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it. Use sections 1-4, 5, 6, 8, 9 to generate submission content directly--no need to ask the user for info already in the context.

| Context section | Maps to directory fields |
|-----------------|---------------------------|
| 1. Product Overview | Name, one-line, category, pricing model |
| 2. Positioning Statement | Tagline, long description |
| 3. Value Proposition | Key messages, proof points -> Pros |
| 4. Target Audience | Description tone, use cases |
| 5. Existing Website | URL, key pages |
| 6. Keywords | Tags, negative keywords, Primary Task |
| 8. Brand & Voice | Tone, avoid terms, preferred wording — see **branding** for full brand strategy |
| 9. Product Documentation | Features, capabilities -> Other features |

**When context exists**: Generate ready-to-paste submission copy (tagline, short/long description, pros/cons, tags) tailored per platform. Output copy the user can paste into Taaft, Product Hunt, etc.

**When context is missing**: Gather from user's site; **search the web** for pricing, features, competitors, reviews, and any gaps. Then generate.

Identify:
1. **Product type**: AI tool, SaaS, app, Chrome extension, Shopify app
2. **Target directories**: AI tools, product launch, app stores, niche
3. **Readiness**: Landing page, screenshots, description, media kit

## Product / Website Info Required

**Source**: Project context (preferred) or user's site. Each directory needs different fields; prepare a base set, then adapt per platform.

### Standard Fields (Most Directories)

| Field | Typical Spec | Notes |
|-------|--------------|-------|
| **Product name** | 60-80 chars | Consistent spelling across all listings |
| **URL** | Working product/landing page | No redirect chains |
| **Tagline / one-liner** | <=60 chars (Taaft: max 12 words) | Catchy, benefit-focused |
| **Short description** | 150-300 chars | Used by many directories |
| **Long description** | 400-600 chars | For platforms that allow more |
| **Category / Task** | Platform-specific | Match taxonomy (Taaft: Primary + Secondary Tasks) |
| **Keywords / Tags** | 5-10 terms, comma-separated | Natural, no stuffing |
| **Contact** | Email, optional NAP | For verification |
| **Company name** | Legal entity | Some directories require |
| **Promo code** | If applicable | Product Hunt, deal platforms |
| **Other URLs** | Blog, Affiliate Program, FAQ | Optional but useful |
| **API availability** | Yes/No | AI/SaaS directories |
| **Demo video** | URL or file | Many platforms support |

**Platform-specific**: Taaft requires many more fields (icon, main image, demo video, features, models, built-with tools, modalities, pricing, legal URLs, pros/cons, socials, tracking links)--see Taaft section.

### Prepare Asset Tiers

Create multiple versions so you can match each directory's format without rewriting from scratch:

- **One-liner** (<=60 chars): Elevator pitch; "Remote Project Manager Pro" beats "Project Tool"
- **Short** (150-300 char
google-search-consoleSkill

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.

seo-monitoringSkill

When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.

ai-traffic-trackingSkill

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

traffic-analysisSkill

When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.

analytics-trackingSkill

When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.

community-forumSkill

When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.

product-hunt-launchSkill

When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.

distribution-channelsSkill

When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.