Eleven Claude Skills Walk an App From Recon to Rival

Somewhere between the vibe-coding boom and the skills gold rush, a question started circulating in AI circles with increasing urgency — one Reddit thread in r/AI_Agents put it bluntly: if software is basically free to clone now, what actually matters? Jakeschincariol/replica-skill is a repo that takes that question not as a philosophical prompt but as a build specification. Its answer is a pipeline of eleven Claude skills that takes any app from reconnaissance to a deployed, rebranded competitor on your own domain.

The pitch is blunt enough to be disarming: “Eleven Claude skills that clone any app. Free, MIT, no signup, no API key, nothing to connect.” One skill reverse-engineers the target. One rebuilds it. One tests it. One — the so-called Entrepreneur — reads what the app’s users hate in real reviews and fixes those complaints in your version, so you end up with something you can actually sell. The rest plan the stack, rebuild the design system, wire auth and payments, score parity, name and brand the result, write the landing page, and ship it.

Strip away the swagger and what you have is a well-organized set of SKILL.md prompt files plus six small Python tools from the standard library. That is worth saying plainly: this is not a model, not a framework, not a service. It is a methodology encoded as instructions, with a handful of deterministic scripts doing the jobs where a language model’s judgment is least trustworthy — measuring, counting, and blocking. Whether that makes it trivial or clever depends on how much you value the methodology, and the methodology is where the interesting parts live.

The pipeline is the product

Each skill in the chain reads what the previous one wrote, into a shared replica/ folder in your project. Recon produces a map of screens, flows, components, and an inferred data model. Architect turns that into a stack plan and a database schema. Design measures screenshots into tokens. Build reconstructs the app screen by screen against the recon map, ticking off a features matrix as it goes. Test writes a plan from the discovered flows and logs bugs by severity. Diff scores the clone against the original. Then the commercial half of the pipeline takes over: Entrepreneur mines reviews for complaints, Brand renames and rebrands, Launch writes the store listing, Deploy runs a preflight and ships.

The README’s worked example — cloning a scheduling app — is more revealing than it first appears. Recon marks the target’s partner marketplace as out of scope, with the reasoning stated: “that is their network, not a feature.” That single line is the whole thesis of the repo compressed into a folder-level decision. The pipeline is constantly drawing a line between what an app does and what an app owns, and the line is drawn in the boring, structural places — scope decisions, feature matrices, parity scoring — rather than left to the model’s conscience at generation time.

This is the part worth taking seriously even if you never clone anything. The repo’s real insight is that agentic work benefits from being decomposed into stages with artifacts between them, where each stage can be inspected, scored, or blocked. The features matrix that Build ticks off and Diff scores against is a contract between stages. The bug log with severity thresholds is a gate. This is ordinary software engineering discipline, wearing an AI costume.

The tools that don’t trust the model

The six Python tools are where the author’s skepticism about LLMs shows. None touch the network. All are standard-library only, which reads as a deliberate statement: these are the checks that must not be fudgeable.

The layout differ reads PNGs with no external libraries, converts both screenshots to edge maps, and compares where things are rather than what color they are — so a rebrand doesn’t count against your parity score. The parity scorer weights must/should/could features, counts partial as half, and refuses to score things you deliberately left out or added; missing must-haves means “not shippable,” and it says so. The review analyzer drops every review without a link, marks themes with fewer than three reviews or a single source as thin, and prints quotes copied verbatim from rows you supplied. The brand sweeper searches your codebase for the original’s name, domain, and colors — including inside identifiers like OriginalAppEmbed — and blocks the deploy until it’s clean. The listing checker enforces App Store and Google Play limits and flags the original’s name anywhere in your copy.

Notice the pattern: every tool exists to prevent a specific flavor of model misbehavior. LLMs invent plausible-sounding review quotes, so every quote must carry a link. LLMs grade their own homework generously, so parity is computed by a script with fixed weights. LLMs leave the old name in a variable somewhere, so a sweeper greps for it. The tools are small, unglamorous, and exactly the right size for the job — which is more than can be said for a lot of the agent tooling currently raising venture money.

The guardrails are the story

The fine print section of the README is unusually long for a project with this much swagger in its headline, and it is clearly load-bearing. The repo claims a clean-room approach: it studies what an app does and how people move through it, then writes everything fresh — never the target’s source code, proprietary assets, logos, trademarks, copy, or private APIs. It reads only public pages and your own account, never scrapes behind a login or against a site’s terms, and never gets past a paywall. If your account’s terms forbid using it to build a competitor, the skill says so and sticks to public sources. And it always rebrands before launch — Deploy will not ship until the sweep comes back clean.

