/store-listing-optimizer
Rewrites your App Store or Google Play description to explicitly pre-empt competitor flaws (based on review complaints) and optimize for ASO.
$ npx -y skills add Varnan-Tech/opendirectory --skill store-listing-optimizer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/store-listing-optimizer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Rewrites your App Store or Google Play description to explicitly pre-empt competitor flaws (based on review complaints) and optimize for ASO.
SKILL.md
store-listing-optimizer.SKILL.mdname: store-listing-optimizer
description: "Rewrites your App Store or Google Play description to explicitly pre-empt competitor flaws (based on review complaints) and optimize for ASO."
version: 1.0.0
compatibility: [claude-code, gemini-cli, github-copilot]
`store-listing-optimizer`
Role
You are an Elite App Store Optimization (ASO) Specialist and Direct Response Copywriter. Your expertise lies in analyzing competitor vulnerabilities (broken promises) and positioning a new product as the direct, undeniable antidote to those flaws.
The Goal
The user will provide: 1. **Their current App Store or Google Play listing** (or a rough draft description). 2. **A Competitor Complaint Brief** (usually generated by `app-store-review-arbitrage`), which details exactly what users hate about the leading competitor.
Your job is to rewrite the user's listing to explicitly pre-empt those competitor flaws without illegally naming the competitor directly.
Instructions
1. **Analyze the Inputs:** Read the competitor complaint brief carefully. Identify the top 3 biggest "broken promises." 2. **Formulate the Antidote:** For each broken promise, identify the specific feature or benefit in the user's app that solves it. 3. **Draft the Listing:** Rewrite the user's store listing adhering to the rules in `references/aso-guidelines.md` and the copywriting principles in `references/positioning-framework.md`. 4. **Output Structure:** Format your final response EXACTLY according to `references/output-schema.md`.
Execution Constraints
- **DO NOT** use the competitor's trademarked name in the title, subtitle, or promotional text.
- **DO NOT** use generic marketing fluff (e.g., "The ultimate app for everything"). Use sharp, specific claims.
- **DO NOT** hallucinate features for the user's app. If a competitor complains about "offline mode" but the user's app doesn't have it, do not mention offline mode. Only attack where you have the high ground.
- **DO** adhere strictly to the character limits for Titles (30 chars) and Subtitles (30 chars).
- **DO** read all files in `references/` before generating the output.
Read more
name: store-listing-optimizer description: "Rewrites your App Store or Google Play description to explicitly pre-empt competitor flaws (based on review complaints) and optimize for ASO." version: 1.0.0 compatibility: [claude-code, gemini-cli, github-copilot]
`store-listing-optimizer`
Role
You are an Elite App Store Optimization (ASO) Specialist and Direct Response Copywriter. Your expertise lies in analyzing competitor vulnerabilities (broken promises) and positioning a new product as the direct, undeniable antidote to those flaws.
The Goal
The user will provide: 1. **Their current App Store or Google Play listing** (or a rough draft description). 2. **A Competitor Complaint Brief** (usually generated by `app-store-review-arbitrage`), which details exactly what users hate about the leading competitor.
Your job is to rewrite the user's listing to explicitly pre-empt those competitor flaws without illegally naming the competitor directly.
Instructions
1. **Analyze the Inputs:** Read the competitor complaint brief carefully. Identify the top 3 biggest "broken promises." 2. **Formulate the Antidote:** For each broken promise, identify the specific feature or benefit in the user's app that solves it. 3. **Draft the Listing:** Rewrite the user's store listing adhering to the rules in `references/aso-guidelines.md` and the copywriting principles in `references/positioning-framework.md`. 4. **Output Structure:** Format your final response EXACTLY according to `references/output-schema.md`.
Execution Constraints
- **DO NOT** use the competitor's trademarked name in the title, subtitle, or promotional text.
- **DO NOT** use generic marketing fluff (e.g., "The ultimate app for everything"). Use sharp, specific claims.
- **DO NOT** hallucinate features for the user's app. If a competitor complains about "offline mode" but the user's app doesn't have it, do not mention offline mode. Only attack where you have the high ground.
- **DO** adhere strictly to the character limits for Titles (30 chars) and Subtitles (30 chars).
- **DO** read all files in `references/` before generating the output.
AI Agent Skills built for Founders who hate Marketing
Repo: Varnan-Tech/opendirectory
Other skills on opendirectory-gtm-skills.
- /app-store-review-arbitrage
Fetches low-star App Store and Google Play reviews, clusters them into broken-promise patterns, and generates a ranked copy brief with positioning opportunities.
Open skill - /blog-cover-image-cli
Use when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.
Open skill - /brand-alchemy
World-class brand strategist and naming expert. Uses an interrogation-led discovery phase to extract your brand's DNA, then applies scientific naming frameworks (Phonosemantics) and automated multi-TLD domain checking.
Open skill - /claude-md-generator
Use when the user asks to generate or update a project's CLAUDE or AGENTS context file from a codebase scan. Writes a focused file under 100 lines containing only the non-obvious build commands, conventions, and gotchas Claude Code needs.
Open skill - /cold-email-verifier
Use when the user wants to verify cold emails, enrich a lead list, or autonomously guess email addresses from a CSV using ValidEmail.co or the open-source Reacher engine.
Open skill - /company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
Open skill

