dmca-strategies-for-ip-violations
Made by JeffRuns evidence-first copyright enforcement for a SaaS's paid content: proof, notices, deadlines, DMCA takedowns, follow-up. Use when paid content leaks, or for takedown notices or infringing forks.
From Jeffrey's Skills.md: professionally crafted skills for any AI agent, installed and kept in sync by the jsm CLI. Subscription only, $20/month.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New skill: dmca-strategies-for-ip-violations, evidence-first takedowns when paid content leaks into public repositories
An agent runs copyright enforcement for a SaaS whose paid content turns up in public repositories, forks, mirrors and directory sites. Each claimed file is matched by fingerprint against what was actually sold, checked against everything the owner ever published, dated against the sale and re-read anonymously before anyone is contacted. Notices go out only on the owner's yes to the exact text, and takedowns only with the owner's signature.
- A five-check claim test per file: rights, measured identity, never public, on sale before the copy appeared, and an anonymous re-read on the day of sending.
- fingerprint-match.py indexes every delivered version and reads every branch and tag of a repository through a blob-free clone. A ref, folder or file it cannot read is reported as UNSCANNED, never as clean.
- text-overlap.py measures reformatted and re-headed copies by 8-word shingle share and cover, against only the versions on sale before the copy appeared.
- 25 templates with a lint kind for each, from a gentle note to a customer to GitHub's and GitLab's takedown forms. notice-lint.py checks register, required elements, leftover options and size.
- The owner approves the exact text and signs every takedown; a scheduled run drafts and asks but never sends or files.
- Every surface is checked before anything is called removed: branches, tags and their archives, history, closed pull-request refs, forks, module proxies and directory sites, each with copy-paste commands.
- A stalled-host ladder at days 7, 14 and 30, and the counter-notice questions to settle with counsel before the first filing.
- From one campaign: 80% of first notices were complied with by the deadline, a follow-up after a partial removal converted 4 of 4, and the host removed nothing recorded within 12 days.
- 24 anonymized cases, a 30-rule kernel tied to 89 verified quotes, 19 playbooks, 27 ready-to-paste agent prompts and a validator that checks every cross-reference.
A file is claimed only when it passes five checks: the signer owns the rights; it is byte-identical to a file that was delivered, or proven to be one reformatted, with the number stated; it was never public anywhere the owner's exclusion inventory covers; that version was on sale before the copy first appeared in the holder's history; and an anonymous raw fetch agrees on the day of sending. A title or folder name is only a lead, and a fork that asks for a login is recorded as unscanned rather than clean.