dev-tool-directory-listings

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# Developer Tool Directory Listings

## Overview

Developers discover tools through curated directories, GitHub awesome-lists, and recommendation threads. Unlike general business directories, developer directories are often community-maintained, have genuine editorial standards, and drive qualified traffic. Getting listed requires meeting quality bars and contributing authentically to these communities.

This skill covers identifying valuable directories, submitting effectively, and maintaining your presence over time.

## Understanding the Directory Landscape

### Types of Developer Directories

**GitHub Awesome Lists**
Community-curated lists organized by technology or category. Examples:
- awesome-python
- awesome-react
- awesome-selfhosted
- awesome-developer-tools

These have high credibility because they're community-vetted and contributions are public.

**Curated Directories**
Editorially maintained directories with submission processes:
- AlternativeTo
- Product Hunt (for launches)
- StackShare
- LibHunt
- ToolsForCreators

**Category-Specific Directories**
Niche directories for specific developer needs:
- NoCodeDevs (no-code tools)
- RemoteTools (remote work tools)
- DevHunt (dev tool launches)
- APIList (API directories)

**Package Registries**
If you have libraries, these are essential:
- npm (JavaScript)
- PyPI (Python)
- crates.io (Rust)
- Go packages
- Maven Central (Java)

### Which Directories Actually Matter

Not all directories drive value. Prioritize based on:

1. **Traffic quality**: Do developers you want actually use this?
2. **Domain authority**: Does a backlink help SEO?
3. **Maintenance**: Is the directory actively maintained?
4. **Competition**: Are similar tools listed?
5. **Referral tracking**: Can you measure actual visits?

**High-value directories to prioritize:**
- GitHub awesome-lists in your category
- StackShare
- AlternativeTo
- Product Hunt (for major launches)
- Category-specific directories with engaged communities

**Often low-value:**
- Generic "software directories"
- Abandoned lists with no recent updates
- Directories that accept anything
- Link farms disguised as directories

## GitHub Awesome-List Strategy

### Finding Relevant Awesome Lists

1. Search GitHub for "awesome-[your-category]"
2. Check the awesome-list curated directory: https://github.com/sindresorhus/awesome
3. Look for lists your competitors appear on
4. Find niche lists for specific use cases

### Submission Best Practices

Awesome lists have contribution guidelines. Follow them exactly.

**Before submitting:**
- Read the entire CONTRIBUTING.md
- Review recent accepted PRs for patterns
- Ensure your tool meets stated criteria
- Check if similar tools are already listed

**Submission PR structure:**
```markdown
Title: Add [Tool Name]

## Description
[Brief description of what your tool does]

## Why it belongs
[How it fits the list's criteria]

## Checklist
- [ ] Read the contribution guidelines
- [ ] Tool is actively maintained
- [ ] Description follows list format
- [ ] Placed in correct alphabetical order
```

**Common rejection reasons:**
- Not following contribution guidelines
- Tool doesn't fit list scope
- Description too promotional
- Tool not mature/stable enough
- Missing required features for the category

### Contributing Beyond Self-Promotion

Build credibility by contributing value, not just listing your own tool:

- Fix broken links you notice
- Suggest improvements to list organization
- Add other quality tools you've used (not your own)
- Improve documentation

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills