replica-entrepreneur
Skill399 starsChanged 41 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- realtahailyas/reverse-engineer-app-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- realtahailyas/reverse-engineer-app-skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- replica-architectSkill
- replica-backendSkill
- replica-brandSkill
- replica-buildSkill
- replica-deploySkill
- replica-designSkill
- replica-diffSkill
- replica-launchSkill
- replica-reconSkill
- replica-testSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Never fabricate: No invented reviews, quotes, ratings, counts, users or sources.
- Distinctive: line 32
Reading, not scraping: Read review pages the way a person does, in the browser, and copy rows into the sheet.
- Distinctive: line 39
No fake reviews, ever: Not for your app, not against theirs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdThe 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.mdIt 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.