SkillAgentSearch skills...

directory-submissions

Launch and submit a startup, SaaS, AI tool, or MCP server across 50+ high-DR software review sites, startup launchpads, MCP registries, and GitHub Awesome lists using a single Product Manifest and autonomous browser/PR submission workflow

Install / Use

npx skills add Illyism/seo-skills --skill directory-submissions

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Automation

Supported Platforms

Universal

Our assessment of directory-submissions

directory-submissions scores 90/100 on our quality scale, 1230th of 2,758 Automation skills we index (top 45%).

Its SKILL.md is 13 KB long, well organised into 10 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

It has 531 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 38 days ago, so directory-submissions is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-21. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

directory-submissions compared with similar skills

All 4 of these similar skills score higher than directory-submissions; compare them before choosing.

SkillScoreStarsUpdatedFormat
directory-submissions (this skill)by Illyism9053138d agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md

Frequently asked questions

How do I install directory-submissions?
Run npx skills add Illyism/seo-skills --skill directory-submissions. The install tabs above show the steps for each supported agent.
Which AI agents does directory-submissions work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is directory-submissions safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is directory-submissions still maintained?
The repository was last updated 38 days ago, so directory-submissions is actively maintained.

name: directory-submissions description: Launch and submit a startup, SaaS, AI tool, or MCP server across 50+ high-DR software review sites, startup launchpads, MCP registries, and GitHub Awesome lists using a single Product Manifest and autonomous browser/PR submission workflow. Use when launching a new product from DR 0, building foundational dofollow backlinks, publishing one repo to 15+ MCP & agent registries, or running directory submissions. metadata: author: illyism source: https://linkdr.com/resources/directories version: 1.0.0

Startup, AI tool, and MCP directory submissions

Review sites, launchpads, AI tool directories, MCP registries, and GitHub Awesome lists all ask for the same ~25 product fields at different lengths and aspect ratios.

Prepare one submission-manifest.json, add the repo files that 15+ MCP and agent registries index, then work through the 5 waves below. Log every submission in submissions-log.json so a rerun skips what is done.

Companion resources:

Step 1: Prepare submission-manifest.json once

Before opening any form or pull request, build submission-manifest.json in the project root. Read the codebase, package.json, landing page metadata, and public /images assets first, and ask the user only for missing facts:

{
  "product": {
    "name": "YourProduct",
    "slug": "yourproduct",
    "domain": "yourproduct.com",
    "url": "https://yourproduct.com",
    "pricing_url": "https://yourproduct.com/pricing",
    "contact_email": "press@yourproduct.com",
    "contact_page": "https://yourproduct.com/contact",
    "privacy_url": "https://yourproduct.com/privacy",
    "terms_url": "https://yourproduct.com/terms"
  },
  "copy": {
    "tagline_40c": "Punchy plain-English value prop (<=40c)",
    "tagline_60c": "Search-intent headline naming what the tool does (<=60c)",
    "mcp_description_100c": "Strict <=100 character summary required by Official MCP Registry validator.",
    "awesome_list_bullet": "- [YourProduct](https://yourproduct.com) - Factual one-line description with zero hype.",
    "description_160c": "15-25 word summary stating who it is for, what input it takes, and what output it produces (<=160c).",
    "description_500c": "Two-paragraph factual overview (minimum 510 chars) covering the core workflow, supported integrations/formats, and concrete differentiators, with zero em dashes or AI buzzwords.",
    "key_features": [
      "Concrete input -> output capability",
      "Verification, speed, or accuracy guarantee",
      "API, CLI, SKILL.md, or MCP integration support",
      "Export formats or team controls"
    ]
  },
  "taxonomy": {
    "primary_category": "Developer Tools / AI Tools / SaaS",
    "tags": ["ai", "saas", "developer-tools", "automation", "seo"],
    "competitors_replaced": ["CompetitorA", "CompetitorB", "CompetitorC"],
    "pricing_model": "Freemium",
    "starting_price_usd": 19,
    "free_tier_details": "Exact free tier or trial allowance"
  },
  "assets": {
    "favicon_64": "https://yourproduct.com/favicon.ico",
    "logo_square_512": "https://yourproduct.com/logo-512x512.png",
    "og_image_1200x630": "https://yourproduct.com/og.png",
    "screenshots_16x9": [
      "https://yourproduct.com/screenshots/01-hero-1280x800.png",
      "https://yourproduct.com/screenshots/02-workflow-1280x800.png",
      "https://yourproduct.com/screenshots/03-output-1280x800.png"
    ]
  },
  "agent_and_mcp": {
    "mcp_endpoint": "https://yourproduct.com/mcp",
    "github_repo": "https://github.com/yourorg/yourproduct"
  }
}

