replica-deploy
Jakeschincariol/replica-skill / replica-deploy
checks the clone before going live on your domain , which improves: catches production oversights
Details
- judge’s score
- 6/10
- place
- outside the packs
- publisher
- Jakeschincariol
- status
- new
- pinned commit
- 77c9436 on GitHub (new tab)
- skill’s last commit
- Oct 3, 2026
- repo stars
- 3,651
- main type
- Website
Judgement
Precise triggering and a useful checklist (DNS, SPF/DKIM/DMARC, Stripe live, OAuth). But the preflight scripts are missing, the “rebranded clone” purpose is debatable, and the content remains generic.
reservations
- The scripts mentioned (replica-diff/parity.py, replica-brand/sweep.py, replica-launch/listing.py) and replica-test are not provided: the preflight steps cannot be verified.
- The skill depends on sibling replica-* packs that are not included: its standalone use is limited.
- The skill aims to put a “rebranded” clone of an existing application online: legal risks (intellectual property rights, trademarks) are not addressed.
- Much of the checklist (DNS, Stripe, OAuth, DMARC) is generic and already known to Claude; the Vercel-specific parts are brief.
- Triggering
- 2/2
- Added value
- 1/2
- Precision
- 1/2
- Scope
- 1/2
- Quality
- 1/2
Alerts
no alerts
Neither the static scan nor the judge flagged a risk for this skill.
Original description
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 mobi…
added on Oct 18, 2026 · license MIT