CtrlK
BlogDocsLog inGet started
Tessl Logo

directory-submissions

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

59

Quality

68%

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

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.

A thorough, actionable directory-submission playbook with clear sequencing, validation gates, and well-organized bundle references. Its main weakness is conciseness — significant redundancy across the rules, readiness, and "What NOT to Do" sections.

Suggestions

Consolidate the "What NOT to Do" section, which largely restates the Three Hard Rules and earlier guidance, into cross-references or a tight anti-pattern list.

Move the Community & Ongoing Distribution and GEO sections into a reference file so SKILL.md stays a lean overview pointing to details.

Dedupe repeated evidence (e.g., the Typeform 30K-signup/$3M-LTV example and the single-H1 2.8x citation stat each appear in multiple sections).

DimensionReasoningScore

Conciseness

Most content is high-value, non-obvious domain knowledge (PH algorithm, G2 cutoffs, tier lists), but it is noticeably redundant: "What NOT to Do" restates the Three Hard Rules, the readiness checklist re-lists Rule 1/2 items, and the Typeform template stat appears twice.

3 / 5

Actionability

Highly concrete guidance throughout — named directories, dated timelines (Day -21), review thresholds (10-in-30), cadences, and one executable command (`curl -sIL https://directory.com/your-listing | grep -i rel=`), with only minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

A clear 4-step workflow with a readiness-gate checklist that blocks on "no" and a post-submit backlink verification step provides the validation this batch operation requires; recovery loops for moderator rejections are thin, keeping it just below 5.

4 / 5

Progressive Disclosure

Three real, well-signaled one-level-deep references (directory-list.md, positioning-variations.md, submission-tracker-template.csv) are appropriately split from the overview, though sizable inline sections (Community, GEO) could be extracted to references.

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.

A concise, well-triggered description that clearly states when to use the skill and its domain, with solid natural keywords. It is held back by thin action specificity and minor overlap with adjacent marketing skills.

Suggestions

Add 1-2 more concrete actions beyond "submit" (e.g., prepare per-tier positioning variants, verify dofollow backlinks, log submissions in a tracker) to lift specificity.

Include one or two flagship directory names (e.g., Product Hunt, G2) as trigger terms so the description matches higher-intent user requests.

Tighten the what-clause into a short verb list ("Submit and track product listings across…") to make capabilities more concrete.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("submit their product to…directories") plus outcomes, but the listed benefits (backlinks, domain rating, discovery) are results rather than actions, so coverage is not comprehensive.

3 / 5

Completeness

Explicit "When the user wants to…" trigger guidance is present (so not capped at 3) and the what is stated, but the what is thin and could be more specific, landing between anchors 4 and 5.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present ("submit their product to startup, SaaS, AI, or review directories", "backlinks", "domain rating"), though specific high-intent names like Product Hunt or G2 are absent.

4 / 5

Distinctiveness Conflict Risk

Directory submissions is a clear niche with distinct triggers, but it overlaps with closely related marketing skills (launch-strategy, ai-seo) listed in the skill itself.

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.

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