← Search

Replica Deploy, ship your clone live on your own domain
Development 📌 Pinned version: commit 77c9436
⚙ Needs: everything in replica/ complete…

Replica Deploy, ship your clone live on your own domain

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 host, DNS records for the domain and for email, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play.

⚠️ 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
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 host, DNS records for the domain and for email, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play.
Cost
Free
Needs
everything in replica/ complete, including a clean rebrand sweep; a domain you buy yourself; production accounts and live keys set by you in the host. Preflight needs the sibling scripts ../replica-diff/parity.py + replica/features.csv, ../replica-brand/sweep.py + replica/brand.json, ../replica-launch/listing.py + replica/launch/listing.json, plus the replica/ project itself. The listing-linted gate applies only if shipping to stores. If there is a mobile app, developer accounts cost Apple $99/yr and Google $25 once; Stripe's test is one real purchase and a refund. Nothing goes live without your go after the preflight.
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: everything in replica/ complete, including a clean rebrand sweep; a domain you buy yourself; production accounts and live keys set by you in the host. Preflight needs the sibling scripts ../replica-diff/parity.py + replica/features.csv, ../replica-brand/sweep.py + replica/brand.json, ../replica-launch/listing.py + replica/launch/listing.json, plus the replica/ project itself. The listing-linted gate applies only if shipping to stores. If there is a mobile app, developer accounts cost Apple $99/yr and Google $25 once; Stripe's test is one real purchase and a refund. Nothing goes live without your go after the preflight. Install "Replica Deploy, ship your clone live on your own domain" for me. It gives my agent @Jakeschincariol's shipping workflow, the final step of the Replica pack: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, host and DNS for my own domain, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play if there is an app. I buy and sign in myself; the agent never buys a domain, enters a card, types a password or pastes a live key. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-deploy/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 the preflight.md checklist template) 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-deploy". 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. show me the preflight results and wait for my go; buy the domain and set DNS and live keys myself). 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. Ship my finished, rebranded clone live on my own domain.
You get
Illustrative example only, not a real user's result. replica/deploy.md with every preflight check and its result, shown to you for your go before anything goes live; then the production database, host and DNS records, Stripe live mode, OAuth redirects and monitoring, and the live URL with what to watch in the first week.
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.