[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F0QVPTPHEX5RH724KS81W":3,"skill-same:01M78F0QVPTPHEX5RH724KS81W":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M78F0QVPTPHEX5RH724KS81W","recipe-freedom-to-operate",null,"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\u002Fclearance search.","flowleap-ai\u002Fflowleap-plugins","flowleap-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F308447201?v=4","01M78EW41SDYP0XH04G056G4GS","01M78EW42W8DAJJK73C3Z95PEA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fflowleap\u002Fskills\u002Frecipe-freedom-to-operate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: recipe-freedom-to-operate\ndescription: 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\u002Fclearance search.\nmetadata:\n  requires:\n    skills: [\"flowleap-shared\", \"flowleap-patent\", \"flowleap-uspto\", \"flowleap-ops\"]\n---\n\n# Recipe: Freedom-to-Operate (FTO) Search\n\nSearch for potentially blocking patents for a product or technology. Each\ndatabase uses its own query syntax — see `flowleap-uspto` for the USPTO Lucene\ngrammar.\n\nIn 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.\n\n## Steps\n\n### Step 1: Write Targeted Searches\n\nWrite a query per key product feature, in each database's own syntax, yourself\n(method in `flowleap-patent`; ODP Lucene in `flowleap-uspto`). For each\nfeature: extract its specific noun phrases, build the CQL around the\ndiscriminating ones, and probe the count — FTO is a recall search, so refine\ntoward broad (drop classifications, OR in synonyms) rather than precise:\n\n```bash\n# EPO CQL count probe for feature 1 (read `total` from the payload)\nflowleap --json tools run search_patents query='\u003CCQL for feature 1>' range=1-1 details=false\n# Repeat for each feature; USPTO Lucene queries are title + metadata only\n```\n\nDone when every key feature has a probed EPO CQL query and a USPTO ODP query.\n\n### Step 2: Search for Potentially Blocking Patents\n\n```bash\nflowleap --json patent search --query \"\u003CCQL for feature 1>\" --limit 20\nflowleap --json uspto search --query \"\u003Crecommended_query for feature 1>\" --limit 20\n# Repeat for each feature\n```\n\n**A missing patent-data key never narrows a clearance scope.** If one office\nanswers `provider_keys_required`, search the live office fully and carry the\ngated office into the deliverable as an explicit missing-key gap — an\nunsearched jurisdiction is not a cleared one, and web-scraped patent data is not\nan acceptable substitute for it. Ask for the free key at the end of the turn;\nwhen the user adds it, re-run only that office and merge. See `flowleap-keys`.\n\nDone when both databases have been searched for every feature, or the gated\noffice is recorded as an open missing-key gap.\n\n### Step 3: Screen to Live, In-Market Candidates\n\nTake the one-call snapshot (bibliography + legal status + family + term) and\nkeep only patents that are **legally alive** and cover a **jurisdiction you\nsell in**:\n\n```bash\nflowleap --json summary \u003Cpatent-number>\n```\n\nOr, if you need the pieces separately:\n\n```bash\nflowleap --json ops legal \u003Cpatent-number>     # is it active? which states?\nflowleap --json ops family \u003Cpatent-number>    # where is it filed?\n```\n\nRead the jurisdiction from the right field. `family` names the **offices** the\ninvention published in; for an EP member that is one entry (\"EP\") and says\nnothing about countries. The countries are the `designatedStates` on the legal\nstatus (`extensionStates` for extension\u002Fvalidation states) — for a European\nregional filing those ARE its designated-state coverage. Then subtract the states\nlapsed per the `PG25`\u002F`PGFP` events, which each carry their own `state`: a patent\ndesignating DE and still paying fees there blocks you in Germany, one lapsed\nthere does not.\n\nThe designation is rolled up from the AK event with the latest date. If that\nevent carried no readable list an older one answers, so the set can be a\nsuperseded, **wider** one — it can name a state the applicant has since dropped.\nFor a clearance call that is the dangerous direction, so read the `AK` rows in\n`events` before you flag or clear a market on the roll-up alone.\n\nDone when every survivor is both in force and designates a sales jurisdiction;\ndrop the rest.\n\n### Step 4: All-Elements Claim Mapping\n\nFor each surviving blocker, pull its claims and map product features against\nevery element of each independent claim:\n\n```bash\nflowleap --json ops claims \u003Cpatent-number>\n```\n\nFor an office with no text source, use the family-member workaround in `flowleap-shared`.\n\n**An unread claim is never a cleared claim.** A survivor at an office with no\ntext source answers `FULLTEXT_UNAVAILABLE`. When the workaround finds a served\nmember, chart from that member's claims and label the chart\n\"member text, not the office's claims\": a reading aid, not a verdict on the\noffice's right. When\nno member's text is served, carry the survivor into the deliverable as\n\"claims not readable here\", an open gap on the same footing as a missing-key\ngap: never cleared, never dropped.\n\nA claim clears only if at least one of its elements is absent from the product.\nDone when every independent claim of every survivor is either cleared (≥1 element\nabsent), flagged as a live infringement risk, or recorded as\n\"claims not readable here\".\n\n## Output\n\nFTO data package per live blocking patent:\n- Legal status (active, expired, abandoned) and remaining term\n- Geographic reach against your sales jurisdictions — family members for the\n  offices, `designatedStates` minus lapsed states for an EP filing's countries\n- Per-claim all-elements verdict: cleared or at-risk; a chart built on a\n  family member's claims carries the label\n  \"member text, not the office's claims\"; a right whose claims no source\n  serves is \"claims not readable here\", an open gap\n\nIf the full skill pack is installed, continue with `recipe-infringement-charting`\nto chart the at-risk claims element by element.\n","# Recipe: Freedom-to-Operate (FTO) Search\n\nSearch for potentially blocking patents for a product or technology. Each\ndatabase uses its own query syntax — see `flowleap-uspto` for the USPTO Lucene\ngrammar.\n\nIn 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.\n\n## Steps\n\n### Step 1: Write Targeted Searches\n\nWrite a query per key product feature, in each database's own syntax, yourself\n(method in `flowleap-patent`; ODP Lucene in `flowleap-uspto`). For each\nfeature: extract its specific noun phrases, build the CQL around the\ndiscriminating ones, and probe the count — FTO is a recall search, so refine\ntoward broad (drop classifications, OR in synonyms) rather than precise:\n\n```bash\n# EPO CQL count probe for feature 1 (read `total` from the payload)\nflowleap --json tools run search_patents query='\u003CCQL for feature 1>' range=1-1 details=false\n# Repeat for each feature; USPTO Lucene queries are title + metadata only\n```\n\nDone when every key feature has a probed EPO CQL query and a USPTO ODP query.\n\n### Step 2: Search for Potentially Blocking Patents\n\n```bash\nflowleap --json patent search --query \"\u003CCQL for feature 1>\" --limit 20\nflowleap --json uspto search --query \"\u003Crecommended_query for feature 1>\" --limit 20\n# Repeat for each feature\n```\n\n**A missing patent-data key never narrows a clearance scope.** If one office\nanswers `provider_keys_required`, search the live office fully and carry the\ngated office into the deliverable as an explicit missing-key gap — an\nunsearched jurisdiction is not a cleared one, and web-scraped patent data is not\nan acceptable substitute for it. Ask for the free key at the end of the turn;\nwhen the user adds it, re-run only that office and merge. See `flowleap-keys`.\n\nDone when both databases have been searched for every feature, or the gated\noffice is recorded as an open missing-key gap.\n\n### Step 3: Screen to Live, In-Market Candidates\n\nTake the one-call snapshot (bibliography + legal status + family + term) and\nkeep only patents that are **legally alive** and cover a **jurisdiction you\nsell in**:\n\n```bash\nflowleap --json summary \u003Cpatent-number>\n```\n\nOr, if you need the pieces separately:\n\n```bash\nflowleap --json ops legal \u003Cpatent-number>     # is it active? which states?\nflowleap --json ops family \u003Cpatent-number>    # where is it filed?\n```\n\nRead the jurisdiction from the right field. `family` names the **offices** the\ninvention published in; for an EP member that is one entry (\"EP\") and says\nnothing about countries. The countries are the `designatedStates` on the legal\nstatus (`extensionStates` for extension\u002Fvalidation states) — for a European\nregional filing those ARE its designated-state coverage. Then subtract the states\nlapsed per the `PG25`\u002F`PGFP` events, which each carry their own `state`: a patent\ndesignating DE and still paying fees there blocks you in Germany, one lapsed\nthere does not.\n\nThe designation is rolled up from the AK event with the latest date. If that\nevent carried no readable list an older one answers, so the set can be a\nsuperseded, **wider** one — it can name a state the applicant has since dropped.\nFor a clearance call that is the dangerous direction, so read the `AK` rows in\n`events` before you flag or clear a market on the roll-up alone.\n\nDone when every survivor is both in force and designates a sales jurisdiction;\ndrop the rest.\n\n### Step 4: All-Elements Claim Mapping\n\nFor each surviving blocker, pull its claims and map product features against\nevery element of each independent claim:\n\n```bash\nflowleap --json ops claims \u003Cpatent-number>\n```\n\nFor an office with no text source, use the family-member workaround in `flowleap-shared`.\n\n**An unread claim is never a cleared claim.** A survivor at an office with no\ntext source answers `FULLTEXT_UNAVAILABLE`. When the workaround finds a served\nmember, chart from that member's claims and label the chart\n\"member text, not the office's claims\": a reading aid, not a verdict on the\noffice's right. When\nno member's text is served, carry the survivor into the deliverable as\n\"claims not readable here\", an open gap on the same footing as a missing-key\ngap: never cleared, never dropped.\n\nA claim clears only if at least one of its elements is absent from the product.\nDone when every independent claim of every survivor is either cleared (≥1 element\nabsent), flagged as a live infringement risk, or recorded as\n\"claims not readable here\".\n\n## Output\n\nFTO data package per live blocking patent:\n- Legal status (active, expired, abandoned) and remaining term\n- Geographic reach against your sales jurisdictions — family members for the\n  offices, `designatedStates` minus lapsed states for an EP filing's countries\n- Per-claim all-elements verdict: cleared or at-risk; a chart built on a\n  family member's claims carries the label\n  \"member text, not the office's claims\"; a right whose claims no source\n  serves is \"claims not readable here\", an open gap\n\nIf the full skill pack is installed, continue with `recipe-infringement-charting`\nto chart the at-risk claims element by element.\n",{"name":5,"metadata":23,"description":7},{"requires":24},{"skills":25},[26,27,28,29],"flowleap-shared","flowleap-patent","flowleap-uspto","flowleap-ops","main","83ea326400c9270816882fce38d9a026bd78d023","plugins\u002Fflowleap\u002Fskills\u002Frecipe-freedom-to-operate",0,"https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins","https:\u002F\u002Fgithub.com\u002Fflowleap-ai","2026-11-03 00:32:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add flowleap-ai\u002Fflowleap-plugins --skill recipe-freedom-to-operate",{"tool":43,"command":44},"bunx","bunx skills add flowleap-ai\u002Fflowleap-plugins --skill recipe-freedom-to-operate",{"tool":46,"command":47},"pnpm","pnpm dlx skills add flowleap-ai\u002Fflowleap-plugins --skill recipe-freedom-to-operate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fflowleap\u002Fskills\u002Frecipe-freedom-to-operate\u002FSKILL.md",true,[],[52,59,65,72,79,85],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M78F35H37QQZ9YPMHPRFTV1H","totally-different-name","This skill's frontmatter name does not match its folder 'baz-skill' and must be rejected.","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-skill-name-mismatch\u002Fplugins\u002Fbaz\u002Fskills\u002Fbaz-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M78F32ETQQ73XTJ0QQ2RTDPT","bar-skill","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-skill-missing-description\u002Fplugins\u002Fbar\u002Fskills\u002Fbar-skill\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M78F2Z98DYP2PV9Q3ATDRAAA","qux-skill","A valid skill in a plugin whose README is too short.","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-plugin-readme-short\u002Fplugins\u002Fqux\u002Fskills\u002Fqux-skill\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M78F2WEH2WYVZMMW8MHFQ8GN","grault-skill","A valid skill in a plugin whose .mcp.json server is broken.","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-mcp-server-url-scheme\u002Fplugins\u002Fgrault\u002Fskills\u002Fgrault-skill\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M78F2SY7AVXS8SM6Z33584XZ","corge-skill","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-mcp-server-no-endpoint\u002Fplugins\u002Fcorge\u002Fskills\u002Fcorge-skill\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M78F2R4APKHKDNW8MBK8M93D","quux-skill","A valid skill in a plugin whose .mcp.json is malformed.","https:\u002F\u002Fgithub.com\u002Fflowleap-ai\u002Fflowleap-plugins\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid-mcp-json\u002Fplugins\u002Fquux\u002Fskills\u002Fquux-skill\u002FSKILL.md",[],[]]