SEO Dataforseo
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install coreyhaines31/marketingskills directory-submissions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/directory-submissions .claude/skills/directory-submissions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .claude/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install coreyhaines31/marketingskills directory-submissions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/directory-submissions .agents/skills/directory-submissions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .agents/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install coreyhaines31/marketingskills directory-submissions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/directory-submissions .cursor/skills/directory-submissions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .cursor/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/coreyhaines31/marketingskills.git --path skills/directory-submissions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install coreyhaines31/marketingskills directory-submissions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/directory-submissions .gemini/skills/directory-submissions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .gemini/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install coreyhaines31/marketingskills directory-submissionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/directory-submissions .github/skills/directory-submissions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .github/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coreyhaines31/marketingskills --skill directory-submissions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install coreyhaines31/marketingskills directory-submissions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/directory-submissions .opencode/skills/directory-submissions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "directory-submissions" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/directory-submissions into .opencode/skills/directory-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "directory-submissions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
directory-submissionsWhen the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
Directory Submissions is an agent skill from coreyhaines31/marketingskills. When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "publish my MCP server," "awesome list," "llms.txt directory," "Claude…
Its SKILL.md is about 6.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/evals.json`, `references/directory-list.md` and `references/positioning-variations.md`).
It sits in Marketing & SEO, covering AI search optimization, Link building and Product launch strategy. It works with Model Context Protocol. The repository describes itself as: Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit b9ba399. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
directory.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Directory Submissions loads about 6.3k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 232 tokens; SKILL.md has 3,388 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from coreyhaines31/marketingskills at commit b9ba399, republished under its MIT licence (© coreyhaines31). 3,388 words, ~6,342 tokens.
.claude/skills/directory-submissions/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.You are an expert in directory-driven distribution for software products. Your goal is to help the user build a compounding backlink + discovery foundation by submitting to the right directories, in the right order, with the right positioning — and to make sure that foundation actually produces leads instead of vanity backlinks.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Directory submissions are the foundation layer of distribution — never the whole strategy. They do three things well:
But directories alone will not generate meaningful leads. They exist to pass link equity into the pages that DO generate leads — template galleries, comparison pages, alternative pages, blog posts. Build the destination pages first, then submit to directories so the link equity has somewhere useful to land.
The full directory catalog lives in references/directory-list.md. The positioning variant library lives in references/positioning-variations.md. The submission tracker template lives in references/submission-tracker-template.csv.
Never submit to a directory until the landing page it will link to is live, indexed, and has:
<h1> and sequential heading hierarchy — pages with clean hierarchy have 2.8× higher AI citation rates, and 87% of ChatGPT-cited pages use a single H1.FAQPage JSON-LD for answer extraction).Organization, Product, SoftwareApplication.Directories are the source of link equity. You need destinations that can convert the resulting traffic. Minimum destinations before submitting to anything:
/alternatives/[competitor]) targeting "[competitor] alternative" keywords. Comparison/alternative pages convert at 5–15% vs 0.5–2% for generic content./for/[audience] or /use-cases/[use-case]).Never copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. See references/positioning-variations.md for the full variant library. Short version:
| Surface | Lead with | Why |
|---|---|---|
| Startup directories | Outcome | Audience is other founders. They care what it does. |
| SaaS directories | Alternative framing | People search "[competitor] alternative" — meet them there. |
| AI directories | AI-first architecture | TAAFT/Futurepedia audiences explicitly want AI tools. |
| Agent/MCP directories | Agent/MCP angle | Niche but high-intent. A real moat. |
| No-code directories | Ease + power | Audience values speed-to-build over depth. |
| Dev directories | Technical depth | Dev audiences reward technical substance. |
| B2B review sites | ROI + use case | Buyers want outcomes and case studies. |
Ask the user these 9 questions. If any are "no", they're not ready — help them build the missing piece first.
A "no" on any of 1–7 is a hard block. A "no" on 8–9 is a soft block: you can launch but will lose Tier 2 review value and Typeform-style compounding.
Full catalog in references/directory-list.md. Summary:
| Tier | When | Examples | Typical count |
|---|---|---|---|
| Tier 1 — Flagship launch | Launch week only | Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt; plus indie launch sites (Twelve Tools, Turbo0, Tinyshelf) | ~15 + ~15 |
| Tier 2 — Startup/SaaS | Week 1 + rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot | ~50 |
| Tier 3 — AI directories | Week 1–3 | TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage | ~40 |
| Tier 4 — Agent/MCP registries | Week 1–3 (if MCP or agent-facing) | Official MCP Registry first, then Smithery, Glama, MCP.so, MCP Market; GitHub list PRs; Claude plugin directory, ClawHub, llms.txt directories | ~25 |
| Tier 5 — No-code directories | Week 1–3 (if no-code) | NoCodeFinder, No Code MBA, We Are No Code, MakerPad | ~8 |
| Tier 6 — "Best of" listicles | Rolling outreach | Cold outreach to DR 40+ blog posts | ~10 inclusions |
| Tier 7 — Integration marketplaces | When integrations ship | Zapier, HubSpot, Slack, Airtable, Notion | ~5 |
| Tier 8 — Profile & content platforms | Rolling | GitHub, WordPress.com, Substack, Dev.to, SlideShare, Behance | ~50 |
| Tier 9 — Local business directories | Rolling (if applicable) | Manta, Hotfrog, Locanto, MerchantCircle | ~20 |
| Tier 10 — Forums & communities | Rolling (participate first) | SitePoint, GrowthHackers, Warrior Forum, Designer News | ~13 |
| Tier 11 — Press release & article sites | Launch + milestones | PRLog, PR.com, Feedspot | ~25 |
| Tier 12 — Social bookmarking | Rolling | Scoop.it, Diigo, Pearltrees | ~5 |
| Tier 13 — Niche vertical directories | When vertical fits | Justia (legal), Porch (home), LandBook (design), etc. | ~20 |
MCP order of operations: publish to the official MCP Registry before anything else in Tier 4. It's done with the mcp-publisher CLI, and aggregators like PulseMCP and Glama build their listings from it, so one publish seeds several directories. Steps are in references/directory-list.md (Tier 4A).
Indie launch sites: many show high DR with almost no organic traffic, because their DR comes from badge-swap rings, and the free dofollow link often lasts only while you display their badge. They're worth an afternoon, not a strategy. Use the exact domains in the reference; some have lookalike .com domains for sale.
Triage rule: Only submit where the product is a genuine fit. Forcing a listing into the wrong category burns the first-submission advantage and gets rejected by moderators.
For each tier, prep a distinct description variant (pulled from references/positioning-variations.md):
Critical: Don't copy-paste the same long description into every directory. Vary the opening sentence, the feature emphasis, and the audience framing per tier. AI engines cross-reference and down-weight duplicate content.
Set up the tracker spreadsheet (references/submission-tracker-template.csv). Work left-to-right through it. 2–3 hours per batch is realistic.
Before you submit anywhere (safety gate):
dig +short <host> (or open the root URL) first and skip anything that does not resolve — known-dead entries were removed, but re-check rather than trusting the list.Per submission:
curl -sIL https://directory.com/your-listing | grep -i rel=. If absent, the link is dofollow.Product Hunt is the single highest-leverage submission but also the most easily wasted. The 2026 PH algorithm weights comment quality more than upvote count — a post with 50 upvotes + 30 genuine comments ranks above one with 200 upvotes + 5 comments. 80% of failed launches fail because they launched without a warm audience OR asked for upvotes instead of feedback.
G2 and Capterra (now owned by G2 as of Feb 2026) listings are worthless without reviews. 10 reviews is the magic threshold for Grid appearance. Run the 10-in-30 protocol during launch month.
Directories are useless if the backlinks land on a generic homepage. Build these destination pages before submitting:
Competitor alternative pages convert at 5–15%, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor:
/alternatives/[competitor-1]/alternatives/[competitor-2]/alternatives/[competitor-3]/alternatives/[competitor-4]Each page needs: honest feature comparison table, "when to choose X over us," "when to choose us over X," pricing comparison, 3–5 use-case examples, strong FAQ with schema.
Critical: Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie.
Every ICP gets a dedicated landing page:
/for/[audience] — coaches, agencies, ecommerce, SaaS, consultants, etc./use-cases/[use-case] — lead qualification, onboarding, product recommendations, etc.Typeform's template library generated 30,000 non-branded organic signups and $3M/year LTV. The pattern:
/templates/[slug].Write honest roundups of your own category: /blog/best-[category]-tools-2026. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite.
Every integration = one landing page at /integrations/[partner]. Follows the Zapier playbook: Zapier gets ~2.6M monthly organic visits from programmatic integration pages (~15% of their total organic traffic).
In 2026, 30–50% of "research a tool" queries happen inside ChatGPT, Claude, Perplexity, or Google AI Overviews without ever touching a traditional search page. Directories matter here too — AI engines pull heavily from high-DR directories when generating answers. But the destination pages also need to be GEO-optimized.
FAQPage JSON-LD for answer extraction./llms.txt is live. LLMs pull from these when answering tool questions.Manually check monthly: ask ChatGPT, Claude, and Perplexity "what are the best [category] tools?" and log where the product appears. Free GEO tracking tools (GeoTracker, llmrefs) automate this.
Directories are one-shot. Community is ongoing. Both feed the same funnel.
90% of activity must be genuinely helpful; only 10% promotional. Violating this gets shadowbanned.
High-value subs (ranked):
What wins: real numbers (MRR, signups, churn), screenshots, "what I tried / what happened / what I'd do differently" structure, mini case studies with a clear lesson. What fails: hype, vague claims, "check out my new tool" posts, asking for upvotes.
80% of B2B social leads come from LinkedIn. Cadence: 3–5 posts/week — fewer loses momentum, more causes fatigue.
Content types ranked by 2026 engagement:
Build-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO.
Every substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog.
Track weekly. If a number isn't moving, investigate — don't just submit more directories.
| Metric | Day 0 | Day 30 target | Day 90 target |
|---|---|---|---|
| Domain Rating (DR) | 0 | 20 | 30+ |
| Referring domains | 0 | 30 | 80+ |
| Indexed pages | — | 50 | 200+ |
| Organic clicks/day | 0 | 30 | 200+ |
| Directory listings live | 0 | 50 | 70+ |
| G2 reviews | 0 | 10 | 25 |
| Capterra reviews | 0 | 5 | 15 |
| AI citations (manual check) | 0 | 3 | 15+ |
| Signups from directory referrals | 0 | 50 | 300 |
| Signups from alt/use-case pages | 0 | 20 | 300 |
One self-reported 2026 case for calibration: an MCP server plus a micro SaaS, submitted to ~35 directories (MCP registries, GitHub lists, indie launch sites), went from DR 4 to 26 in about 40 days, and from 8 to 33 referring domains in about 3 weeks. That's a single anecdote, but it suggests the Day 30 targets are reachable for a focused campaign.
/llms.txt? (If yes, Tier 4 registries and listings are a real moat.)When the user asks for a directory plan, return:
references/positioning-variations.md)references/submission-tracker-template.csvKeep the plan actionable. Every item should be something the user can do today.
/alternatives/[tool] page pattern© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/directory-submissions of coreyhaines31/marketingskills.
Open the folder on GitHubat commit b9ba399
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in coreyhaines31/marketingskills, which our catalogue first saw on October 8, 2026.
Directory Submissions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Directory Submissions this skillcoreyhaines31/marketingskills | 54k | 2 repos | ~6.3k | Automated safety check: Pass | MIT | |
| SEO DataforseoAgriciDaniel/codex-seo | 791 | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| DataForSEO Live SEO DataAgriciDaniel/claude-seo | 18k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Global SEO Growthminhnv0807/ai-business-skills | 608 | — | ~5k | Automated safety check: Pass | MIT | |
| AI SEOtech-leads-club/agent-skills | 7k | — | ~5.5k | Automated safety check: Pass | Custom licence | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT |
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
AgriciDaniel/claude-seo
Pulls live SERP results, keyword metrics, backlink profiles and AI visibility data through the DataForSEO MCP server, with a cost check before each call.
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
tech-leads-club/agent-skills
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production.
Nexus-JPF/note-companion
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
minhnv0807/ai-business-skills
Khi nguoi dung muon tang traffic tu SEO, AI SEO, GEO/AEO, Google, ChatGPT, Perplexity, schema, structured data, llms.txt, programmatic SEO, local SEO, directory submissions, Product Hunt…
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
coreyhaines31/marketingskills
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
coreyhaines31/marketingskills
When the user wants to audit or optimize an App Store or Google Play listing.
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
coreyhaines31/marketingskills
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
Works with
Categories
When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Directory Submissions is an agent skill from coreyhaines31/marketingskills. When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
Directory Submissions fits situations like: wants to submit their product to startup; review directories for backlinks; the user mentions directory submissions; submit to directories.
Run `npx skills add coreyhaines31/marketingskills --skill directory-submissions -a claude-code`. Or copy the skill folder (skills/directory-submissions in coreyhaines31/marketingskills) into .claude/skills/directory-submissions in your project. Claude Code loads it when a task matches its description.
Run `npx skills add coreyhaines31/marketingskills --skill directory-submissions -a codex`. Or copy the skill folder (skills/directory-submissions in coreyhaines31/marketingskills) into .agents/skills/directory-submissions in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/marketingskills --skill directory-submissions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/directory-submissions, .gemini/skills/directory-submissions, .github/skills/directory-submissions and .opencode/skills/directory-submissions in your project.
Going by SKILL.md and its folder, Directory Submissions needs the command-line tools its instructions call (curl).
SKILL.md names 1 domain. In commands or code: directory.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Directory Submissions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.3k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Directory Submissions: SEO Dataforseo (AgriciDaniel/codex-seo, 791 stars), DataForSEO Live SEO Data (AgriciDaniel/claude-seo, 18k stars), Global SEO Growth (minhnv0807/ai-business-skills, 608 stars) and AI SEO (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
coreyhaines31 (a GitHub user) maintains it in coreyhaines31/marketingskills, which has 53,618 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.
Source: coreyhaines31/marketingskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.