mcpField
S
store-listing-optimizer

store-listing-optimizer

github.com/varnan-techMarketing & growth68739 installsUpdated 2w ago
Repository

About store-listing-optimizer

An ASO skill for rewriting App Store or Google Play listings from a product’s existing copy and a competitor complaint brief. It addresses competitor shortcomings only where the product has matching features, while following listing limits and output rules.

Key features

  1. 01Analyzes competitor broken promises
  2. 02Maps complaints to the product’s features
  3. 03Rewrites store listing copy
  4. 04Enforces title and subtitle limits
  5. 05Avoids competitor trademarks and invented features

Use cases

  1. 01Revise app store titles and subtitles
  2. 02Position a product against competitor complaints
  3. 03Turn a listing draft into store copy

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/varnan-tech/opendirectory --skill store-listing-optimizer

After installing, type/store-listing-optimizerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

.env.example
README.md
evals/
evals.json
evals/fixtures/
competitor_brief.md
current_listing.md
references/
aso-guidelines.md
output-schema.md
positioning-framework.md

Details

From the project README

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.

Comments

Markdown supported