Recipe freedom to operate

Skill flowleap-ai/flowleap-plugins/plugins/flowleap/skills/recipe-freedom-to-operate

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-freedom-to-operate

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

Freedom-to-operate clearance for a product or technology — per-feature query generation, dual-database blocking-patent search, and legal-status, family, and all-elements claim checks on every live candidate. Trigger when the user asks whether a product or technology can launch without infringing, or requests an FTO/clearance search.

SKILL.md

2.7 KB, 553 tokens by cl100k_base, as published. Nobody here has run it

Recipe: Freedom-to-Operate (FTO) Search

Search for potentially blocking patents for a product or technology. Each database uses its own query syntax — see flowleap-uspto for the USPTO Lucene grammar.

Steps

Step 1: Generate Targeted Searches

Build a query per key product feature, in each database's own syntax:

# EPO CQL
flowleap patent build-query "<feature 1 description>" --allow-external-processing
# USPTO ODP
flowleap uspto build-query "<feature 1 description>" --allow-external-processing
# Repeat for each feature

Done when every key feature has an EPO and a USPTO query.

Step 2: Search for Potentially Blocking Patents

flowleap --json patent search --query "<CQL for feature 1>" --limit 20
flowleap --json uspto search --query "<recommended_query for feature 1>" --limit 20
# Repeat for each feature

Done when both databases have been searched for every feature.

Step 3: Screen to Live, In-Market Candidates

Take the one-call snapshot (bibliography + legal status + family + term) and keep only patents that are legally alive and cover a jurisdiction you sell in:

flowleap --json summary <patent-number>

Or, if you need the pieces separately:

flowleap --json ops legal <patent-number>     # is it active?
flowleap --json ops family <patent-number>    # where is it filed?

Done when every survivor is both in force and filed in a sales jurisdiction; drop the rest.

Step 4: All-Elements Claim Mapping

For each surviving blocker, pull its claims and map product features against every element of each independent claim:

flowleap --json ops claims <patent-number>

A claim clears only if at least one of its elements is absent from the product. Done when every independent claim of every survivor is either cleared (≥1 element absent) or flagged as a live infringement risk.

Output

FTO data package per live blocking patent:

Legal status (active, expired, abandoned) and remaining term
Geographic coverage (family members) against your sales jurisdictions
Per-claim all-elements verdict: cleared or at-risk

If the full skill pack is installed, continue with recipe-infringement-charting to chart the at-risk claims element by element.

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most product growth skills give in 553 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

build a query per key product feature
use each database's own syntax
search both EPO and USPTO databases
keep only legally alive patents
keep only patents covering a sales jurisdiction
pull claims for each surviving blocker

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.