dev-tool-directory-listings

Name: dev-tool-directory-listings
Author: jonathimer

70installs6forks

How to install dev-tool-directory-listings?

jonathimer/devmarketing-skills/dev-tool-directory-listings

$npx -y skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings

Installs into the current project.

Summary

Getting listed on developer tool directories, awesome lists, and curated resources. Covers which directories matter for developer tools, submission best practices, contributing to awesome-lists on GitHub, maintaining listings over time, and tracking referral traffic. Use when ask

Files · 1

View on GitHub

SKILL.md

1	# Developer Tool Directory Listings
2
3	## Overview
4
5	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.
6
7	This skill covers identifying valuable directories, submitting effectively, and maintaining your presence over time.
8
9	## Understanding the Directory Landscape
10
11	### Types of Developer Directories
12
13	GitHub Awesome Lists
14	Community-curated lists organized by technology or category. Examples:
15	- awesome-python
16	- awesome-react
17	- awesome-selfhosted
18	- awesome-developer-tools
19
20	These have high credibility because they're community-vetted and contributions are public.
21
22	Curated Directories
23	Editorially maintained directories with submission processes:
24	- AlternativeTo
25	- Product Hunt (for launches)
26	- StackShare
27	- LibHunt
28	- ToolsForCreators
29
30	Category-Specific Directories
31	Niche directories for specific developer needs:
32	- NoCodeDevs (no-code tools)
33	- RemoteTools (remote work tools)
34	- DevHunt (dev tool launches)
35	- APIList (API directories)
36
37	Package Registries
38	If you have libraries, these are essential:
39	- npm (JavaScript)
40	- PyPI (Python)
41	- crates.io (Rust)
42	- Go packages
43	- Maven Central (Java)
44
45	### Which Directories Actually Matter
46
47	Not all directories drive value. Prioritize based on:
48
49	1. Traffic quality: Do developers you want actually use this?
50	2. Domain authority: Does a backlink help SEO?
51	3. Maintenance: Is the directory actively maintained?
52	4. Competition: Are similar tools listed?
53	5. Referral tracking: Can you measure actual visits?
54
55	High-value directories to prioritize:
56	- GitHub awesome-lists in your category
57	- StackShare
58	- AlternativeTo
59	- Product Hunt (for major launches)
60	- Category-specific directories with engaged communities
61
62	Often low-value:
63	- Generic "software directories"
64	- Abandoned lists with no recent updates
65	- Directories that accept anything
66	- Link farms disguised as directories
67
68	## GitHub Awesome-List Strategy
69
70	### Finding Relevant Awesome Lists
71
72	1. Search GitHub for "awesome-[your-category]"
73	2. Check the awesome-list curated directory: https://github.com/sindresorhus/awesome
74	3. Look for lists your competitors appear on
75	4. Find niche lists for specific use cases
76
77	### Submission Best Practices
78
79	Awesome lists have contribution guidelines. Follow them exactly.
80
81	Before submitting:
82	- Read the entire CONTRIBUTING.md
83	- Review recent accepted PRs for patterns
84	- Ensure your tool meets stated criteria
85	- Check if similar tools are already listed
86
87	Submission PR structure:
88	```markdown
89	Title: Add [Tool Name]
90
91	## Description
92	[Brief description of what your tool does]
93
94	## Why it belongs
95	[How it fits the list's criteria]
96
97	## Checklist
98	- [ ] Read the contribution guidelines
99	- [ ] Tool is actively maintained
100	- [ ] Description follows list format
101	- [ ] Placed in correct alphabetical order
102	```
103
104	Common rejection reasons:
105	- Not following contribution guidelines
106	- Tool doesn't fit list scope
107	- Description too promotional
108	- Tool not mature/stable enough
109	- Missing required features for the category
110
111	### Contributing Beyond Self-Promotion
112
113	Build credibility by contributing value, not just listing your own tool:
114
115	- Fix broken links you notice
116	- Suggest improvements to list organization
117	- Add other quality tools you've used (not your own)
118	- Improve documentation
119
120	This builds reputation before you submit your own tool.
121
122	## Directory Submission Strategy
123
124	### Preparation Before Submitting
125
126	Ensure your presence is submission-ready:
127
128	1. Clear value proposition: Can someone understand what you do in one sentence?
129	2. Screenshots/demos: Visual proof of your tool working
130	3. Documentation: Enough to evaluate without signing up
131	4. Pricing clarity: Transparent about costs
132	5. Social proof: GitHub stars, user count, notable users
133
134	Asset preparation:
135	- Logo in multiple formats (SVG, PNG, various sizes)
136	- Screenshots at common dimensions
137	- Short description (50-100 words)
138	- Long description (200-300 words)
139	- Category keywords
140	- Comparison positioning
141
142	### Writing Directory Descriptions
143
144	Different approach than marketing copy:
145
146	Do:
147	- Lead with what the tool does, not why it's great
148	- Be specific about func

