recipe-infringement-charting
Skill1 starsChanged 4 months agoMITView on GitHub
Litigation recipe for an element-by-element infringement claim chart — verify the patent is in force where it matters, decompose the asserted claims, extract accused-product evidence (OCR datasheets and manuals), and map every element with literal and doctrine-of-equivalents columns. Trigger when the user asks whether a product infringes a patent, wants a claim chart, or needs element-by-element infringement mapping.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- flowleap-academicSkill
- flowleap-authSkill
- flowleap-citationSkill
- flowleap-keysSkill
- flowleap-legalSkill
- flowleap-nplSkill
- flowleap-opsSkill
- flowleap-patentSkill
- flowleap-patstat-graphSkill
- flowleap-patstatSkill
- flowleap-sharedSkill
- flowleapSkill
- flowleap-toolsSkill
- flowleap-usptoSkill
- persona-ip-analystSkill
- persona-patent-attorneySkill
- persona-researcherSkill
- persona-startup-founderSkill
- recipe-academic-literature-reviewSkill
- recipe-audit-reportSkill
- recipe-claim-analysisSkill
- recipe-claim-draftingSkill
- recipe-custom-dashboardSkill
- recipe-find-betterSkill
- recipe-freedom-to-operateSkill
- recipe-invalidity-analysisSkill
- recipe-invention-disclosureSkill
- recipe-maintenance-feesSkill
- recipe-office-action-responseSkill
- recipe-patent-landscapeSkill
- recipe-patent-to-reportSkill
- recipe-prior-art-searchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Only chart in jurisdictions with a live family member.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Recipe: Infringement Charting
Map asserted claims onto an accused product, element by element.
In a chat client with the FlowLeap connector or in the FlowLeap Patent AI app, call the tools named in the flowleap-shared tool table instead of these commands, and never run a flowleap command there. The steps stay the same.
Step 1: Asserted Patent Intake
flowleap --json summary <asserted-patent> # biblio, legal status, family, term
flowleap --json ops claims <asserted-patent>
flowleap --json ops description <asserted-patent> # claim-construction supportStep 2: Enforceability Check
A chart against an expired or lapsed patent is wasted work — check first:
flowleap --json ops legal <asserted-patent> # status events
flowleap --json tools run get_patent_term patent_number=<asserted-patent> # expiry estimate
flowleap --json ops family <asserted-patent> # where it is in forceOnly chart in jurisdictions with a live family member.
Step 3: Decompose the Asserted Claims
Decompose each asserted independent claim yourself: split on the
comprising transition and the semicolon/wherein boundaries, and keep the
claim language verbatim per element — the chart maps accused-product
evidence against the claim words, not a paraphrase (the method is in
recipe-claim-analysis, Step 4).
The element list becomes the chart's rows. Every element must be met — one missing element defeats literal infringement of that claim.
Step 4: Accused-Product Evidence Intake
flowleap ocr ./accused-product-datasheet.pdf > datasheet.md
flowleap ocr https://example.com/product-manual.pdf > manual.mdCollect: datasheets, manuals, teardown reports, marketing claims. Note the provenance of every document — the chart cites evidence, not impressions.
Step 5: Build the Chart
| Claim element | Claim language | Accused product feature | Evidence (doc + location) | Literal? | DoE? |
- Literal: the element reads directly on the product feature
- DoE (doctrine of equivalents): insubstantial difference — function/way/result; flag prosecution-history estoppel risks from the file history
The doctrine of equivalents and prosecution-history estoppel are US case law,
not MPEP text. Read the MPEP section that names the decisions from the
office's own page with flowleap-legal (MPEP 2186), quote it with its URL and
edition, and name the decisions it cites.
Step 6: Construction Disputes
For each element where the mapping is contested, pull the specification passages that define the term (Step 1's description) and record both constructions with the chart cell marked "disputed".
Output
- Enforceability memo (status, term, jurisdictions)
- Element-by-element claim chart with literal/DoE columns and evidence cites
- List of disputed constructions with spec support for each side
- Caveat block: this is an analysis aid, not a legal opinion
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

