- Rename skills/aso-audit/ directory to skills/aso/
- Update name field in frontmatter
- Update marketplace.json reference
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use when auditing an App Store or Google Play listing for optimization.
Triggers: "ASO audit", "app store optimization", "optimize my app listing",
"improve app visibility", "app store ranking", "audit my listing", or when
user shares an App Store / Google Play URL and wants to improve it. Also
triggers on: "why aren't people downloading my app", "improve my app
conversion", "keyword optimization for app", "compare my app to competitors".
name: aso
description: "When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it."
metadata:
version: 1.0.0
---
@@ -90,14 +84,13 @@ work with what's available. Ask the user to paste missing fields if critical.
### Visual asset assessment
WebFetch cannot extract screenshot images or caption text. **Always use the
Playwright browser tool** to get visual data:
WebFetch cannot extract screenshot images or caption text. **Take a screenshot
of the listing page** to get visual data:
1. Navigate to the listing URL with `browser_navigate`
2. Take a full-page screenshot with `browser_take_screenshot`
3. Read the screenshot image to assess: icon, screenshot count, caption text,
1. Navigate to the listing URL and capture a full-page screenshot
description: Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
metadata:
version: 1.0.0
@@ -141,23 +141,3 @@ Depending on what the user needs, produce one of:
- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix
Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
---
## Task-Specific Questions
1. What platform are you building on (or considering)?
2. What stage is the community at? (Pre-launch, early, growing, established)
3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
4. Who is the ideal community member and what motivates them?
5. Do you have existing users or customers to seed from?
6. How much time can you dedicate to community management weekly?
---
## Related Skills
- **referral-program**: For structured referral and ambassador incentive programs
- **churn-prevention**: For retention strategies that complement community engagement
- **social-content**: For content creation across social platforms
- **customer-research**: For understanding your community members' needs and language
> **Note**: `/neverbounce-alternative`, `/zerobounce-alternative`, `/mailercheck-alternative`, `/mails-so-alternative`, `/millionverifier-alternative`, `/validity-alternative`, `/verifalia-alternative` already exist. `/hunter-io-list-verification` exists but is not an "alternative" page.
> **Recommendation**: Don't invest in data quality content — it's not product-adjacent enough to convert.
---
## Content Refreshes
> Separate section — tackle after new pages are built.
### Priority 1: Cannibalization Fixes
| Issue | Pages | Combined Imps | Fix |
|---|---|---|---|
| Email format (duplicate posts) | `/blog/format-of-email-address` (pos 11) + `/blog/format-of-an-email-address` (pos 16) | 122,049 | Merge into one canonical post, 301 the other |
| Email list cleaning (4 pages splitting queries) | `/blog/email-list-cleaning-services`, `/blog/email-list-cleaning-tools`, `/blog/best-email-list-cleaning-service`, `/use-cases/email-list-cleaning` | ~12,000 | Pick one winner, redirect the rest |
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Corey Haines