Run any Skill in Manus with one click

$pwd:

store-listing-optimizer

Name: Store Listing Optimizer
Author: Varnan-Tech

// Rewrites your App Store or Google Play description to explicitly pre-empt competitor flaws (based on review complaints) and optimize for ASO.

Run Skill in Manus

$ git log --oneline --stat

stars:399

forks:45

updated:May 21, 2026 at 11:49

File Explorer

9 files

SKILL.md

readonly

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:

Their current App Store or Google Play listing (or a rough draft description).
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

Analyze the Inputs: Read the competitor complaint brief carefully. Identify the top 3 biggest "broken promises."
Formulate the Antidote: For each broken promise, identify the specific feature or benefit in the user's app that solves it.
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.
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.

related-skills.json

same repository

dx-roaster.md

from "Varnan-Tech/opendirectory"

Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked by impact × effort, and sketches an ideal README. Trigger when user says "roast my repo", "audit my README", "dx audit", "developer experience review", "score my GitHub project", "before launch checklist", or "make my repo shareable".

2026-05-30399

company-radar.md

from "Varnan-Tech/opendirectory"

Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.

2026-05-29399

app-store-review-arbitrage.md

from "Varnan-Tech/opendirectory"

Fetches low-star App Store and Google Play reviews, clusters them into broken-promise patterns, and generates a ranked copy brief with positioning opportunities.

2026-05-23399

blog-cover-generator.md

from "Varnan-Tech/opendirectory"

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.

2026-05-22399

twitter-gtm-find-skill.md

from "Varnan-Tech/opendirectory"

End-to-end pipeline for scraping X/Twitter for GTM/DevRel tech startup jobs using Apify, or optionally TweetClaw for OpenClaw and Hermes Tweet for Hermes Agent, then validating them against an Ideal Customer Profile (ICP) using Gemini's native Google Search Grounding. Use this skill when OpenClaw needs to find developer-first, funded startups actively hiring for GTM, DevRel, or Growth roles.

2026-05-20399

github-discussion-to-devrel-content.md

from "Varnan-Tech/opendirectory"

Find recurring confusion in your repo's GitHub Discussions, rank it by urgency, and draft the actual docs fixes and content angles — with verbatim community quotes and source links as evidence.

2026-05-18399

package.json

"author": "Varnan-Tech"

"repository": "Varnan-Tech/opendirectory"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations13-1161L4

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

The Goal

The user will provide:

Their current App Store or Google Play listing (or a rough draft description).
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

Analyze the Inputs: Read the competitor complaint brief carefully. Identify the top 3 biggest "broken promises."
Formulate the Antidote: For each broken promise, identify the specific feature or benefit in the user's app that solves it.
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.
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.

store-listing-optimizer

store-listing-optimizer

Role

The Goal

Instructions

Execution Constraints

More from this repository

More from this repository

store-listing-optimizer

Role

The Goal

Instructions

Execution Constraints

`store-listing-optimizer`

`store-listing-optimizer`