CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

directory-submissions

When the user wants to submit their product to startup, SaaS, AI, or review directories for backlinks, domain rating, and discovery.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/directory-submissions/SKILL.md

The canonical home for this skill is directory-submissions in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly actionable body: concrete commands, exact specs, timelines, and a validated readiness-first workflow, with real one-level-deep reference files for the bulk catalogs. Its one weakness is length — the GEO, destination-pages, and community sections push well past the directory-submission core and would be tighter as reference files.

Suggestions

Move the 'Community & Ongoing Distribution' and 'GEO' sections into reference files (e.g., references/community-distribution.md, references/geo-tactics.md), keeping only a few-line summary plus pointers in SKILL.md.

Trim the 'Destination Pages Strategy' section to a checklist and defer the detailed page patterns to the related programmatic-seo/competitor-alternatives skills it already names.

Consolidate the many inline statistics into the reference files where they support the claim, leaving the actionable rule in the body.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious specifics (PH algorithm behavior, G2 pricing and cutoff dates, tier catalogs) with little generic explanation of concepts Claude already knows, but at ~370 lines it includes whole sections — 'Community & Ongoing Distribution', 'GEO', 'Destination Pages Strategy' — that stretch beyond directory submissions and could be tightened or moved to reference files. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim-only anchor.

3 / 5

Actionability

Guidance is fully executable throughout: an exact verification command (`curl -sIL https://directory.com/your-listing | grep -i rel=`), precise asset specs (1024x1024 logos, 1270x760 gallery images, 260-char descriptions), a day-by-day 3-week Product Hunt timeline, the 10-in-30 review protocol, and concrete KPI targets. Copy-paste-ready instructions cover the common cases.

5 / 5

Workflow Clarity

A clear 4-step workflow with explicit validation checkpoints: the 9-question readiness assessment distinguishing hard blocks (1-7) from soft blocks (8-9), per-submission logging, dofollow backlink verification, and weekly KPI review with an 'if a number isn't moving, investigate' feedback loop. The batch-submission operation is well validated, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

Three real, one-level-deep reference files (directory-list.md, positioning-variations.md, submission-tracker-template.csv) are clearly introduced with their purpose and re-cited at point of use in the workflow and output sections. Minor gap: large inline sections (Product Hunt deep dive, reviews playbook, community distribution) carry content that could be split into reference files, keeping the anchor at 'good structure; most content appropriately placed' rather than fully optimal splitting.

4 / 5

Total

17

/

20

Passed

Description

70%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 focused, well-targeted description with explicit trigger guidance and natural directory/backlink vocabulary. Its main weakness is that the capability statement is thin — it covers the trigger well but only names one action, leaving the skill's broader workflows (readiness checks, positioning variants, review campaigns) undescribed.

Suggestions

Add a leading capability statement before the 'When...' clause, e.g., 'Assesses launch readiness, prepares per-directory positioning variants, plans Product Hunt launches, and drives G2/Capterra review campaigns.'

Include more natural trigger variations such as 'list my product/tool', 'get backlinks', or specific directory names (Product Hunt, G2) that users are likely to say.

Mention the output users get (a tiered submission plan and tracker) so the 'what' is concrete rather than implied.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — 'submit their product to startup, SaaS, AI, or review directories for backlinks, domain rating, and discovery' — but it does not list the skill's multiple distinct capabilities (readiness assessment, positioning variants, review generation, launch planning), matching the 'names domain and 1-2 concrete actions' anchor rather than the 'lists several specific actions' anchor.

3 / 5

Completeness

Explicit trigger guidance is present ('When the user wants to...') and the 'what' is embedded in the same clause (submit product to directories for backlinks, domain rating, discovery), so both what and when are answered. However, the 'what' could be more explicit and comprehensive — the readiness assessment, positioning, and review workflows are not hinted at — matching the anchor where both exist but 'when' or 'what' could be more specific.

4 / 5

Trigger Term Quality

Natural user phrasings are present — 'submit their product', 'startup, SaaS, AI, or review directories', 'backlinks', 'domain rating' — giving good keyword coverage. A few natural terms are missing (e.g., 'list my product/tool', specific directories like Product Hunt or G2), so it falls short of the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Directory submissions is a clear niche with distinct triggers ('directories for backlinks, domain rating'), so it is mostly distinct with only minor overlap risk against adjacent SEO/backlink/marketing skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-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.