How do I install the Recipe Claim Analysis skill?

Run npx skillmds@latest add flowleap-ai/recipe-claim-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Recipe Claim Analysis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Recipe Claim Analysis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Recipe Claim Analysis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Recipe Claim Analysis?

flowleap-ai (@flowleap-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Recipe Claim Analysis by flowleap-ai

Name: Recipe Claim Analysis
Author: flowleap-ai

Recipe Claim Analysis

Decompose a patent's claims into elements, keywords, and search queries with full supporting context — claims text, abstract, bibliography, description, and family. Trigger when the user asks to analyze what a patent claims, break claims into elements, or interpret claim scope against its specification.

flowleap-ai Updated Sep 17, 2026

File contents

Recipe: Claim Analysis

Extract a patent's claims with full context, then decompose them into elements.

Steps

Step 1: Extract Claims

flowleap --json ops claims <patent-number>

Done when you have the full claim set, independent claims identified.

Step 2: Get Context

flowleap --json ops abstract <patent-number>
flowleap --json ops biblio <patent-number>
flowleap --json ops description <patent-number>

Step 3: Check Related Patents

flowleap --json ops family <patent-number>

Step 4: Decompose Every Independent Claim — Yourself

There is no backend claim analyzer: you do the decomposition, one independent claim at a time.

Split the claim into preamble, transition (comprising / consisting of), and body. Element boundaries fall at the semicolons and at wherein / configured to clauses.
Keep the claim language verbatim per element — paraphrase in a second column if useful, but the verbatim text is what later maps against prior art. Tag each element structural or functional.
Derive keywords and synonyms per element from the element's own nouns, checking the description (Step 2) for the applicant's own alternative wording — the specification is the claim's dictionary.
Write a search query per key element combination with the self-written query method in flowleap-patent (extract terms, discriminating term, count probe). The element pairs, not single elements, usually carry the discrimination.

Repeat for every independent claim. For each dependent claim, note how it narrows its parent (the added element). Done when every independent claim has an element breakdown and each dependent claim's added limitation is recorded.

Output

Complete claim data with supporting context:

Full claims text (independent and dependent)
Abstract, bibliographic data, and description for interpretation
Family members for jurisdiction coverage
Element breakdown (verbatim language, structural/functional tag, keywords) and self-written follow-up search queries per independent claim, plus the narrowing limitation added by each dependent claim

---name: recipe-claim-analysisdescription: Decompose a patent's claims into elements, keywords, and search queries with full supporting context — claims text, abstract, bibliography, description, and family. Trigger when the user asks to analyze what a patent claims, break claims into elements, or interpret claim scope against its specification.---# Recipe: Claim AnalysisExtract a patent's claims with full context, then decompose them into elements.## Steps### Step 1: Extract Claims```bashflowleap --json ops claims <patent-number>```Done when you have the full claim set, independent claims identified.### Step 2: Get Context```bashflowleap --json ops abstract <patent-number>flowleap --json ops biblio <patent-number>flowleap --json ops description <patent-number>```### Step 3: Check Related Patents```bashflowleap --json ops family <patent-number>```### Step 4: Decompose Every Independent Claim — YourselfThere is no backend claim analyzer: you do the decomposition, one independentclaim at a time.1. **Split the claim** into preamble, transition (`comprising` / `consisting of`), and body. Element boundaries fall at the semicolons and at `wherein` / `configured to` clauses.2. **Keep the claim language verbatim per element** — paraphrase in a second column if useful, but the verbatim text is what later maps against prior art. Tag each element structural or functional.3. **Derive keywords and synonyms per element** from the element's own nouns, checking the description (Step 2) for the applicant's own alternative wording — the specification is the claim's dictionary.4. **Write a search query per key element combination** with the self-written query method in `flowleap-patent` (extract terms, discriminating term, count probe). The element pairs, not single elements, usually carry the discrimination.Repeat for every independent claim. For each dependent claim, note how itnarrows its parent (the added element). Done when every independent claim has anelement breakdown and each dependent claim's added limitation is recorded.## OutputComplete claim data with supporting context:- Full claims text (independent and dependent)- Abstract, bibliographic data, and description for interpretation- Family members for jurisdiction coverage- Element breakdown (verbatim language, structural/functional tag, keywords) and self-written follow-up search queries per independent claim, plus the narrowing limitation added by each dependent claim

Frequently asked questions