devtool directory submission checklist

TL;DR

Before submitting a devtool to any directory, assemble the full kit: a one-line description, a longer paragraph, the canonical URL, a logo, two or three screenshots, docs links, pricing info, and the right category. Most rejections come from incomplete kits, not bad tools, so run the checklist per directory and fill the gaps before you submit.

devtool directory submission checklist

Use this when

• Preparing a directory submission batch
• A submission was rejected as incomplete
• Briefing someone else to do submissions

Not for this skill when

• The tool is pre-launch with no docs (wait)
• The directory is irrelevant to your audience (skip it)
• You are bulk-submitting without reading each directory's rules

Steps

1. Write the one-liner. One sentence: what the tool does and for whom. This is the most reused asset in the kit. Expected: a sentence you would not be embarrassed to see quoted.

1. Write the long description. Two to three short paragraphs: problem, how it works, who it is for. No jargon stacking. Expected: a non-user understands the tool after reading it.

1. Gather links. Canonical homepage URL, docs URL, and one standout resource (quickstart or demo). Use the same canonical URL everywhere. Expected: three URLs, all live.

1. Prepare visuals. Logo in the directory's required format, plus two or three screenshots showing the tool doing its main job. Expected: files sized to the directory's specs.

submission kit:
  one-liner:        [sentence]
  description:      [2-3 paragraphs]
  urls:             homepage, docs, quickstart
  visuals:          logo, 2-3 screenshots
  category:         [best fit]
  pricing:          [free/paid/freemium]
  contact:          [maintainer contact]

1. Pick the category before submitting. Browse the directory's taxonomy and choose the closest fit; wrong categories get rejected or buried. Expected: a category you can defend.

1. Submit and log it. Record the directory, date, URL submitted, and status. Expected: the submission is trackable from day one.

Variant phrasings

what do I need to submit to a software directory

One-liner, description, links, logo, screenshots, category, pricing, contact.

directory listing submission requirements

Every directory wants the same kit with different formatting; assemble once, adapt per directory.

preparing a devtool for directory listings

Docs live, visuals ready, copy written, category chosen, then submit.

Why it happens

Directory maintainers triage fast and reject incomplete submissions faster. A complete kit signals a maintained tool, which is what they want to list; a half-empty form signals future link rot, which is what they are trying to avoid.

Edge cases / pitfalls

• Some directories require the tool to be open source or have a free tier; check before writing copy.
• Logo format requirements vary wildly; keep SVG and PNG versions ready.
• Never submit a staging or non-public URL; it will be rejected and remembered.
• If the directory has an approval queue, note the expected wait so you do not double-submit.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nwRcu-dzdKeJAGk3iXcxzA