Recipe infringement charting

Skill flowleap-ai/flowleap-plugins/plugins/flowleap/skills/recipe-infringement-charting

The FlowLeap Plugin Marketplace — curated, free-to-install skill packs for patent and IP work.

Install

npx -y skills add flowleap-ai/flowleap-plugins --skill recipe-infringement-charting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.1 KB, 614 tokens by cl100k_base, as published. Nobody here has run it

Recipe: Infringement Charting

Map asserted claims onto an accused product, element by element.

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 support

Step 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 force

Only chart in jurisdictions with a live family member.

Step 3: Decompose the Asserted Claims

Save each asserted independent claim to a file, then:

flowleap analyze-claim --file claim1.txt --focus elements

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.md

Collect: 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

flowleap --json legal search "doctrine of equivalents function way result" --jurisdiction uspto
flowleap --json legal search "prosecution history estoppel" --jurisdiction uspto

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.