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…
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .claude/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add Jakeschincariol/replica-skill --skill replica-recon -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .agents/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add Jakeschincariol/replica-skill --skill replica-recon -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .cursor/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add Jakeschincariol/replica-skill --skill replica-recon -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .gemini/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add Jakeschincariol/replica-skill --skill replica-recon -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .github/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add Jakeschincariol/replica-skill --skill replica-recon -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "replica-recon" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-recon into .opencode/skills/replica-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-recon", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
replica-recon
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
682 words
Files
3
Skills in repo
11
Repo updated
First seen
Licence
MIT
At a glance
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…
Works in 9 steps: scope → list the sources → screen inventory → …
The user says clone this app
SKILL.md covers The rules, before anything else, Step 1: scope, Step 2: list the sources and Step 3: screen inventory, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Replica Recon is an agent skill from 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `recon-map.md`).
It sits in Mobile, covering App store release and UX design. The repository describes itself as: Eleven free Claude skills that clone any app: reverse-engineer it, rebuild it, test it for bugs, then fix what its users hate. Free, MIT. The licence is MIT.
When your agent uses it
The user says clone this app
Reverse engineer X
How does X work
What screens does X have
Example prompts
“clone this app”
“reverse engineer X”
“how does X work”
“/replica-recon”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 77c9436. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Replica Recon loads about 1.4k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 682 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~129
When it runs· the whole SKILL.md, loaded when a task matches
~1.4k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/replica-recon/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
replica-recon
description
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-recon
Everything else in the pack builds from what this skill writes. A bad recon
map means a bad clone, so take the time here.
Output goes in the user's project:
replica/recon.md the recon map (template: recon-map.md in this folder)
replica/features.csv the feature matrix (template: features.csv in this folder)
replica/screens/ reference screenshots of the original. Never shipped.
The rules, before anything else
This skill rebuilds functionality and UX patterns, clean-room style. It
studies what the app does and how a user moves through it. It does not take
anything the app owns.
Public sources and the user's own account only. Never log into an
account that is not the user's, never ask for a password, never get past a
paywall or a login by any trick.
Reading, not scraping. No crawlers, no bulk downloads, no loops. If a
browser tool is connected to the user's own browser, read pages at human
speed with the user present.
No source code, no private APIs. Do not read or save the app's
JavaScript bundles, decompile its binary, or log its network calls to copy
endpoints. Public API docs are fine to read.
Check the terms. Some products' terms forbid using an account to build a
competing product. If the user's account is under terms like that, say so
and work from public sources only.
Screenshots are reference. They live in replica/screens/, are used to
compare layouts, and never go into the clone.
Step 1: scope
Ask three things, or propose answers and get a yes:
Which app, which platform. Web, iOS, Android, desktop.
Which slice. "All of Notion" is not a project. "Notion's pages, blocks
and sharing" is. Default to the core loop: the one flow users pay for.
Who it is for. The user's own business, a niche, a product to sell.
Step 2: list the sources
Build a sources table first, with a URL on every row. In order of value:
source
what it gives you
help center / docs
the most complete feature list there is, and the settings
pricing page
which features matter (they gate them)
changelog
what was added recently, what the team thinks is important
app store listing
screenshots of every key screen, the pitch, ratings
public walkthrough videos
real flows, click by click
marketing site
positioning, the core loop in their words
the user's own account
the real thing, every state, driven by the user
public API docs
the data model, almost for free
Show full SKILL.md (298 more words)Show less
Step 3: screen inventory
One row per screen. IDs are stable: S01, S02... Every other file refers to them.
ID | screen | route or how you get there | purpose | key components | states seen
States matter: empty, loading, filled, error, permission denied, mobile. An
empty state you did not record is an empty state you will not build.
Step 4: user flows
F01, F02... Each one is a goal and the screens it passes through:
F01 Guest books a meeting
S07 booking page -> S08 pick a time -> S09 details form -> S10 confirmed
edge: no slots this week, time zone differs, slot taken while filling the form
Count the clicks on the happy path. It becomes the number to beat.
Step 5: components
Every repeated UI part: buttons, inputs, date pickers, modals, tables, toasts,
nav. Name, variants, states, which screens use it. This becomes
replica-design's component list.
Step 6: inferred data model
Entities, fields and relationships, each with its evidence and a confidence:
Booking id, event_type_id, start_at, end_at, guest_name, guest_email,
status (confirmed | cancelled | rescheduled), answers (json)
evidence: S09 form fields, S10 confirmation, help article "Cancel a booking"
confidence: high
Mark guesses as guesses. replica-architect turns this into a real schema.
Step 7: feature matrix
Write replica/features.csv (columns: feature, area, priority, original,
clone, notes). Priority is must / should / could. clone starts at no for
every row and gets filled in during the build. replica-diff scores it.
Step 8: what cannot be cloned
List it honestly, as skip rows with a reason: licensed content (a music
catalogue, a stock library), the network and its users, data the app owns,
partner deals, hardware, regulated licences (banking, health). "Clone any
app" means the features and the flow, not what the app owns.
Step 9: size it
Screens, flows, entities, and the hard parts (realtime, sync, payments,
calendar or email integrations, offline). Give a size: S (a weekend), M (a
few weeks), L (a quarter), XL (rescope it). No promises of a perfect clone.
Output
replica/recon.md and replica/features.csv, then a five-line summary: the
core loop, screen and flow counts, the three hardest parts, what is out of
scope, and the next step: /replica-architect.
Replica Recon next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Replica Recon compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Replica Recon this skillJakeschincariol/replica-skill
A skill your agent uses when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing…
Builds an App Store App Preview video (and a Play Store or landing page promo cut) from a screen recording of the app, using the open-screenshot-generator CLI (osg video): it starts from one of 20…
Prevent UI freezes and ensure a responsive user experience by validating threading rules and migrating blocking calls off the Event Dispatch Thread (EDT).
Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide…
Ships an app clone live on the user's own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the…
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…
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…
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…
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…. Replica Recon is an agent skill from 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.
When should I use Replica Recon?
Replica Recon fits situations like: the user says clone this app; reverse engineer X; how does X work; what screens does X have.
How do I install Replica Recon in Claude Code?
Run `npx skills add Jakeschincariol/replica-skill --skill replica-recon -a claude-code`. Or copy the skill folder (replica-recon in Jakeschincariol/replica-skill) into .claude/skills/replica-recon in your project. Claude Code loads it when a task matches its description.
How do I install Replica Recon in Codex?
Run `npx skills add Jakeschincariol/replica-skill --skill replica-recon -a codex`. Or copy the skill folder (replica-recon in Jakeschincariol/replica-skill) into .agents/skills/replica-recon in your project. Codex loads it when a task matches its description.
Can I use Replica Recon in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/replica-skill --skill replica-recon -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/replica-recon, .gemini/skills/replica-recon, .github/skills/replica-recon and .opencode/skills/replica-recon in your project.
What does Replica Recon need to run?
SKILL.md names no scripts, command-line tools or credentials: Replica Recon is instructions for the agent only.
Does Replica Recon access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Replica Recon safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Replica Recon use?
Replica Recon is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Replica Recon use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Replica Recon?
Skills that share tags, products or a category with Replica Recon: Aesthetic Usability Effect (hashgraph-online/awesome-codex-plugins, 1.3k stars), Workbuddy Skin Studio (cdredfox/workbuddy-skin-studio, 197 stars), Marionette Flutter Drive App (leancodepl/marionette_mcp, 482 stars) and App Preview Video (dotnetdreamer/open-screenshot-generator, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Replica Recon?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/replica-skill, which has 1,432 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.
Source: Jakeschincariol/replica-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.