Name: directory-submissions
Rating: 59.2 (1 reviews)
Author: administrakt0r

directory-submissions

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

67%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 a well-structured, highly actionable directory-submission playbook with concrete steps, validation gates, and well-signaled bundle references. Its main weaknesses are length/verbosity and scope creep beyond core directory submission into adjacent community marketing.

Suggestions

Move the Product Hunt deep dive, Reviews playbook, and Community & Ongoing Distribution sections into separate reference files to tighten the main SKILL.md overview and lift progressive_disclosure.

Trim explanatory prose (Core Philosophy, GEO concept definitions) that re-states what Claude already knows about SEO/link equity.

Tighten the 'What NOT to Do' list (12 items) by merging near-duplicates so the section reads as a concise checklist rather than padded prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly valuable domain-specific guidance, but at ~370 lines it includes explanatory prose (Core Philosophy, GEO concept explanations) and scope creep into community channels (Reddit, LinkedIn, Twitter) that could be trimmed without losing actionable value.	3 / 5
Actionability	Highly concrete guidance throughout — a 9-question readiness checklist, tier tables with named directories, a day-by-day PH timeline, the 10-in-30 protocol, KPI tables, and an executable verification command (`curl -sIL ... \| grep -i rel=`) — with only minor gaps where the actual positioning copy is deferred to references.	4 / 5
Workflow Clarity	Clear four-step workflow with an explicit readiness gate (hard/soft blocks), post-submission backlink verification, and KPI-based feedback loop; validation is present for the batch operation so the destructive/batch cap does not apply, though some error-recovery loops are implicit rather than spelled out.	4 / 5
Progressive Disclosure	Three real one-level-deep reference files (directory-list.md, positioning-variations.md, submission-tracker-template.csv) are well-signaled inline, but the main SKILL.md inlines heavy sections (PH deep dive, reviews playbook, GEO, community) that could be split into references for a cleaner overview.	4 / 5
	Total	15 / 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.

The description uses third-person voice and clearly communicates both what the skill does and when to invoke it, with strong trigger keywords and a distinct niche. It loses points for limited action variety and a when-clause that restates the action rather than supplying independent trigger phrases.

Suggestions

Add one or two more concrete actions beyond 'submit' (e.g., 'prepare positioning variants, track submission status, verify dofollow backlinks') to lift specificity.

Separate the 'when' trigger from the 'what' action with distinct natural phrasings users would say (e.g., 'Use when the user wants to list their product on Product Hunt, BetaList, or AI/SaaS directories').

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("submit their product to startup, SaaS, AI, or review directories") plus outcomes (backlinks, domain rating, discovery), but does not enumerate multiple distinct actions, so it sits at the domain-plus-1-2-actions level rather than comprehensive coverage.	3 / 5
Completeness	Explicitly opens with a "When the user wants to..." trigger clause and states a clear "what" (submit to directories for backlinks/DR/discovery), but the when-clause largely restates the action rather than giving distinct concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural user phrasings ("submit their product", "directories", "backlinks", "domain rating") and concrete directory-type keywords (startup, SaaS, AI, review), though a few natural synonyms (e.g. "list my product", specific site names) are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (directory submissions for distribution/SEO) with minor overlap risk against related marketing skills such as launch-strategy or programmatic-seo.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/skills/directory-submissions/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.