← Search

Replica Diff, score how close your clone is to the original
Development 📌 Pinned version: commit 77c9436
⚙ Needs: a current feature matrix (replica/features.csv) and…

Replica Diff, score how close your clone is to the original

Compares an app clone against the original: a feature parity score from the feature matrix, plus a screenshot layout diff that ignores colour so a rebrand does not count against you.

⚠️ Unverified listing: our automated install test could not be completed for this build (its install prompt tripped a safety filter in our test system), so we have not verified its content.
At a glance
What
Compares an app clone against the original: a feature parity score from the feature matrix, plus a screenshot layout diff that ignores colour so a rebrand does not count against you.
Cost
Free
Needs
a current feature matrix (replica/features.csv) and paired screenshots of the original and the clone in the same viewport and state; Python 3 for the tools (standard-library only, no installs).
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 77c9436

Prerequisites: a current feature matrix (replica/features.csv) and paired screenshots of the original and the clone in the same viewport and state; Python 3 for the tools (standard-library only, no installs). Install "Replica Diff, score how close your clone is to the original" for me. It gives my agent @Jakeschincariol's comparison workflow, the comparison step of the Replica pack: a weighted feature parity score with the missing list in build order, a screenshot layout diff that ignores colour so a rebrand does not count against you, a behaviour diff flow by flow, and an honest verdict: not shippable, shippable, or better than the original. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-diff/SKILL.md Pinned version: install the code at commit 77c9436fb3d18c3d58169efb8caf4fe906b0dc51 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files, including parity.py and imgdiff.py) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code: you create your own accounts and keys and put keys in .env.local, the agent writes .env.example with names only and never types a password, card or live key. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "replica-diff". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. bring the feature matrix up to date; take paired screenshots in the same viewport and state). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. In Muse, invoke pack neighbour skills by name, not as /slash commands. If anything looks off, stop and ask me. After installation, ask me if I want to leave private feedback Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

🧪 Example
You ask
Illustrative example only, not a real user's result. How close is my clone to the original, and what is missing?
You get
Illustrative example only, not a real user's result. replica/parity.md: a feature score and a layout score per screen, the missing features in build order, the behaviour differences, the top five things to build next, and an honest verdict (not shippable, shippable, or better than the original).
Illustrative example based on this skill’s own documentation — not a real user’s result.
🔒 Security, provenance and what this touches
🔒 Security and provenance
📌 Pinned version: commit 77c9436
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.