Recipe patent landscape
Skill flowleap-ai/flowleap-plugins/plugins/flowleap/skills/recipe-patent-landscape
The FlowLeap Plugin Marketplace — curated, free-to-install skill packs for patent and IP work.
npx -y skills add flowleap-ai/flowleap-plugins --skill recipe-patent-landscapeAssembled 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
Patent-landscape analysis for a technology area — scoped dual-database search, key-player identification, full-corpus filing analytics, and CPC-versus-year white-space detection. Trigger when the user asks to map a technology space, identify who patents in an area, or report filing trends and white space.
SKILL.md
3.2 KB, 699 tokens by cl100k_base, as published. Nobody here has run it
Recipe: Patent Landscape Analysis
Map the patent landscape for a technology area, identifying key players, trends,
and gaps. Each database uses its own query syntax — see flowleap-uspto for the
USPTO Lucene grammar.
Steps
Step 1: Define Search Scope
flowleap patent build-query "<technology description>" --allow-external-processing
flowleap uspto build-query "<technology description>" --allow-external-processing
Done when you have an EPO CQL query and a USPTO ODP query for the area.
Step 2: Broad Patent Search
flowleap --json patent search --query "<CQL from step 1>" --limit 50
flowleap --json uspto search --query "<recommended_query from step 1>" --limit 50
Done when both databases have returned their result sets.
Step 3: Corpus Analytics
# Filing trends by year, country and CPC breakdowns, top assignees
flowleap --json analytics --keyword "<technology>" --date-from 2015-01-01
flowleap --json analytics --cpc <cpc-prefix> --country US --date-from 2020-01-01
Step 4: Identify Key Players
Build applicant-scoped queries rather than hand-writing CQL — see flowleap-patent
for the CQL fields (pa= applicant, ti= title):
flowleap patent build-query "<top assignee> patents in <technology>" --allow-external-processing
flowleap --json patent search --query "<CQL from build-query>" --limit 30
Step 5: Check Recent Activity
patent search returns relevance-ranked hits; ops search --cql adds CQL
date-range filtering (pd>=2024) for a time-sliced view the ranked search does
not expose:
flowleap ops search --cql "ti=<technology> AND pd>=2024" --start 1 --end 50
Step 6: Flag White Space
Cross the analytics CPC breakdown against the filing-year trend to flag subclasses that are sparse or declining while neighbours grow. Done when at least one sparse/declining CPC subclass (or a confirmed absence) is identified.
Output
A dataset segmented by database, applicant, and filing date, plus corpus-level
trend charts (filings per year, top assignees, CPC and country distributions).
When tallying players or counts from the search results, collapse to one entry
per patent family so multi-jurisdiction filings are not double-counted; the
corpus analytics figures are aggregate backend counts, reported as returned.
Visual deliverable
To turn Step 3's filing-trend numbers and Step 6's white-space finding into a
shareable HTML dashboard, follow this recipe's analysis through to the end,
then render it with recipe-custom-dashboard — its landscape white-space
template (CPC × year heatmap) is built for this recipe's final step, and its
filing-trends template covers Step 3's year-over-year counts. Analysis
logic stays here; the dashboard skill only owns presentation.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.