Step 2: One repo, 15+ MCP and agent registries (if you ship an MCP server or SKILL.md)

Six small files in your public GitHub repo let agent marketplaces index the product:

  1. server.json: Keep description strictly ≤ 100 characters or the Official MCP Registry validator rejects it.
  2. glama.json: { "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": ["your-github-handle"] } (required to claim on Glama and pass awesome-mcp-servers CI).
  3. .cursor-plugin/plugin.json + .mcp.json: Indexed by Cursor Marketplace (cursor.com/marketplace) and cursor.directory.
  4. .claude-plugin/plugin.json + .mcp.json: Indexed by Claude Code plugin directories.
  5. gemini-extension.json + repo topic gemini-cli-extension: Auto-indexed within 24 hours by Google's Gemini CLI Extensions gallery.
  6. SKILL.md: Auto-indexed by skills.sh, ClawHub (clawhub.ai), and MCP Market (mcpmarket.com).

Then publish once to the Official MCP Registry so downstream directories (glama.ai, pulsemcp.com, mcp.directory, apitracker.io, claudemcp.org) sync automatically:

brew install mcp-publisher
mcp-publisher login github
mcp-publisher publish

Step 3: Work through the 5 waves (50 directories)

Wave 1: Software review sites (do first)

Google's Knowledge Graph, ChatGPT, and Perplexity cross-check these domains when users search "best X" or "X alternatives":

| Directory | DR | Submit URL | Notes | | --- | --- | --- | --- | | Awesome Tools | 80 | https://awesome.tools/submit | Free verified dofollow listing (badge) or instant Featured Launch; supports JSON API & WebMCP | | AlternativeTo | 81 | https://alternativeto.net/manage-item/ | Free dofollow link · 1–5d moderator review · Top LLM citation source for "X alternatives" | | SaaSHub | 80 | https://www.saashub.com/submit | Free dofollow link (2–4w) or paid fast-track | | GoodFirms | 86 | https://www.goodfirms.co/get-listed | Free vendor profile · 3–7 business days | | G2 | 91 | https://sell.g2.com/create-a-profile | Free vendor profile · #1 B2B citation source in ChatGPT & Perplexity | | Capterra / GetApp / Software Advice | 90 | https://www.gartner.com/en/digital-markets/Role-Selection | One Gartner Digital Markets application lists on all 3 sites | | ProvenExpert | 81 | https://www.provenexpert.com/en-us/registration/ | Free profile · Live right after registration | | StackShare | 78 | https://stackshare.io/submit | Free developer tool profile · 1–5d review | | SoftwareWorld | 74 | https://www.softwareworld.co/register/ | Free vendor listing · 3–7 business days | | Alternative.me | 73 | https://alternative.me/how-to/submit-software/ | Free software listing · 3–7d review | | LibHunt | 72 | https://www.libhunt.com/repo/submit | Free developer & open-source tool tracking | | Tekpon | 68 | https://tekpon.com/get-listed/ | Free SaaS vendor profile · 3–7 business days |

