recipe-patent-to-report
Skill1 starsChanged 4 months agoMITView on GitHub
Formatted single-patent dossier — pull bibliography, abstract, claims, description, family, legal status, prosecution timeline, figures, and related art into one structured Markdown report. Trigger when the user asks for a complete profile, dossier, or report on a specific patent.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- flowleap-academicSkill
- flowleap-authSkill
- flowleap-citationSkill
- flowleap-keysSkill
- flowleap-legalSkill
- flowleap-nplSkill
- flowleap-opsSkill
- flowleap-patentSkill
- flowleap-patstat-graphSkill
- flowleap-patstatSkill
- flowleap-sharedSkill
- flowleapSkill
- flowleap-toolsSkill
- flowleap-usptoSkill
- persona-ip-analystSkill
- persona-patent-attorneySkill
- persona-researcherSkill
- persona-startup-founderSkill
- recipe-academic-literature-reviewSkill
- recipe-audit-reportSkill
- recipe-claim-analysisSkill
- recipe-claim-draftingSkill
- recipe-custom-dashboardSkill
- recipe-find-betterSkill
- recipe-freedom-to-operateSkill
- recipe-infringement-chartingSkill
- recipe-invalidity-analysisSkill
- recipe-invention-disclosureSkill
- recipe-maintenance-feesSkill
- recipe-office-action-responseSkill
- recipe-patent-landscapeSkill
- recipe-prior-art-searchSkill
The file
Files
Recipe: Patent to Report
Extract all data from a patent document and assemble it into one structured report.
In 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.
Steps
Step 1: One-Call Snapshot
flowleap --json summary <patent-number> # biblio + legal status + family + term
flowleap --json timeline <patent-number> # chronological prosecution eventsStep 2: Gather Full Text
flowleap --json ops abstract <patent-number>
flowleap --json ops claims <patent-number>
flowleap --json ops description <patent-number>Step 3: Figures
flowleap figures <patent-number> # figure metadata
flowleap figures <patent-number> --out figure.png --page 3 # save one pageStep 4: Find Related Patents
flowleap --json patent search --query "<key terms from abstract>" --limit 10Output
A Markdown dossier for the patent with one section per heading below. Done when every section is present (or explicitly marked "not available"):
- Bibliography — title, applicant/inventor, filing and publication dates, classification
- Abstract
- Claims — independent and dependent
- Description summary — condensed from the full description
- Figures — figure list, with saved pages referenced
- Family — members by jurisdiction
- Legal status — active/expired/abandoned and estimated remaining term
- Prosecution timeline — register + INPADOC legal events
- Related art — patents surfaced from the abstract key terms
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