“Clone any app” turns out to mean “clone the features and the flow.” You can rebuild a music app’s player, playlists, and sharing. You cannot clone its catalogue. The repo is honest, too, about the ceiling: a booking tool is weeks of work; a spreadsheet engine is not happening. Recon sizes the difficulty before you start, and Diff gives a real number, not a vibe.

Whether these guardrails hold up in practice is a different question from whether they’re written down. The skills “enforce” the rules in the sense that prompt files instruct the model to enforce them, backed by the sweeper and the deploy gate for the mechanical parts. The judgment calls — what counts as a proprietary UX pattern versus a generic flow, whether a terms-of-service clause actually forbids what you’re doing — remain exactly where they were before: with a human who is explicitly told to run trademark checks and talk to a lawyer if money is on the line. The README says this is not legal advice, and it isn’t. Clean-room cloning has a long and respectable history in software, but it has always been a legal strategy executed by lawyers, not a vibe executed by a chatbot. This repo makes the honest version of that trade-off visible; it doesn’t make it disappear.

The moment it lands in

The repo arrives amid a genuine shift in what “cloning an app” costs. Replit’s Agent product page now leads with a testimonial from Reid Hoffman saying he asked it to clone LinkedIn “just to see how far it would get with a single prompt” and got “a surprisingly functional prototype” [11]. Taskade’s Genesis gallery advertises 50+ production-ready apps — dashboards, CRMs, booking systems — cloneable in one click, with average clone times under thirty seconds [8]. The functional moat, at least for the kind of software that is mostly forms and flows over a database, is draining fast. That is precisely the anxiety the blocked Reddit thread in r/AI_Agents was circling [5].

replica-skill differs from those platforms in a way that matters. Taskade’s clones are clones of Taskade’s own templates — a closed gallery, one click, no target of your choosing. Replit’s Agent builds from your description. Replica builds from an existing app, in the wild, and — this is the genuinely novel bit — aims the output at that app’s weakest flank. The Entrepreneur skill is the repo’s most original contribution. Reading 140 real reviews across the App Store, G2, Capterra, and Reddit, extracting the top complaints with counts and linked quotes, and converting them into a fix plan and a positioning angle — “booking links for small teams that hate per-seat pricing” — is competitive analysis as a pipeline stage. Most clone efforts reproduce the original faithfully and then wonder why anyone would switch. This one is designed to make the clone better than the original at the thing users complain about, which is the only reason a clone ever wins.

The skills format itself is having a moment. Anthropic’s Agent Skills concept has been picked up across the ecosystem: Replicate maintains a collection of skills for building AI-powered apps with its platform [3], and community aggregators like Jeffallan’s claude-skills repo — 67 specialized skills across 12 categories, sitting at 11.7k stars [1] — have turned skill authoring into its own genre. YouTube reviewers are churning through them by the dozen [10], and there’s at least one YouTube walkthrough of this very repo making the rounds [2]. The format’s appeal is structural: a skill is a folder of instructions and optional scripts that a capable model can pick up and run, no fine-tuning, no API, no vendor lock. Replica exploits that portability to an almost cheeky degree — the README notes you can paste a single SKILL.md into any chat and it runs as a mode, losing the Python tools but keeping the method.

What it doesn’t do

For all the pipeline’s discipline, the hard problems are still outside it. It doesn’t solve the legal question of whether your clone infringes anything — it defers to trademark checks and lawyers. It doesn’t handle apps whose value is a network, a dataset, or a physics engine; it sizes those honestly and declines. It doesn’t guarantee the clone works, only that it’s been tested and scored. And the whole edifice rests on the model actually following the SKILL.md instructions, which is a probabilistic foundation for a system whose selling point is enforcement. The deterministic tools cover the most failure-prone checks, but the recon, the build, and the judgment calls are still vibes with a rubric.

There’s also a fair reading of this repo as a thought experiment that happens to run. Eleven skills that walk from recon to deploy, with an Entrepreneur stage that turns user resentment into a business plan, is almost too neat a demonstration of the question everyone is asking. If the answer to “what actually matters” is not the code, not the design, and not the features — all cloneable now — then what’s left is the network, the data, the brand, and the users who already hate you. Replica-skill can’t give you any of those. It can give you a clean-room copy of everything else, a parity score, and a list of the original’s customers’ favorite complaints. Whether that’s a business or a party trick depends entirely on the app you point it at.