Skip to content
Marketing
Skill

/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.

From plugin
opendirectory-gtm-skills
58364 skills
Install
$ npx -y skills add Varnan-Tech/opendirectory --skill store-listing-optimizer --agent claude-code

How 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.md
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.
Read more
Ships withopendirectory-gtm-skills

AI Agent Skills built for Founders who hate Marketing

Get the whole plugin