dev-tool-directory-listings — скилл для Claude Code: суть и установка
Помогает подготовить описания и подать заявки в каталоги инструментов для разработчиков и списки awesome на GitHub. Пригодится при выводе нового dev-продукта на рынок.
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a claude-codeЧто делает dev-tool-directory-listings
Скилл содержит инструкции по отбору каталогов и подготовке заявок в курируемые списки вроде AlternativeTo, StackShare или DevHunt. Он объясняет, как находить профильные репозитории awesome на GitHub через sindresorhus/awesome, оформлять пулреквесты по правилам CONTRIBUTING.md и соблюдать алфавитный порядок в списках.
Внутри описаны правила подготовки ассетов: варианты логотипов в SVG и PNG, скриншоты интерфейса и тексты на 50–100 и 200–300 слов. Скилл запрещает рекламные формулировки без фактов и требует писать конкретно о функциях, поддерживаемых языках и платформах. Публичные каталоги строго модерируются, поэтому заявки со скрытыми ценами или без рабочей документации сразу получают отказ.
Также материал описывает ежеквартальный пересмотр ссылок, цен и скриншотов, отслеживание реферальных переходов и реакцию на отзывы без публичных споров.
Какие задачи решает
- составить заявку для добавления инструмента в awesome-список на GitHub
- подготовить краткие и развёрнутые описания продукта для AlternativeTo и StackShare
- отобрать профильные каталоги и отсеять неактивные списки
- оформить PR с соблюдением требований CONTRIBUTING.md
Примеры запросов агенту
- Подготовь текст пулреквеста для добавления нашего CLI-инструмента в awesome-python
- Напиши краткое описание для каталога DevHunt без рекламных штампов
- Составь чеклист ассетов и требований перед отправкой проекта в AlternativeTo
Как установить dev-tool-directory-listings
1Через Skills CLI (Vercel)
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a claude-code2Вручную: положить файлы
~/.claude/skills/dev-tool-directory-listings/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/dev-tool-directory-listings/
1Через Skills CLI (Vercel)
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a codex2Вручную: положить файлы
.agents/skills/dev-tool-directory-listings/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a cursor2Вручную: положить файлы
.cursor/skills/dev-tool-directory-listings/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install jonathimer/devmarketing-skills dev-tool-directory-listings2Вручную: положить файлы
.github/skills/dev-tool-directory-listings/SKILL.md1Через Skills CLI (Vercel)
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a gemini-cli2Командой платформы
gemini skills install https://github.com/jonathimer/devmarketing-skills --path skills/dev-tool-directory-listingsВручную: положить файлы
.devin/skills/dev-tool-directory-listings/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о dev-tool-directory-listings
Как установить dev-tool-directory-listings в Claude Code?
Выполните команду npx skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listings -a claude-code. Файл навыка сохранится по пути ~/.claude/skills/dev-tool-directory-listings/SKILL.md.
Что делает dev-tool-directory-listings?
Скилл даёт правила и шаблоны для публикации инструментов разработчика в курируемых каталогах и списках awesome на GitHub. Он помогает составить нерекламные описания и спланировать регулярное обновление профилей.
Почему awesome-списки отклоняют пулреквесты с новыми инструментами?
Отказ обычно происходит из-за нарушения CONTRIBUTING.md, сбитого алфавитного порядка или чересчур рекламного описания. Также кураторы отклоняют проекты без готовой документации и стабильных базовых функций.
Исходный текст
SKILL.md · MIT
---
name: dev-tool-directory-listings
description: |
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
metadata:
version: 1.0.0
---
# 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
This builds reputation before you submit your own tool.
## Directory Submission Strategy
### Preparation Before Submitting
**Ensure your presence is submission-ready:**
1. **Clear value proposition**: Can someone understand what you do in one sentence?
2. **Screenshots/demos**: Visual proof of your tool working
3. **Documentation**: Enough to evaluate without signing up
4. **Pricing clarity**: Transparent about costs
5. **Social proof**: GitHub stars, user count, notable users
**Asset preparation:**
- Logo in multiple formats (SVG, PNG, various sizes)
- Screenshots at common dimensions
- Short description (50-100 words)
- Long description (200-300 words)
- Category keywords
- Comparison positioning
### Writing Directory Descriptions
Different approach than marketing copy:
**Do:**
- Lead with what the tool does, not why it's great
- Be specific about functionality
- Mention key technical differentiators
- Include primary use cases
- Note programming language/platform compatibility
**Don't:**
- Use superlatives ("best," "revolutionary")
- Focus on company story
- Bury functionality under benefits
- Use jargon unexplained
- Copy-paste same description everywhere (duplicate content hurts SEO)
**Example transformation:**
*Marketing copy:*
> "The revolutionary platform that transforms how teams collaborate on code. Trusted by 10,000+ developers."
*Directory description:*
> "Real-time collaborative code editor supporting JavaScript, Python, and Go. Features include shared debugging sessions, integrated terminal, and Git sync. Self-hosted or cloud options available."
### Submission Timing
**For curated directories:**
- Submit when you have meaningful traction
- Wait until core features are stable
- Consider submitting after notable milestone (funding, major release)
**For Product Hunt:**
- Prepare launch thoroughly (separate skill)
- Coordinate with community building
- Time for when team can engage
## Maintaining Directory Presence
### Regular Maintenance
Directories require ongoing attention:
**Quarterly review:**
- Check all listings are accurate
- Update screenshots if UI changed
- Refresh descriptions for new features
- Ensure links work
- Update pricing if changed
**Monitoring:**
- Set up alerts for brand mentions in directories
- Track referral traffic from each source
- Note which directories drive signups
### Responding to Reviews
Many directories allow reviews or comments:
- Respond professionally to criticism
- Thank positive reviewers
- Use feedback to improve product
- Don't argue or get defensive
- Address legitimate concerns publicly
### Handling Outdated Listings
Over time, some listings become outdated:
- Update information when possible
- Request removal from abandoned directories (avoid bad SEO signals)
- Correct misinformation proactively
- Keep screenshots current
## Tracking Referral Value
### Setting Up Tracking
Track which directories actually drive value:
1. **UTM parameters**: Add tracking to directory URLs
2. **Referral reports**: Monitor Google Analytics referrers
3. **Signup attribution**: Ask "how did you hear about us"
4. **Backlink monitoring**: Track SEO value
### Metrics to Track
**Traffic metrics:**
- Visits from each directory
- Bounce rate from directory traffic
- Time on site from referrals
**Conversion metrics:**
- Signups attributed to directories
- Trial-to-paid conversion from directory traffic
- Revenue attributed to directory presence
**SEO metrics:**
- Domain authority of linking directories
- Referral traffic trends over time
### Evaluating Directory ROI
Not all directories warrant ongoing attention:
**Keep maintaining if:**
- Drives consistent qualified traffic
- High conversion rates
- Strong backlink value
- Community engagement
**Deprioritize if:**
- No measurable traffic
- Low-quality visits
- Directory appears abandoned
- No SEO value
## Budget and Resources
### Minimum Viable Approach
- **Time investment**: 2-4 hours for initial submissions
- **Ongoing**: 1-2 hours/quarter for maintenance
- **Cost**: Free (most directories don't charge)
### Scaled Approach
- Dedicated tracking for attribution
- Regular auditing of directory presence
- Proactive updates with product changes
- Contributing to community directories
## Tools
- **Google Analytics**: Referral traffic tracking
- **Ahrefs/Semrush**: Backlink monitoring and discovery
- **Notion/Spreadsheet**: Track all directory listings
- **Brand monitoring tools**: Alerts for new mentions
- **Octolens**: Discover where developers discuss and recommend tools in your category
## Common Mistakes
1. **Spamming low-quality directories**: Focus on quality over quantity
2. **Set and forget**: Listings need maintenance
3. **Identical descriptions everywhere**: Write unique descriptions
4. **Ignoring contribution guidelines**: Leads to rejection
5. **Self-promotion only**: Build reputation through genuine contributions
6. **Missing tracking**: Can't measure what matters
## Related Skills
- **developer-seo**: Directory listings support overall SEO strategy
- **github-community-engagement**: Contributing to awesome-lists fits broader GitHub strategy
- **product-hunt-launch**: Special considerations for Product Hunt specifically
© jonathimer · MIT · jonathimer/devmarketing-skills