Dev Tool Directory Listings
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 asked about: - Developer tool directories - Awesome list submissions - Getting listed on dev resources - Directory submission strategy - Curated list contributions - Tool discovery platforms
Install
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listingsgit clone --depth 1 https://github.com/jonathimer/devmarketing-skills.git /tmp/devmarketing-skills
mkdir -p ~/.claude/skills
cp -r /tmp/devmarketing-skills/skills/dev-tool-directory-listings ~/.claude/skills/dev-tool-directory-listingsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
dev-tool-directory-listings- Repository
- jonathimer/devmarketing-skills
- Path
skills/dev-tool-directory-listings/SKILL.md- License
- MIT
- Repo updated
- 3 March 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Dev Tool Directory Listings skill do?
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 asked about: - Developer tool directories - Awesome list submissions - Getting listed on dev resources - Directory submission strategy - Curated list contributions - Tool discovery platforms
How do I install the Dev Tool Directory Listings skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Dev Tool Directory Listings popular?
It lives in jonathimer/devmarketing-skills, which has 88 GitHub stars and 6 forks, and is included in 1 curated skill list.
Related skills
Alternatives Pages
88jonathimer/devmarketing-skills
Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor comparison", "competitive content", "comparison table", "migration guide", "switch from [competitor]", "compare to [competitor]", "alternative to
API Onboarding
88jonathimer/devmarketing-skills
Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: "API onboarding", "time to first API call", "TTFAC", "developer onboarding", "first API call", "auth simplification", "sandbox environment", "interactive docs", "try it now", "API playground", "developer activation", "onboarding friction
Changelog Updates
88jonathimer/devmarketing-skills
Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog", "release notes", "product updates", "version communication", "breaking changes", "deprecation notice", "what's new", "release communication", "developer updates", "API versioning", "migration announcement
Developer Advocacy
88jonathimer/devmarketing-skills
When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public," "technical speaking," or "dev evangelism.
Detecting Typosquatting Packages in Npm Pypi
100adriannoes/awesome-agentic-ai
Detects typosquatting attacks in npm and PyPI package registries by analyzing package name similarity using Levenshtein distance and other string metrics, examining publish date heuristics to identify recently created packages mimicking established ones, and flagging download count anomalies where suspicious packages have disproportionately low usage compared to their legitimate targets. The analyst queries the PyPI JSON API and npm registry API to gather package metadata for automated comparison. Activates for requests involving package typosquatting detection, dependency confusion analysis,
Developer Audience Context
88jonathimer/devmarketing-skills
When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer profile," "ICP," or "ideal customer profile.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.