directory-submission▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides submitting products, tools, or apps to directories and launch platforms.
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:
- Product type: AI tool, SaaS, app, Chrome extension, Shopify app
- Target directories: AI tools, product launch, app stores, niche
- 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 chars): Core value + one differentiator
- Long (400-600 chars): Problem -> solution story; features + benefits
Rich Content Base (Build First, Use Everywhere)
Even if a directory form does not require it, build a full reference so you can tailor per platform and for SEO/GEO. Search the web when info is missing.
| Section | Content | Use For |
|---|---|---|
| Definition | What the product is; category; one-sentence positioning | Intro text, GEO-friendly summaries |
| Importance | Why it matters for the target audience; key differentiator | Long descriptions, first comments |
| Features | Core capabilities; technical specs; integrations | Taaft, G2, comparison sites |
| Use cases | Who uses it; workflows; outcomes | Taaft tasks, niche directories |
| Solutions | Problems solved; before/after | Product Hunt, curated lists |
| Competitors | Alternatives (e.g. Competitor A, B); how this differs | Comparison sites, G2 |
| Pricing | Plans, credits, free tier | G2, Capterra, budget-focused lists |
| Rules / Avoid | What to emphasize; what to avoid per platform | Quality control |
Multiple Versions for Differentiation (SEO & GEO)
Do not submit identical copy to every directory. Duplicate content hurts SEO and reduces GEO citation diversity. Generate at least 2-3 distinct versions per field (tagline, short, long) so:
- Different directories show different angles
- AI tools and search engines see varied, non-duplicate signals
- Users can pick the best fit per platform or A/B test
| Version | Angle | Best For |
|---|---|---|
| A | Feature-led (capabilities, specs) | Taaft, technical directories |
| B | Benefit-led (outcomes, use cases) | Product Hunt, creator-focused |
| C | Comparison-led (vs. competitors) | AlternativeTo, G2 alternatives |
| D | Audience-led (who, workflow) | Niche directories, vertical lists |
Tailor Per Platform (Different Expression, Different Emphasis)
Do not copy-paste identical descriptions. Each directory has a different audience and format; customizing per platform improves approval, visibility, and conversion.
| Platform Type | Audience | Emphasis | Tone |
|---|---|---|---|
| Product Hunt | Indie makers, founders, early adopters | See product-hunt-launch for full workflow | Community, authentic, maker-friendly |
| Taaft | AI tool seekers, task/job-oriented | Tasks and jobs your tool solves; keyword-rich for AI use cases; "what can I do with this" | Functional, searchable, use-case driven |
| G2 / Capterra | Enterprise buyers, comparison shoppers | Features, integrations, pricing; review-oriented; social proof | Professional, comparison-ready |
| AlternativeTo | Users switching from competitors | "Alternative to X"; migration ease; differentiation | Comparison, migration, alternatives |
| Niche directories | Vertical (e.g., e-commerce, healthcare) | Industry keywords; vertical pain points; compliance if relevant | Vertical-specific, jargon-appropriate |
| App stores (Shopify, Chrome) | Merchants / extension users | Merchant value (Shopify); use case (Chrome); screenshots show workflow | Benefit-first, feature-clear |
Consistency to Keep
While tailoring, keep consistent across all listings:
- Product name spelling and formatting
- Core positioning (who it's for, main benefit)
- Contact info format (NAP if applicable)
Inconsistent NAP or product names can hurt SEO and trust.
Directory Offerings (Beyond Listing)
Directories typically offer multiple touchpoints--not just inclusion in the catalog:
| Offering | Description | Use When |
|---|---|---|
| Listing | Free or paid inclusion in directory catalog | Baseline visibility, backlinks, evergreen traffic |
| Ad placements | Sponsored slots, banners, featured placement | Need boosted visibility; budget for paid promotion |
| Newsletter | Featured in directory's email to subscribers | Product Hunt, Taaft; high-intent audience |
| Social promotion | Directory shares your product on X, LinkedIn, etc. | Launch day amplification; viral potential |
| Marketing campaigns | Bundled packages: listing + newsletter + ads + social | Full-funnel campaign; product launch or relaunch |
Strategy: Start with free listing for backlinks and baseline traffic. Layer paid options (ads, newsletter features, campaigns) when ROI justifies--especially for launches or when organic listing underperforms.
dofollow vs nofollow: dofollow passes link equity for SEO; nofollow does not. But the goal is conversion--if users click through and convert, the shorter path (direct traffic) can outweigh SEO benefit. Small, unknown directories have driven three-figure annual subscriptions from a single 10-minute submission.
Collaboration Channels (Newsletter, Ads, Social, Campaigns)
Include this section in output when the user invokes this skill. Directories offer follow-on collaboration beyond listing:
| Channel | Platform Examples | Scale / Notes |
|---|---|---|
| Newsletter | Product Hunt, Taaft | High-intent; paid or bundled; best for launches |
| Ad placements | Taaft banners, Product Hunt Featured, G2/Capterra sponsored | Use UTM (e.g. utm_medium=paid); test after organic listing. See directory-listing-ads for Taaft, Shopify App Store, G2, Capterra paid campaign setup |
| Social promotion | Taaft, Product Hunt share on X, LinkedIn | Launch-day amplification; @ platform accounts when posting |
| Marketing campaigns | Taaft: listing + newsletter + ads + social | Full-funnel; product launch or relaunch; budget-dependent |
Phased approach: (1) Free listing first. (2) Newsletter features when launching. (3) Ads if organic underperforms. (4) Campaign packages for major launches.
Budget reference: Small teams $0-500/mo (listing + occasional newsletter); growth $300-500/mo; enterprise $1,500-3,000+/mo for full programs.
Directory Types
| Type | Examples | Best For | Traffic / Benefit |
|---|---|---|---|
| AI tools | Taaft (There's An AI For That) | AI products, SaaS | 4M+ monthly visitors; 700-10K+ visitors per listing |
| Developer tools | DevHunt | OSS, dev tools, APIs | Dev-focused; GitHub-verified; free; see open-source-strategy |
| Product launch | Product Hunt | New products, features | See product-hunt-launch for full PH workflow |
| App stores | Shopify App Store, Chrome Web Store | Apps, extensions | Merchant/developer discovery |
| Niche directories | Industry-specific lists | Vertical SaaS, tools | Targeted backlinks, SEO |
| Review platforms | G2, Capterra | B2B SaaS, commercial software | Rich snippets (reviews, ratings); higher-intent buyers; vendor verification required |
| Curated lists | Best-of roundups, Awesome lists, niche blog posts | Any product | Editorial backlinks; outreach to list authors; same prep as directories |
Dimension diversity: Your product has multiple dimensions--AI tool, productivity tool, SaaS, industry-specific. After AI directories, submit to vertical niches (e.g., e-commerce tools, marketing tools, cross-border commerce tools). Smaller traffic but higher intent and conversion.
Feature vs solution directories: Feature directories (text, image, video, audio by modality) suit AI enthusiasts who compare tools. Solution directories (workflow-oriented: SEO tools, EDM marketing, TikTok analytics) suit users seeking 10x productivity in a workflow--often higher conversion for B2B.
Directory Lists (Curated Lists)
Same principles as directories--backlinks, traffic, discovery. Curated lists are editorial roundups (e.g., "Best AI tools 2025," "Top 10 SaaS for marketing") published on blogs, newsletters, or dedicated list sites.
| Type | Examples | How to get listed |
|---|---|---|
| Best-of / Top N | "Best SEO tools," "Top 10 AI writing tools" | Outreach to list authors; provide product info, use case, differentiator |
| Awesome lists | GitHub Awesome-*, Awesome Tools | Submit PR or contact maintainer; follow list format. See github for creating or optimizing awesome-style curated lists. |
| Comparison / alternatives | AlternativeTo, G2 alternatives | Submit as alternative to X; comparison-focused copy |
| Niche roundups | Industry blogs, newsletters | Pitch for inclusion; offer quote, case study, or exclusive angle |
Preparation: Same as directory submission--product info, tagline, short/long description, screenshots. Tailor pitch to list theme (e.g., "best for startups," "budget-friendly," "enterprise-ready").
Tip: One solid backlink from a curated list often beats many low-quality directory links. Prioritize lists with editorial oversight and real traffic.
Key Platforms
Taaft (There's An AI For That)
- URL: taaft.com/submit or theresanaiforthat.com/submit
- Scale: 46K+ AI tools, 4M+ monthly visitors, 2.8M+ newsletter subscribers
- Listing: 700-10K+ guaranteed targeted visitors per listing; early launch bonus (up to $300 PPC credits for launching on Taaft first)
- Beyond listing: Newsletter features (reach 2.8M+ subs), ad placements, social promotion, marketing campaigns
- Free vs paid: Submission fee varies; sometimes free listing is possible (e.g., early action, specific criteria)--check current pricing
- Use when: Product is AI-related; want AI-focused traffic, backlinks, and paid amplification options
Taaft submission fields (prepare before submitting; changes can take up to 24h to reflect):
| Category | Field | Spec / Notes |
|---|---|---|
| Identity | Name | Product/tool name |
| Primary Task | Search and select from Taaft task taxonomy (e.g., Text to speech, Image generation) | |
| Secondary Tasks | Search and add; subject to approval, processed daily | |
| Tagline | Max 12 words; benefit-focused | |
| Description | Full product description; use-case driven, keyword-rich | |
| Country | Select from list | |
| Media | Icon | SVG preferred; PNG/JPEG/WEBP <=500x500 px |
| Main image | Product screenshot or hero visual | |
| Demo video | Optional; no captions (Taaft auto-generates for all languages) | |
| Features | Supported features | Check: Agents, API, MCP, Run locally, Open source, No signup, Supports TAAFT code |
| Other features | Ordered list by importance; add keywords (e.g., ai voice, text to voice, voice cloning) | |
| Tech | Search models | Add AI models used (e.g., GPT-4, Claude) |
| Built with | Select from platform options (e.g. Cursor, Lovable, v0.dev) | |
| Modalities | Supported Inputs/Outputs: Text, Image, Audio, Video, 3D, API, Code, etc. | |
| Pricing | Pricing model | Freemium, Free trial, Paid, etc. |
| Paid starting price (USD) | If paid | |
| Billing frequency | Monthly, Yearly, etc. | |
| Hard paywall | Does tool show paywall before letting users try? | |
| Legal | Refund Policy | No Refunds / Custom text |
| Refund Policy URL | Optional | |
| Privacy Policy URL | Required | |
| Terms & Conditions URL | Required | |
| Discovery | Tags | Comma-separated; use for search and filtering |
| Negative keywords | Comma-separated; exclude from irrelevant searches | |
| Tracking | Tracking link | Custom UTM (default: ?ref=taaft&utm_source=taaft&utm_medium=referral) |
| PPC tracking link | For PPC ads (default: ?ref=taaft_feat&utm_source=taaft_feat&utm_medium=referral) | |
| Socials | Facebook, TikTok, Instagram, Telegram, Discord, X, YouTube, LinkedIn | URLs |
| Pros / Cons | Pros | Add multiple; feature and benefit bullets |
| Cons | Add multiple; honest limitations (builds trust) |
Tip: Pros and cons help users compare; be honest--negative keywords and cons improve relevance and trust.
Product Hunt
See product-hunt-launch for full preparation, launch day strategy, and post-launch. Product Hunt: producthunt.com/launch; free listing; community upvotes; Product Hunt Daily newsletter; paid featured placement. Use when launching new product or major feature.
DevHunt (Developer Tools)
- URL: devhunt.org
- Audience: Developers, indie makers, open source maintainers
- Content: Developer tools, APIs, libraries, open source projects; GitHub-verified submissions; 50+ categories
How to use directory-submission on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add directory-submission
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches directory-submission from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate directory-submission. Access the skill through slash commands (e.g., /directory-submission) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★51 reviews- ★★★★★Kabir Park· Dec 28, 2024
directory-submission fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ishan Torres· Dec 28, 2024
directory-submission has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Henry Kim· Dec 24, 2024
Keeps context tight: directory-submission is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Olivia Liu· Dec 12, 2024
directory-submission is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Gill· Dec 4, 2024
directory-submission reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Charlotte Choi· Nov 23, 2024
directory-submission is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ishan Sanchez· Nov 19, 2024
We added directory-submission from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Min Li· Nov 3, 2024
directory-submission reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kiara Harris· Oct 22, 2024
I recommend directory-submission for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Zara Smith· Oct 14, 2024
Useful defaults in directory-submission — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 51