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

Quality

88%

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

75%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-structured playbook with exact commands, specs, dated protocols, and a validated workflow, backed by a real one-level-deep reference bundle. Its main weakness is redundancy — destination-page guidance and several rules appear multiple times, and time-sensitive 2026 details are spread across the body instead of consolidated, inflating token cost without adding guidance value.

Suggestions

Consolidate destination-page guidance: Rule 2 and the full "Destination Pages Strategy" section cover the same material — keep the rule as a one-line pointer and let the dedicated section (or a reference file) carry the detail.

Move time-sensitive facts (G2 paid-plan pricing and cutoff dates, the Feb 2026 Capterra/G2 acquisition, 2026 PH algorithm specifics) into a single dated section or reference file so stale details can be updated in one place.

Trim the triple-stated duplicate-content rule to a single authoritative statement (e.g., in Step 3) and remove the repeated H1/2.8× citation stats between Rule 1 and the GEO section.

DimensionReasoningScore

Conciseness

Mostly dense and non-obvious, but with real redundancy: destination pages are fully specified twice (Rule 2 and the "Destination Pages Strategy" section), the no-duplicate-descriptions rule is stated three times (Rule 3, Step 3 "Critical", What NOT to Do #9), and time-sensitive 2026 facts (G2 pricing, Capterra acquisition date, PH algorithm details) are woven through the body rather than isolated, which the guidelines penalize.

3 / 5

Actionability

Fully executable guidance throughout: exact commands ("curl -sIL https://directory.com/your-listing | grep -i rel="), precise specs (1270×760 gallery images, 1920×1080 screenshots, 60–90s video), dated timelines (Day -21 to launch day), the 10-in-30 review protocol, and a per-submission checklist — copy-paste ready for the common cases.

5 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced with a genuine validation gate (the 9-question readiness assessment with hard/soft blocks) and per-submission verification (backlink dofollow check, tracker logging), satisfying the batch-operation validation requirement. It falls short of a 5 because error-recovery loops are thin — what to do when a submission is rejected or the backlink is nofollow is only implied via "moderator notes" and "check quarterly".

4 / 5

Progressive Disclosure

Good structure scored against the actual bundle: the heavy catalog (directory-list.md, 477 lines), positioning variant library, and tracker CSV are all correctly split into one-level-deep, clearly signaled reference files that exist and are cited at the right points. Kept at 4 because the body still carries substantial separable playbook material (PH deep dive, reviews, GEO, community sections, ~375 lines) inline with some overlap against the references.

4 / 5

Total

16

/

20

Passed

Description

95%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: concrete what, explicit when, exhaustive natural trigger phrases including platform names, and explicit boundary markers against sibling skills. The only gap is that it describes the submission action and its targets rather than enumerating the skill's internal workflow steps, which keeps specificity just below the top anchor.

DimensionReasoningScore

Specificity

Names the domain and concrete actions with explicit outcomes ("submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery") plus named platforms, but the action set is essentially one verb (submit) rather than the multiple distinct actions a level-5 anchor expects.

4 / 5

Completeness

Explicitly answers both what ("submit their product to ... directories for backlinks, domain rating, and discovery") and when ("Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign", plus a long quoted trigger list), in third-person voice.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with 18+ phrases users would actually say — "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "G2 listing," "Capterra listing," "dofollow backlinks," "directory tracker" — including platform names and synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear niche (directory submissions) with distinct triggers, and it actively disambiguates from adjacent skills ("For the broader launch moment, see launch. For programmatic SEO pages ... see programmatic-seo. For AI citation optimization, see ai-seo."), minimizing wrong-skill activation.

5 / 5

Total

19

/

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

joshmanders/dotfiles

Path

claude/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.