CtrlK
BlogDocsLog inGet started
Tessl Logo

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," "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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The content is highly actionable with concrete checklists, timelines, commands, and KPI targets, and it practices good progressive disclosure by offloading bulk catalogs to real reference files. Its main weakness is conciseness — notable redundancy across sections inflates length without adding capability.

Suggestions

Consolidate the destination-pages guidance, which currently appears in both 'Rule 2' and the 'Destination Pages Strategy' section, into a single section that points to one detailed treatment.

Trim the 'What NOT to Do' list to items not already stated as rules elsewhere — several entries (don't ask for upvotes, don't duplicate descriptions, don't lie on comparison pages) restate earlier guidance verbatim.

Add an explicit corrective-action step to the dofollow verification (e.g., 'if the link is nofollow or missing, contact the directory editor or re-submit') to close the validation loop for this batch operation.

DimensionReasoningScore

Conciseness

Largely dense and stat-driven rather than padded with concepts Claude already knows, but at ~375 lines it includes redundancy — the 'What NOT to Do' list reiterates rules already stated (duplicate descriptions, lying on comparison pages, asking for upvotes) and destination-page guidance appears in two sections — so it could be tightened.

3 / 5

Actionability

Highly concrete and executable: tier tables with named directories and counts, a 9-question readiness checklist, a day-by-day 3-week PH prep timeline, the 10-in-30 review protocol with email/URL/incentive specifics, an executable dofollow check ('curl -sIL https://directory.com/your-listing | grep -i rel='), and KPI tables with Day 0/30/90 targets covering common cases.

5 / 5

Workflow Clarity

Clear multi-step workflow (readiness assessment → tier selection → asset variations → batch submit) with explicit checkpoints (hard vs soft block rules) and a backlink verification step, but for a batch submission operation the verification lacks an explicit corrective-action loop if the link is nofollow, leaving a minor validation gap.

4 / 5

Progressive Disclosure

SKILL.md functions as an overview with bulk material split into real, well-signaled one-level-deep bundle files — references/directory-list.md, references/positioning-variations.md, references/submission-tracker-template.csv — all confirmed to exist and referenced clearly in the body, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is comprehensive, concrete, and trigger-rich, clearly stating both what the skill does and when to use it with extensive natural phrases. It also proactively distinguishes itself from neighboring skills via explicit boundary routing.

DimensionReasoningScore

Specificity

Names the directory-submission domain and lists multiple concrete actions and outcomes — 'submit their product to ... directories,' 'build a compounding backlink + discovery foundation,' 'in the right order, with the right positioning' — across many directory categories, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (submit to directories for backlinks, domain rating, and discovery; build a compounding foundation) and 'when' ('Use when the user mentions...' with concrete triggers and 'Use this whenever someone is planning the directory layer of a product launch'), matching the both-what-and-when-with-concrete-triggers anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and product names — 'directory submissions,' 'submit to directories,' 'list my product,' 'submit to Product Hunt,' 'BetaList,' 'TAAFT,' 'Futurepedia,' 'G2 listing,' 'Capterra listing,' 'AlternativeTo,' 'SaaSHub,' 'MCP registry,' 'dofollow backlinks,' 'launch directories,' 'directory tracker.'

5 / 5

Distinctiveness Conflict Risk

Clear niche (directory submissions for backlinks) with distinct triggers and explicit boundary routing to sibling skills — 'For the broader launch moment, see launch,' 'see programmatic-seo,' 'see ai-seo' — minimizing overlap risk.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.