agentsclimarketplace

Recipe invention disclosure

Skill flowleap-ai/flowleap-plugins/plugins/flowleap/skills/recipe-invention-disclosure

Prosecution recipe for turning an inventor conversation into a complete invention disclosure form (IDF) — structured technical capture, bar-date audit, novelty pre-check across patents and literature, landscape context, and a filing recommendation. Trigger when the user asks to document an invention, create an invention disclosure, or run a pre-filing novelty sanity check.From its SKILL.md

Install
npx -y skills add flowleap-ai/flowleap-plugins --skill recipe-invention-disclosure

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 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.

SKILL.md

2.9 KB, 578 tokens by cl100k_base, as published. Nobody here has run it

Recipe: Invention Disclosure (IDF)

Capture an invention completely enough that an attorney can draft from it.

Step 1: Structured Capture

Interview for these sections (push past marketing language to mechanisms):

  1. Problem — what fails today, and why existing approaches fall short
  2. Prior approaches — what the inventors know exists, including their own earlier work
  3. The inventive concept — the mechanism of the solution, not the benefit
  4. Key elements — minimum set needed for the invention to work
  5. Variations — alternative embodiments, ranges, materials, algorithms
  6. Evidence — prototypes, test data, figures
  7. People and dates — inventors and contribution; conception date; any public disclosure, sale, offer, or publication with dates (bar dates differ by jurisdiction — flag anything older than 12 months)

Step 2: Novelty Pre-Check

flowleap patent build-query "<inventive concept in plain language>" --allow-external-processing
flowleap --json patent search --query "<generated CQL>" --limit 20
flowleap --json uspto search --query "<generated CQL>" --limit 20   # ODP Lucene syntax

# Literature — inventors' own field publishes here first
flowleap --json academic search "<concept keywords>" --limit 15
flowleap --json npl "<concept keywords>" --limit 10

For anything close, pull claims and record how the invention differs:

flowleap --json ops claims <close-patent>

This is a sanity check, not a legal search — say so in the IDF.

Step 3: Landscape Context

flowleap --json analytics --keyword "<technology>" --date-from 2018-01-01

Filing trends and top assignees tell the reviewer whether this space is crowded, growing, or abandoned — context for the filing decision.

Step 4: Assemble the IDF

Sections: title; inventors + contributions; problem; prior approaches (including Step 2 findings with the differences recorded); detailed description of the inventive concept; key elements; variations; evidence; disclosure/bar-date audit; landscape summary.

Step 5: Recommendation

Close with one of: file now (novelty check clean, bar clock running), develop further (concept not yet enabled), or defensive publication (crowded space, low claim scope) — with the reasoning.

Output

A complete IDF document plus the raw novelty pre-check data (queries used, hits reviewed, differences noted) as an appendix.

What ships with it

Read from the repository

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

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.