People who liked this also viewed

6 picks

Type

dev-tool-directory-listings

70installs6forks

View on GitHub

How to install dev-tool-directory-listings?

jonathimer/devmarketing-skills/dev-tool-directory-listings

$npx -y skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Tool Directory Listings
2
3	## Overview
4
5	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.
6
7	This skill covers identifying valuable directories, submitting effectively, and maintaining your presence over time.
8
9	## Understanding the Directory Landscape
10
11	### Types of Developer Directories
12
13	GitHub Awesome Lists
14	Community-curated lists organized by technology or category. Examples:
15	- awesome-python
16	- awesome-react
17	- awesome-selfhosted
18	- awesome-developer-tools
19
20	These have high credibility because they're community-vetted and contributions are public.
21
22	Curated Directories
23	Editorially maintained directories with submission processes:
24	- AlternativeTo
25	- Product Hunt (for launches)
26	- StackShare
27	- LibHunt
28	- ToolsForCreators
29
30	Category-Specific Directories
31	Niche directories for specific developer needs:
32	- NoCodeDevs (no-code tools)
33	- RemoteTools (remote work tools)
34	- DevHunt (dev tool launches)
35	- APIList (API directories)
36
37	Package Registries
38	If you have libraries, these are essential:
39	- npm (JavaScript)
40	- PyPI (Python)
41	- crates.io (Rust)
42	- Go packages
43	- Maven Central (Java)
44
45	### Which Directories Actually Matter
46
47	Not all directories drive value. Prioritize based on:
48
49	1. Traffic quality: Do developers you want actually use this?
50	2. Domain authority: Does a backlink help SEO?
51	3. Maintenance: Is the directory actively maintained?
52	4. Competition: Are similar tools listed?
53	5. Referral tracking: Can you measure actual visits?
54
55	High-value directories to prioritize:
56	- GitHub awesome-lists in your category
57	- StackShare
58	- AlternativeTo
59	- Product Hunt (for major launches)
60	- Category-specific directories with engaged communities
61
62	Often low-value:
63	- Generic "software directories"
64	- Abandoned lists with no recent updates
65	- Directories that accept anything
66	- Link farms disguised as directories
67
68	## GitHub Awesome-List Strategy
69
70	### Finding Relevant Awesome Lists
71
72	1. Search GitHub for "awesome-[your-category]"
73	2. Check the awesome-list curated directory: https://github.com/sindresorhus/awesome
74	3. Look for lists your competitors appear on
75	4. Find niche lists for specific use cases
76
77	### Submission Best Practices
78
79	Awesome lists have contribution guidelines. Follow them exactly.
80
81	Before submitting:
82	- Read the entire CONTRIBUTING.md
83	- Review recent accepted PRs for patterns
84	- Ensure your tool meets stated criteria
85	- Check if similar tools are already listed
86
87	Submission PR structure:
88	```markdown
89	Title: Add [Tool Name]
90
91	## Description
92	[Brief description of what your tool does]
93
94	## Why it belongs
95	[How it fits the list's criteria]
96
97	## Checklist
98	- [ ] Read the contribution guidelines
99	- [ ] Tool is actively maintained
100	- [ ] Description follows list format
101	- [ ] Placed in correct alphabetical order
102	```
103
104	Common rejection reasons:
105	- Not following contribution guidelines
106	- Tool doesn't fit list scope
107	- Description too promotional
108	- Tool not mature/stable enough
109	- Missing required features for the category
110
111	### Contributing Beyond Self-Promotion
112
113	Build credibility by contributing value, not just listing your own tool:
114
115	- Fix broken links you notice
116	- Suggest improvements to list organization
117	- Add other quality tools you've used (not your own)
118	- Improve documentation
119
120	This builds reputation before you submit your own tool.
121
122	## Directory Submission Strategy
123
124	### Preparation Before Submitting
125
126	Ensure your presence is submission-ready:
127
128	1. Clear value proposition: Can someone understand what you do in one sentence?
129	2. Screenshots/demos: Visual proof of your tool working
130	3. Documentation: Enough to evaluate without signing up
131	4. Pricing clarity: Transparent about costs
132	5. Social proof: GitHub stars, user count, notable users
133
134	Asset preparation:
135	- Logo in multiple formats (SVG, PNG, various sizes)
136	- Screenshots at common dimensions
137	- Short description (50-100 words)
138	- Long description (200-300 words)
139	- Category keywords
140	- Comparison positioning
141
142	### Writing Directory Descriptions
143
144	Different approach than marketing copy:
145
146	Do:
147	- Lead with what the tool does, not why it's great
148	- Be specific about func

People who liked this also viewed

6 picks

Type