Wave 2: MCP and AI agent registries

  • GitHub MCP Registry (https://github.com/mcp · DR 98, pulls from Official MCP Registry)
  • OpenAI ChatGPT App Directory (https://platform.openai.com/plugins · DR 93, verify /.well-known/openai-apps-challenge)
  • Cursor Marketplace (https://cursor.com/marketplace/publish · DR 84) & cursor.directory (https://cursor.directory/ · DR 69)
  • ClawHub Skills Registry (https://clawhub.ai/ · DR 83)
  • Official MCP Registry (https://modelcontextprotocol.io/registry/quickstart · DR 82)
  • Smithery (https://smithery.ai/ · DR 79), Glama (https://glama.ai/mcp/servers · DR 77), LobeHub MCP (https://lobehub.com/mcp · DR 76)
  • mcpservers.org (https://mcpservers.org/submit · DR 71) & MCP Market (https://mcpmarket.com/submit · DR 62)

Wave 3: Startup and developer launchpads

  • Hacker News (Show HN) (https://news.ycombinator.com/submit · DR 91) & Product Hunt (https://www.producthunt.com/posts/new · DR 91)
  • Fazier (https://fazier.com/submit · DR 84), Twelve Tools (https://twelve.tools/submit · DR 83), Findly.tools (https://findly.tools · DR 82)
  • Peerlist Launchpad (https://peerlist.io/user/projects/add-project · DR 78), BetaList (https://betalist.com/submit · DR 77), PeerPush (https://peerpush.com/submit · DR 77)
  • Uneed (https://www.uneed.best/submit-a-tool · DR 76), LaunchIgniter (https://launchigniter.com/submit · DR 75), DevHunt (https://devhunt.org/account/tools/new · DR 68)

Wave 4: AI tool directories

  • ShowMeBest.AI (https://showmebest.ai/submit · DR 77), Good AI Tools (https://goodaitools.com/submit · DR 75), AI Agents Directory (https://aiagentsdirectory.com/submit-agent · DR 75)
  • Supertools / The Rundown (https://www.therundown.ai/tools · DR 72), Insidr.ai (https://www.insidr.ai/submit-tools/ · DR 71), aidirectori.es (https://www.aidirectori.es/submit-ai-tool · DR 71)
  • AItrendytools (https://www.aitrendytools.com/submit · DR 69), Foundr.ai (https://foundr.ai/submit · DR 64), DokeyAI (https://dokeyai.com/submit · DR 62), Easy With AI (https://easywithai.com/submit-tool/ · DR 60)

Wave 5: Web design galleries (once the landing page is polished)

  • One Page Love (https://onepagelove.com/submit · DR 79), Land-book (https://land-book.com/submission-guidelines · DR 66), Recent Design (https://recent.design/signup · DR 64)
  • Lapa Ninja (mailto:hi@lapa.ninja · DR 61), Minimal Gallery (https://minimal.gallery/submit/ · DR 61), Hover States (https://www.hoverstat.es/about/ · DR 56)
  • Curated Design (https://www.curated.design/submit · DR 52), Footer Design (https://www.footer.design/submit · DR 52), TOOOLS.design (https://www.toools.design/submission · DR 48)

The full database of 856+ directories comes with any backlink order at linkdr.com/resources/directories.

Step 4: Rules for agent submissions

When you run browser or GitHub PR submissions as an agent, follow all 10:

  1. No unapproved spend. Submit only to free tiers unless the user explicitly approves a paid fast-track checkout. If a submission lands on a Stripe/PayPal paywall with no free path, record status: "skipped_paid_only" and continue.
  2. Contact privacy. Directories get scraped across 500+ aggregator sites. Never submit personal phone numbers, home/registered-agent street addresses, or internal holding LLC names. Always use the product brand name, "Media Relations", a generic role email (press@<domain>), empty phone/address fields, and https://<domain>/contact.
  3. Factual copy. Never use em-dashes, emojis, or hype buzzwords ("unleash", "revolutionize", "seamless", "game-changing"). Editors and Awesome-list maintainers reject copy that reads as AI marketing.
  4. Agent endpoints before browser forms. Check whether the directory exposes a JSON, MCP, or agent endpoint (for example https://awesome.tools/api/tools/submit, /agent, /api/mcp, or /llms.txt) before driving a browser UI.
  5. Honeypots. Never fill any input that is hidden (!isVisible(), aria-hidden="true", tabindex="-1", type="hidden", style*="scale(0)", display:none) or carries spam-trap names/labels (opl_hp_field, _honeypot, bot-field, website_url alongside a visible url field, or "Leave this empty").
  6. Embedded forms. If a /submit page renders an embedded widget ([data-paperform-id], tally.so, typeform.com, airtable.com, embed.fillout.com), open the standalone form URL directly in a top-level tab so inputs and file uploads work.
  7. Assets. Keep 512×512 PNG + 48×48 WebP logos, a 1200×630 OG image, and three 1280×800 screenshots (<300 KB WebP + PNG) ready before starting batch submissions.
  8. Email verification. Check press@<domain> for magic links and 6-digit codes right away so listings don't stall in unverified state.
  9. GitHub Awesome PRs. Before opening any

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars531
CategoryAutomation
Updated1mo ago
Forks56

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium