Paid content copy detection
@slashclone/paid-content-copy-detection
Catch re-uploads of paid content before they go public: fingerprint each paid item's files, ignore the parts a copier changes for free (front matter, whitespace), and hold any public upload by someone else that matches for a person to review. Writes the code and tests for you to review.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads and changes files in the places it lists, nowhere else.
- Nothing runs until you choose to use it, and you can remove it any time.
SKILL.md
Copy detection for paid content
Goal: a buyer can always copy files they paid for, so make the obvious abuse (re-uploading paid files as free content on your own platform) easy to catch and costly. Hold matches for a person; never auto-delete.
How it works
- Fingerprint paid items. When an item becomes paid, and whenever a new version of a paid item publishes, store one fingerprint per file:
sha256of the file's normalized content, with the item id and path. Normalize before hashing, so trivial edits do not escape:
- text files: drop a leading YAML front matter block (it usually names the item, the first thing a copier renames), collapse all whitespace to single spaces, and trim;
- binary files: hash as they are;
- skip manifest files (they always differ) and anything under a minimum size, for example 200 bytes after normalizing, since tiny boilerplate files match by chance.
- Check public uploads. Before a public version is reviewed or published, fingerprint its files the same way and look up matches against paid items owned by someone else. Never match an owner against their own items.
- Hold, do not reject. A match puts the version in a held state with the matching item names, alerts staff, and publishes nothing. Staff compare and either publish (fair use, the owner, a licensed copy) or reject.
- Private copies are fine. Buyers may keep private clones of what they bought. Only public uploads are checked.
Steps
- Find where uploads are validated and published, and where "held for review" already exists (reuse it if so).
- Add a fingerprint table (item id, sha256, path) with an index on sha256, and the normalize-and-hash function.
- Index on pricing and on each new paid version; clear the index when an item becomes free.
- Call the check before publishing public versions; record the reason on the held version and send one alert.
- Add a report reason such as "a copy of paid content", so buyers and creators can flag copies found later.
- Write tests: an exact copy is held, a copy with a renamed header and changed spacing is held, the owner's own next version is not, a private copy is not, and small files never match.
Rules
- Never block a person's private copies or downloads of what they bought.
- Do not store file contents for this, only hashes.
- Off the platform (other sites), the creator's copyright and a takedown notice are the tools; say so in your terms.
README.md
paid-content-copy-detection
A house kit harvested from building SlashClone. See SKILL.md for what it does and how Claude uses it.
Files
- README.md
- SKILL.md
- kit.json
Did it work?
0worked for them0did not work
Sign in to say whether it worked for you.
Nobody has said yet. Tried it? Tell the next person.
