skills/legal/answer-with-invalidity-contentions/SKILL.md
Drafts a defendant's Answer with Invalidity Contentions responding to a U.S. patent infringement complaint. Covers FRCP 8(b) admissions/denials, affirmative defenses, and PLR 3-3 invalidity contentions with claim charts under 35 U.S.C. §§ 101, 102, 103, 112. Use when representing a defendant in the pleadings phase of federal patent litigation who must respond to an infringement suit and assert prior art, anticipation, obviousness, or § 112 defenses.
npx skillsauth add casemark/skills answer-with-invalidity-contentionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Combined answer and Patent Local Rule 3-3 invalidity contentions for a patent defendant — responds to each complaint allegation while building the invalidity record for trial.
Respond paragraph-by-paragraph mirroring complaint numbering.
| Response | When | Language | |---|---|---| | Admit | Verifiable facts (jurisdiction, patent issuance) | "Defendant admits U.S. Patent No. X was issued on [date]." | | Admit in part / Deny in part | Mixed fact and legal conclusion | "Admits it manufactures [product]; denies infringement of any valid claim." | | Lack of knowledge (8(b)(5)) | Within plaintiff's peculiar knowledge | "Lacks sufficient knowledge; treated as denial." | | Deny | False facts and all legal conclusions | "Defendant denies." |
Number separately. Apply Twombly/Iqbal plausibility with brief factual predicates.
| # | Defense | Notes | |---|---|---| | 1 | Non-infringement | Literal and DOE | | 2 | Invalidity — §§ 101, 102, 103, 112 | Claim charts in § 5; pled in alternative | | 3 | Inequitable conduct | FRCP 9(b) particularity; reserved pending discovery | | 4 | Prosecution laches / Equitable estoppel | If prosecution history supports | | 5 | License / Exhaustion | If authorized sale or course of dealing | | 6 | Failure to state a claim | Missing claim specificity | | 7 | Statute of limitations | 35 U.S.C. § 286 (6-year bar) | | 8 | Unclean hands / Waiver | As facts support |
Defenses not raised may be waived under FRCP 8(c) — err toward inclusion.
Each contention requires: (a) reference identification, (b) prior art qualification, (c) claim chart.
Reference header: Title, authors/inventors, publication date, publisher/assignee, patent or publication number, prior art basis (AIA § 102(a)(1)/(a)(2) or pre-AIA § 102(a)/(b)/(e)/(g)).
One chart per reference per claim. Map every limitation.
| Claim Limitation | Prior Art Disclosure (col:line or pg:¶) | Analysis | |---|---|---| | [Preamble] | [Ref. p. X, ¶ Y] | [Disclosure explanation] | | [Element 1a] | [Ref. col. 3:12–25] | [Mapping] |
Apply Graham v. John Deere (scope of art, differences, POSITA level, objective indicia). Motivation to combine per KSR v. Teleflex: explicit suggestion, problem-solution, obvious to try, known elements in established functions.
| Claim Limitation | Primary Ref. | Secondary Ref. | Combination Rationale | |---|---|---|---| | [Element 1a] | Ref. A, col. 2:10 | — | Taught by A alone | | [Element 1b] | — | Ref. B, p. 5 | POSITA would combine: [motivation] |
Rebut secondary considerations: commercial success (non-claimed features), long-felt need (art already suggested), failure of others (lack of motivation), unexpected results (predictable to POSITA).
| Ground | Standard | Identify | |---|---|---| | § 112(a) Written description | Inventor possessed full claim scope at filing | Broad terms unsupported by spec | | § 112(a) Enablement | No undue experimentation (Wands factors) | Claim breadth vs. spec disclosure | | § 112(b) Indefiniteness | Reasonably certain to POSITA (Nautilus v. Biosig) | Subjective/relative terms, unbounded functional language | | § 112(f) Means-plus-function | Spec must disclose corresponding structure | Nonce words without disclosed structure |
Alice/Mayo two-step: (1) directed to abstract idea, law of nature, or natural phenomenon? (2) inventive concept beyond routine/conventional activity?
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.