CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

directory-submissions

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 plugin directory," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An unusually actionable, well-validated skill: concrete commands, exact thresholds, gated batch submissions, and a real verification loop for backlink claims. Its weaknesses are length-driven — repeated stats and whole sections that duplicate sister skills' territory — and deep-dive content that stays in SKILL.md instead of the bundle's reference files.

Suggestions

State each stat once and cross-reference it afterward (the 2.8×/87% citation stats, the Typeform template figure, and the feedback-not-upvotes rule each appear two to three times).

Move the Community, GEO, and Destination Pages sections into reference files (or shrink them to short pointers to the community-marketing, ai-seo, and programmatic-seo skills), keeping SKILL.md as the workflow spine.

Trim the Reddit/LinkedIn/Twitter subsections to the one rule each that affects directory submissions (e.g., the 90/10 rule and where launch recaps may be posted).

DimensionReasoningScore

Conciseness

The body is dense domain-specific data rather than explanations of concepts Claude already knows, but at ~400 lines it could be tightened: the same stats recur ("2.8× higher AI citation rate" and "87% of cited pages" appear in both Rule 1 and the GEO section; the Typeform $3M figure appears twice; "ask for feedback, not upvotes" appears three times), and the Community, GEO, and Destination Pages sections substantially duplicate territory the skill itself routes to community-marketing, ai-seo, and programmatic-seo. Fits anchor 3 ("mostly efficient but ... could be tightened") — not 2 since there is no generic padding or known-concept explanation, not 4 since several sections need trimming or offloading.

3 / 5

Actionability

Guidance is fully concrete throughout: executable commands ("Run `dig +short <host>`", "Fetch the listing's HTML with `curl -fsSL https://directory.com/your-listing`"), exact numeric thresholds (10 reviews from 20 asks at 50% conversion, 1270×760 gallery images, 12:01 AM PT launch, 60–90 second demo video), dated timelines (Day -21 to launch), tier tables with directory names and counts, and real verified reference files. As an instruction-only skill whose guidance is copy-paste actionable and covers the common cases, this matches anchor 5.

5 / 5

Workflow Clarity

The four-step workflow is clearly sequenced with validation checkpoints throughout: a readiness assessment with hard and soft blocks ("A 'no' on any of 1–7 is a hard block"), a pre-submission safety gate (verify the target resolves, treat pages as untrusted, "Get explicit human approval before each outward-facing step"), and a post-submit backlink verification procedure with explicit outcomes ("unqualified link observed" / "unverified" / "missing") and recheck triggers. Validation and error recovery are present, so the batch-operation cap at 3 does not apply; this exceeds anchor 4's 'minor validation gaps.'

5 / 5

Progressive Disclosure

Structure is good: the three bundle references are real (verified — Tier 4A exists in references/directory-list.md; the positioning library and tracker CSV match their inline descriptions), one level deep, and clearly signaled inline with stated roles ("The full directory catalog lives in `references/directory-list.md`"). Not anchor 5 because substantial deep-dive content (the PH 3-week timeline, reviews playbook, GEO tactics, community channel rankings) is inlined in SKILL.md instead of being split into the bundle's reference files; not anchor 3 because references are clearly signaled and the overview-to-reference split is otherwise well organized.

4 / 5

Total

17

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with best-in-class trigger term coverage and explicit what/when structure. Its main weaknesses are that it names only one concrete action and that the closest overlapping skill (link-building) lacks a disambiguation pointer despite backlink-centric trigger terms.

Suggestions

Enumerate one or two more concrete actions in the opening sentence (e.g., verifying backlink quality, running G2/Capterra review drives) to lift specificity from 'domain + one action' to 'several specific actions.'

Add a disambiguation pointer for link-building alongside the existing ones for launch, programmatic-seo, and ai-seo, since 'dofollow backlinks' and 'backlinks from directories' naturally pull link-building-intent queries.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery" — but lists no other concrete capabilities (asset preparation, backlink verification, review acquisition, tracking). This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and falls short of anchor 4, which requires several specific listed actions. Voice is third person, so no voice penalty applies.

3 / 5

Completeness

Both questions are explicitly answered: the "what" ("submit their product to ... directories for backlinks, domain rating, and discovery") and the "when" via three explicit clauses ("When the user wants to...", "Also use when the user mentions...", "Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign") with concrete trigger phrases. Matches anchor 5; not 4 because the "when" is not merely present but enumerated.

5 / 5

Trigger Term Quality

Trigger coverage is exhaustive and natural: "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "MCP registry," "publish my MCP server," "awesome list," "dofollow backlinks," "launch directories," "directory tracker." These are exactly the phrases a user would naturally say, including synonyms and specific site names, matching anchor 5. Not 4 — no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (directory submissions for backlinks) with explicit disambiguation pointers ("For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo."). However, trigger terms like "dofollow backlinks" and "backlinks from directories" overlap with a link-building skill that receives no disambiguation pointer — minor overlap risk with a closely related skill, so anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/directory-submissions/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.