directory-submission
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first
npx skills add kostja94/marketing-skills --skill directory-submission --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Submits a product or app to directories, curated lists, launch platforms, or app stores by generating ready-to-paste copy per platform. Reads project-context.md when present. Triggers include mentions of directory submission, get listed, app store listing, submit to directories, curated list, Product Hunt, and similar terms. Also uses product-hunt-launch for Product Hunt launch day tactics and cold-start-strategy for full 0→1 planning.
How it works
On first use in a conversation, it outputs Introduction, Importance, Methods, Collaboration Channels, Rules, Avoid, Action. On subsequent uses or when skip is requested, it goes directly to Action. It reads sections from the context file (.claude/project-context.md or .cursor/project-context.md) to generate platform-tailored copy with fields like tagline, short/long descriptions, pros/cons, and tags. It supports multiple versions per field (A/B/C/D) to avoid duplication across directories. It structures content for per-platform tailoring (Product Hunt, Taaft, G2/Capterra, etc.), and requires building a rich content base (Definition, Importance, Features, Use cases, Solutions, Competitors, Pricing, Rules / Avoid) to adapt per directory.
When to use it
Use when the user requests directory submission assistance or when terms indicating directory submission arise (e.g., directory submission, get listed, app store listing, submit to directories, curated list, Product Hunt, directory ads, newsletter feature, directory campaign, Shopify App Store, Chrome Web Store). Use Product Hunt launch workflow via product-hunt-launch and full channel planning via cold-start-strategy. Read project-context first if available to generate ready-to-paste copy tailored to platform requirements.
What it can touch
If the skill indicates collaboration channels, use provisions for Newsletter, Ads, Social, and Campaigns as appropriate in outputs. It references fields like Product name, URL, Tagline / one-liner, Short description, Long description, Category / Task, Keywords / Tags, Contact, Company name, Promo code, Other URLs, API availability, Demo video, and platform-specific requirements (e.g., Taaft’s extra fields). It urges creating multiple asset versions and tailoring per platform.
Caveats
Mentions of platform-specific strategies and budgets are cited but any numbers or outcomes are to be taken from the user context or the skill's provided ranges. No promises beyond the content stated. License: MIT. Version: 1.2.0. Tools: cursor. Ensure alignment with the exact terms and sections described in the skill and its frontmatter references.
# 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 traf
- Why Directory Submission Matters
- Current Best Practices
- Initial Assessment
- Product / Website Info Required
- Standard Fields (Most Directories)
- Prepare Asset Tiers
- Rich Content Base (Build First, Use Everywhere)
- Multiple Versions for Differentiation (SEO & GEO)
- Tailor Per Platform (Different Expression, Different Emphasis)
- Consistency to Keep
- Directory Offerings (Beyond Listing)
- Collaboration Channels (Newsletter, Ads, Social, Campaigns)
- Directory Types
- Directory Lists (Curated Lists)
What does the directory-submission skill do?
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill directory-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.