CtrlK
BlogDocsLog inGet started
Tessl Logo

takedown

Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice. Use when asserting copyright through a §512(c)(3) takedown with the fair-use and perjury gates, when an incoming takedown needs triage into comply / counter / engage / ignore options, or when drafting a §512(g)(3) counter-notice with the consent-to-federal-jurisdiction gate.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with clear, gated workflows appropriate to sworn legal documents — its strongest dimensions. It loses points on conciseness (duplicated mode summaries and jurisdiction notes) and progressive disclosure (a large monolithic file with no reference split).

Suggestions

De-duplicate the three-mode summary and the jurisdiction note so each appears once; collapse the "Purpose" restatement or fold it into the top instructions.

Extract the stable templates (triage memo, loud-gate blocks, statutory element checklists) into reference files under references/ and link to them, reducing the SKILL.md body and adding genuine progressive disclosure.

DimensionReasoningScore

Conciseness

Much of the detail is genuinely specialized legal content Claude should not assume, but the body carries clear redundancy: the three-mode summary is repeated (top instructions and the Purpose section) and the jurisdiction note appears both as Instruction step 5 and again as the "Jurisdiction assumption" section. It is not score 3 because of this duplicated material, and not score 1 because the bulk is substantive rather than explaining concepts Claude already knows.

2 / 3

Actionability

Exact §512(c)(3) and §512(g)(3) element lists, verbatim statement language, concrete output paths, the copyright.gov DMCA directory URL, and a full triage-memo template give copy-paste-ready executable guidance. It is not score 2 because the instructions are complete and specific rather than pseudocode or abstract.

3 / 3

Workflow Clarity

Each mode has numbered Steps with explicit validation checkpoints (fair-use gate, loud gate) and feedback loops ("debatable"/"likely" fair use stops the draft and routes to attorney review; "Do not write the final output without explicit engagement"). It is not score 2 because checkpoints and error-recovery loops are explicit for these consequential sworn-statement operations.

3 / 3

Progressive Disclosure

The skill is a single ~448-line file with no references/scripts/assets bundle, and content that could be split (triage memo template, loud-gate ASCII blocks) is inline. It is not score 3 because the under-50-lines simple-skill exemption does not apply and no one-level-deep reference files exist, and not score 1 because the body is well-sectioned rather than a disorganized wall of text.

2 / 3

Total

10

/

12

Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit "Use when" trigger clause, concrete enumerated actions, and a clearly bounded DMCA niche. Its only weakness is trigger-term quality, where natural user phrasing is weighed down by statutory citations.

Suggestions

Lead the "Use when" clause with the plain-language terms a user would actually say (e.g., "send a DMCA takedown", "got a DMCA takedown notice", "file a counter-notice") before the statutory citations.

Move the dense §512(c)(3)/§512(g)(3) qualifiers into the body and keep the description's trigger language closer to everyday phrasing.

DimensionReasoningScore

Specificity

"Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice" lists multiple specific concrete actions (draft, triage, draft counter-notice), matching the score-3 anchor. It is not score 2 because the actions are concrete and enumerated rather than partial.

3 / 3

Completeness

It explicitly states what the skill does (draft / triage / counter) and includes an explicit "Use when..." clause covering all three triggers, answering both what and when. It is not score 2 because the when is explicit rather than merely implied.

3 / 3

Trigger Term Quality

Natural terms like "DMCA takedown notice", "counter-notice", and "triage" are present, but the "Use when" clause is dominated by statutory jargon (§512(c)(3), §512(g)(3), perjury gates, consent-to-federal-jurisdiction) that a lay user would not naturally say. It is not score 3 because common natural variations are buried under technical citations, and not score 1 because several relevant everyday keywords do appear.

2 / 3

Distinctiveness Conflict Risk

The DMCA takedown / counter-notice / triage niche has distinct triggers unlikely to fire for unrelated skills. It is not score 2 because the scope is sharply bounded to a specific statutory regime rather than overlapping with general legal or document skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-for-legal
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.