$ loading_
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "takedown" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/ip-legal/skills/takedown/SKILL.md 2. Save it as ~/.claude/skills/takedown/SKILL.md 3. Reload skills and tell me it's ready
Use send mode to draft a DMCA §512(c)(3) takedown notice, and first check fair-use risk plus the good-faith and accuracy requirements.
A takedown notice draft, or a stop-and-review result if fair use is a concern.
Use respond mode to assess a DMCA notice I received, covering license, fair use, defects, host compliance, and sender credibility, then recommend comply / counter / engage / ignore.
A triage memo listing the four response options with a recommendation.
Use counter mode to draft a §512(g)(3) counter-notice, and first confirm the content was removed after a §512 notice, that I have a good-faith belief of mistake or misidentification, and that I am ready for the federal-jurisdiction consent statement.
A counter-notice draft, or a stopped result if the required conditions are not met.
When a copyright owner finds allegedly infringing content on a platform, this skill can draft a DMCA takedown notice. It checks fair-use risk as well as the good-faith, accuracy, and statement requirements first.
When a person or team receives a takedown notice, they can use this skill for initial triage. It reviews license, fair use, defects, host compliance, and sender credibility, then presents comply, counter, engage, and ignore options.
If content was removed after a §512 notice and the recipient has a good-faith belief of mistake or misidentification, this skill can draft a §512(g)(3) counter-notice. It highlights key gates such as federal-jurisdiction consent and the perjury statement.
The README describes three workflows for the takedown skill: drafting a DMCA takedown notice, triaging a notice you received, and preparing a counter-notice. It emphasizes setup checks for the practice profile and matter workspaces, plus gate reviews before output, including fair-use analysis, perjury-related warnings, and consent to federal jurisdiction. It also notes that DMCA §512 is U.S. federal law, so cross-border cases may require a different notice regime.
Three modes. Pick one:
/ip-legal:takedown --send — draft a §512(c)(3) takedown notice. Fair-use gate (Lenz) + loud perjury / §512(f) gate before delivery./ip-legal:takedown --respond — triage a takedown someone sent you. Options: comply / counter / engage / ignore./ip-legal:takedown --counter — draft a §512(g)(3) counter-notice. Loud gate for the federal-jurisdiction admission and the perjury statement.Read the practice profile. Load ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If it contains [PLACEHOLDER] markers or does not exist, stop and say: "This plugin needs setup before it can give you useful output. Run /ip-legal:cold-start-interview — the takedown skill depends on your approval matrix and practice profile."
Check matter workspaces. Per ## Matter workspaces: if Enabled is ✗, skip. If enabled and there is no active matter, ask: "Which matter is this for? Run /ip-legal:matter-workspace switch <slug> or say practice-level."
Dispatch on $ARGUMENTS:
--send → run send mode (below). Walk identify-the-work, identify-the-infringing-material, fair-use gate (Lenz), good-faith belief, accuracy/authority, draft the §512(c)(3) notice, run the loud gate, write output.--respond → run respond mode (below). Read the incoming notice, assess (license, fair use, defects, host §512(g) compliance, sender credibility), present the four options, recommend, write the triage memo.--counter → run counter mode (below). Confirm the predicate (taken down in response to a §512 notice, good-faith belief of mistake/misidentification, ready for federal-jurisdiction admission, attorney in the loop), draft the §512(g)(3) counter-notice, run the loud gate, write output.Respect the gates. In --send and --counter, the loud gate runs before any final output is written. The fair-use gate in --send is separate and runs earlier; "debatable" or "likely" fair use stops the draft and routes to attorney review.
Jurisdiction note. DMCA §512 is US federal law. If the service provider, content, or infringer sits outside US jurisdiction, flag before drafting — you may need an EU DSA notice, UK OSA notice, or local-regime instrument instead of (or in addition to) a DMCA notice.
Hand off where appropriate. --respond with a counter-notice recommendation chains into /ip-legal:takedown --counter — but only after the triage memo has been reviewed and the decision to counter has been made deliberately.
/ip-legal:takedown --send
/ip-legal:takedown --respond ~/Downloads/youtube-takedown-notice.pdf
/ip-legal:takedown --counter
/ip-legal:takedown
The DMCA §512 notice-and-takedown system is fast, cheap, and consequential in equal measure. A takedown is a sworn statement under penalty of perjury that gets content pulled with no judicial review. A counter-notice is another sworn statement that consents to federal jurisdiction and puts the content back. Both decisions can become litigation. This skill handles all three moves with the guardrails each warrants.
Three modes:
--send — draft a §512(c)(3) takedown notice…
It has three modes: drafting a §512(c)(3) takedown notice, triaging a notice you received, and drafting a §512(g)(3) counter-notice. The docs also state that explicit gate checks run for outgoing notices and counter-notices.
The docs require reading the practice profile first; if the configuration is missing or still has placeholders, you need to run the cold-start interview. If matter workspaces are enabled but no matter is active, you must switch to the relevant matter or use practice-level.
It is not just a static template: it separates send, respond, and counter workflows and adds gates for fair use, perjury risk, and federal-jurisdiction consent. The docs also warn that if the parties or content are outside U.S. jurisdiction, a local regime may be needed instead of DMCA.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Temporarily disable or re-enable an installed community skill without deleting files.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Manage matter workspaces to separate, switch, and archive client contexts.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Standardize new matter intake and generate matter files plus a structured log.