skill
Skill1 starsChanged 25 days agoMITView on GitHub
You now know how to clone any website's public interface, byte-faithfully, and deploy it as a live copy on GitHub Pages. Follow this file exactly. Single-file CLI at skill/sitejack.py (Python 3.8+ stdlib only). Run with python3 skill/sitejack.py <command>. When a user says "clone this site and put it online":
- Reads credentials
66 other projects use a version of this.
Adopted by
Most recently taken up by
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- nmamano/isomuxtheir own version, first seen Nov 15, 2026
- Qson8/topicscouttheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- thenavidm/skill-buildertheir own version, first seen Nov 8, 2026
- HelloRuru/claude-teams-gotheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ai-slop-cleaner, ralplan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Jurel89Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Also in 5 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 5 projects that use this
ibahgatSkillhud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 5 projects that use this
Jurel89Skillultraqa
QA cycling loop — build/lint/test, fix, retry up to 5 cycles
Also in 3 projects that use this
LucasCooperBeySkillvisual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons. Returns JSON scores driving edit iterations. Use after any UI implementation to verify visual fidelity.
Also in 3 projects that use this
Yeachan-HeoSkillultragoal
Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.
Also in 3 projects that use this
Other versions66 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 66
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tradecatlabs/vibe-coding-cn★ 18ksame name
- tukuaiai/vibe-coding-cn★ 18ksame name
- liyue-aigc/female-portrait-director★ 1.6ksame name
- sundial-org/skills★ 151same name
- build23w/fdv.lol★ 128same name
- builders-toronto/fdv.lol★ 128same name
- redf0x1/camofox-mcp★ 124same name
56 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
When a user says "clone this site and put it online":
- Distinctive: line 33
Never try to clone authenticated content, paid content, or anything behind a login.
- Distinctive: line 34
Never print a secret the scan finds — it prints masked.
- Very specific: line 35
Never claim byte-fidelity without running verify.
- Distinctive: line 37
If the user seems to want to impersonate someone's brand/site, ask what the clone is for and suggest legal alternatives (backup, study, …
“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
sitejack — agent skill
You now know how to clone any website's public interface, byte-faithfully, and deploy it as a live copy on GitHub Pages. Follow this file exactly.
Tool
Single-file CLI at skill/sitejack.py (Python 3.8+ stdlib only). Run with python3 skill/sitejack.py <command>.
Command contract
| command | use it when | on failure |
recon <url> | the user names a site they want studied or cloned | report the HTTP status honestly; do not guess the stack |
clone <url> | the user wants the interface copied; mirror lands in ./<host>-clone/ with manifest.json | a partial report in the manifest is normal for huge sites — say how deep it went |
clone <url> --wayback | the site is down or returns errors | wayback mirrors are best-effort; say so |
scan <dir> | ALWAYS between clone and deploy — non-negotiable | if it exits with code 2, STOP: there are secrets. Show the masked findings, propose removal, never deploy |
deploy <dir> <repo> | the user asks to publish; requires GITHUB_TOKEN env (repo scope) | if Pages build hasn't finished, say it is building — never claim live without HTTP 200 |
verify <dir> <url> | the user doubts the copy, or before claiming "perfect clone" | exit code 2 means hash mismatch — report exactly which files |
The canonical run
When a user says "clone this site and put it online":
recon <url>— tell them the stack, fonts, palette, and roughly how many assets.clone <url>.scanthe clone dir. If secrets: STOP and report.deploy <dir> <repo-name>— picks a repo name close to the brand; asks the user only if the name matters.- Report the live URL and the repo URL. Offer
verifyas proof.
Guardrails (hard rules)
- Public frontends only. https-only. Private/internal hosts are blocked by the tool — never work around it.
- Never try to clone authenticated content, paid content, or anything behind a login.
- Never print a secret the scan finds — it prints masked; keep it masked in your replies.
- Never claim byte-fidelity without running
verify. - Clones are static: API calls still point to the original domain. Say this when the user expects functionality, not just the interface.
- If the user seems to want to impersonate someone's brand/site, ask what the clone is for and suggest legal alternatives (backup, study, redesign, demo).
Reading the outputs
manifest.json— every saved file with size and SHA-1;skippedexplains every absence;partial: truemeans the cap hit before the graph closed.scanoutput — file, secret family (Mapbox, OpenAI…), masked fragment. This mirrors what GitHub Push Protection blocks, so a clean scan ≈ a push that goes through.deploy— printsLIVE: <url>only after an HTTP 200 check on the Pages URL.
Known gotchas the tool already handles (don't reintroduce them)
- GitHub Pages runs Jekyll, which silently ignores folders starting with
_(like SvelteKit's_appor Next's_next) —deploywrites.nojekyllfor you. - Routes without extensions (
/pricing) must land inpricing/index.html, or they 404 on Pages. - Absolute URLs in the source must stay absolute (they point at the original); only same-origin paths become clone files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

