← Search

Replica Launch, write the landing page, pricing and store listing for your clone
Development 📌 Pinned version: commit 77c9436
⚙ Needs: a positioning angle and evidence from…

Replica Launch, write the landing page, pricing and store listing for your clone

Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules.

⚠️ 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
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules.
Cost
Free
Needs
a positioning angle and evidence from replica-entrepreneur, and a brand from replica-brand; you create Stripe products and prices yourself. Inputs you must already have: feedback.md (pricing complaints), the replica-design contrast check on the landing page, and a project that already exists — launch-only, without the prior pack steps, cannot run end-to-end.
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 positioning angle and evidence from replica-entrepreneur, and a brand from replica-brand; you create Stripe products and prices yourself. Inputs you must already have: feedback.md (pricing complaints), the replica-design contrast check on the landing page, and a project that already exists — launch-only, without the prior pack steps, cannot run end-to-end. Install "Replica Launch, write the landing page, pricing and store listing for your clone" for me. It gives my agent @Jakeschincariol's launch workflow, the launch step of the Replica pack: a landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and an App Store and Google Play listing linted against the stores' limits and copycat rules, plus a launch plan. No fake proof, no reviewer quotes as testimonials, and the original's name stays out of the app name, listing, keywords and ads. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-launch/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 listing.py and listing.example.json) 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-launch". 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 angle and brand; read the original's public pricing page and note the date; create Stripe products and prices 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. Write the landing page, pricing and store listing for my rebranded clone.
You get
Illustrative example only, not a real user's result. replica/launch/ complete: landing.md built in the project, pricing.md, listing.json with listing.py passing (upstream example: 0 errors, 1 warning — “free reads as a ranking or price claim”, so not warning-free), and launch-plan.md with the first ten users to talk to by hand. Next step: replica-deploy (invoked by name in Muse).
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.