replica-entrepreneur
Researches the app being cloned and reads what its real users say in public reviews (App Store, Google Play, G2, Capterra, Trustpilot, Reddit, Hacker News, its own feature-request board), then ranks what they hate, what is missing and what is unsolved, turns it into a fix plan for the clone and a positioning angle you can sell. Every quote is real, verbatim and linked. Use when the user says "what do people hate about X", "read the reviews", "how do I make mine better", "find the gap", "what features are missing", "how do I position this", "make it sellable", or after /replica-diff.
- Installs
- 679
- Last 24h
- +42
- Trending rank
- #3703
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jakeschincariol/replica-skill --skill replica-entrepreneur- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads replica-entrepreneur automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
replica-entrepreneur
A straight copy of an app has no reason to exist. This skill finds the reason: what the original's users hate, in their own words, and fixes it in yours.
Tool in this folder:
python3 reviews.py replica/reviews.csv --out replica/feedback.md
The rules, which are not negotiable
- Never fabricate. No invented reviews, quotes, ratings, counts, users or sources. If a source cannot be reached, say so and move on. If there are 14 reviews, say 14.
- Every quote is verbatim and linked. Copied exactly from the page, with
the URL of the review or thread.
reviews.pydrops any row without a link. - Reading, not scraping. Read review pages the way a person does, in the
browser, and copy rows into the sheet. No scraping libraries against stores
or review sites whose terms forbid it. Official public feeds and APIs are
fine within their terms: Apple's customer reviews RSS feed
(
https://itunes.apple.com/us/rss/customerreviews/id=<APP_ID>/sortBy=mostRecent/json), the Hacker News Algolia API (hn.algolia.com/api/v1/search?query=...), Reddit's official API under its terms. - No fake reviews, ever. Not for your app, not against theirs. It is illegal in the US (the FTC's 2024 rule) and in many other places.
- Reviewers are not your testimonials. Their words are research. Do not put them on your landing page.
Step 1: collect
Aim for 100+ reviews across at least three sources, recent first:
| source | where |
|---|---|
| App Store | the app page, Ratings and Reviews, See All; or the RSS feed above |
| Google Play | the listing, See all reviews, sort by newest |
| G2, Capterra, Trustpilot | the product's review pages, filter to 1 to 3 stars too |
| search "X alternative", "switched from X", "X sucks", "X vs" | |
| Hacker News | the Algolia API or site search, same queries |
| the original's own board | its public roadmap or feature-request board (Canny and similar) and the vote counts |
| its changelog | what it shipped, so you do not "fix" what is already fixed |
Each row in replica/reviews.csv: source,url,date,rating,text, text copied
exactly. Read the 3 and 4 star reviews too. "Love it, but..." is where the
best fixes hide.
Step 2: rank
python3 reviews.py replica/reviews.csv --out replica/feedback.md
It sorts reviews into themes (themes.json, edit it for the app's category),
weights low ratings and recent reviews higher, marks themes with fewer than 3
reviews or only one source as thin, lists every request in the users' own
words, and surfaces low ratings that matched no theme. Read that last list by
hand. It is often the best part.
Step 3: three lists
From feedback.md, write three ranked lists. Each item: the problem in one
line, how many reviews, how many sources, one or two linked quotes.
- What they hate. Complaints about things the app does.
- What is missing. Features people ask for by name.
- What is unsolved. Whole jobs or groups the app ignores ("not built for teams", "useless for therapists"). These become positioning.
Thin themes are listed as thin. Do not present three angry Reddit comments as a trend.
Step 4: the fix plan
Pick the top 5 to 8 by evidence times how cheaply you can fix them. For each:
what to build or change, size (S, M, L), which skill does it, and the
evidence. Add each one to replica/features.csv as a row with original set
to no. Pricing and billing complaints go to /replica-launch.
Step 5: the angle
Three positioning options, each grounded in a top theme:
For {{who}} who {{hate this about the original, in plain words}},
{{your app}} {{does this instead}}.
Evidence: {{theme}}, {{n}} reviews across {{n}} sources.
Recommend one. It drives replica-brand's name and voice and replica-launch's hero. Do not put the original's name in your app name, ads or store listing. A factual comparison page is a legal question for a lawyer in your country.
Output
replica/reviews.csv, replica/feedback.md, replica/fixes.md (three
lists, fix plan, angle), new rows in features.csv, and a summary that
states the sample size. Next: /replica-brand.
FAQ
What does the replica-entrepreneur skill do?
Researches the app being cloned and reads what its real users say in public reviews (App Store, Google Play, G2, Capterra, Trustpilot, Reddit, Hacker News, its own feature-request board), then ranks what they hate, what is missing and what is unsolved, turns it into a fix plan for the clone and a positioning angle you can sell. Every quote is real, verbatim and linked. Use when the user says "what do people hate about X", "read the reviews", "how do I make mine better", "find the gap", "what features are missing", "how do I position this", "make it sellable", or after /replica-diff.
How do I install replica-entrepreneur?
Run npx skills add https://github.com/jakeschincariol/replica-skill --skill replica-entrepreneur in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/replica-entrepreneur/ (personal) or .claude/skills/replica-entrepreneur/ (project).
Which AI agents can use replica-entrepreneur?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is replica-entrepreneur safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains replica-entrepreneur?
It is published by jakeschincariol in jakeschincariol/replica-skill. It has 679 recorded installs.
More from jakeschincariol/replica-skill
replica-recon
jakeschincariol/replica-skill
Reverse-engineers any app into a recon map: screen inventory, user flows, component list, inferred data model and a feature matrix, from public pages, screenshots, app store listings, help docs and the user's own account. The first step of the Replica pack. Use when the user says "clone this app", "reverse engineer X", "how does X work", "map out X", "what screens does X have", "I want to build my own version of X", "copy this app", or pastes an app's URL or App Store link and wants to rebuild it.
replica-test
jakeschincariol/replica-skill
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
replica-design
jakeschincariol/replica-skill
Rebuilds an app's design system for a clone: colour roles, type scale, spacing, radius, shadows and every component with its states, as design tokens plus component specs, with original assets instead of the target's logos, icons, illustrations or licensed fonts. Includes a WCAG contrast checker. Use when the user says "match the design", "rebuild the design system", "get the colours and fonts", "make it look like X", "design tokens for my clone", or after /replica-architect.
replica-diff
jakeschincariol/replica-skill
Compares an app clone against the original: a feature parity score from the feature matrix (weighted by must, should, could) with the missing list in build order, plus a screenshot layout diff that ignores colour so a rebrand does not count against you. Two standard-library Python tools. Use when the user says "how close is my clone", "compare it to the original", "what's missing", "parity check", "diff the screens", "is it ready", or after /replica-test.
replica-build
jakeschincariol/replica-skill
Rebuilds an app screen by screen from the recon map: app shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix as it goes. Writes every line fresh, never the original's code, assets or copy. Use when the user says "build the clone", "build screen S07", "start building", "rebuild this screen", "implement the booking page", or after /replica-design.
replica-launch
jakeschincariol/replica-skill
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after /replica-brand.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.