- Home
- Skills
- Legal & Compliance
- Patent Claims Drafting
More screenshots
Works with the AI Agents you already use
Patent Claims Drafting
Turn an invention disclosure into a claim set: extract the inventive concept, build the claim tree broad to narrow, keep antecedent basis airtight, in US, EP, or CN style.
$5
Patent Claims Drafting
Example session with this skill installed
Draft a claim set for this disclosure: a garden irrigation valve that waters only when needed. It has a soil moisture sensor in the ground, a small controller, and a low-power radio that receives a local rain forecast twice a day. The controller opens the valve only if soil moisture is below a threshold AND the forecast says no significant rain in the next 24 hours. If the radio link fails, it falls back to moisture-only decisions. A solar cell keeps a battery charged. Target: US filing, apparatus and method claims.
- Read your context and instructions
- Compiled the patent claims drafting
Inventive concept: gating irrigation on a conjunction — measured soil moisture below threshold AND a received forecast of no significant rain within a forward window — so the valve skips watering that rainfall would have made wasted, decided locally at the valve. Core: moisture sensor, forecast receiver, controller applying the two-condition gate. Supporting: radio-failure fallback to moisture-only control, forecast window, threshold adaptation. Context: the valve, the solar cell and battery (known elements — not the novelty).
Claim 1 (apparatus): "An irrigation control device comprising: a valve configured to control water flow to an irrigation zone; a soil moisture sensor configured to measure moisture of soil in the zone; a radio receiver configured to receive a precipitation forecast; and a controller configured to open the valve only when the measured moisture is below a threshold and the received forecast indicates precipitation below a predetermined amount within a following 24-hour period."
Claim 2 (dependent — the most valuable fallback): "The device of claim 1, wherein the controller is further configured to, upon failing to receive the forecast for a predetermined interval, open the valve based on the measured moisture alone."
Claim 3 (dependent): "The device of claim 1, wherein the threshold is adjusted based on a history of the received forecasts and the measured moisture."
Claim 4 (method, mirrors claim 1): "A method of controlling irrigation, comprising: measuring soil moisture in an irrigation zone; receiving a precipitation forecast via a radio receiver; determining that the measured moisture is below a threshold and that the forecast indicates precipitation below a predetermined amount within a following 24-hour period; and opening a valve in response to the determining."
Self-attack, abbreviated: design-around test — a competitor using a wired forecast feed avoids "radio receiver"; that element is embodiment detail, so claim 1 should be broadened to "forecast receiver" with the radio pushed to a dependent. Noted for the next draft; solar power stays out of the independents — context, not the fence.
Connects securely to your tools. The creator never sees your data.
About this skill
In a patent, the claims are the property lines — a beautiful specification with badly drawn claims protects nothing. This skill drafts claim sets that are broad enough to matter and precise enough to survive examination. It starts where most drafting goes wrong: before any claim is written, you state the inventive concept in one paragraph (what does the prior art not do?) and sort every feature into core, supporting, and context piles. Claims protect the core; refinements become dependent claims; known elements stay in preambles. The claim tree is built broad to narrow, with at least two independent claims in different categories — a method claim and an apparatus claim that mirror each other step for component — and dependent claims layered from most to least commercially valuable as fallback positions. The language rules that prevent mechanical rejections are enforced throughout: antecedent basis (a/an first, the after), one term per element used identically everywhere, structure and steps instead of result language, open transitions unless closure is deliberate. Jurisdiction dialects are handled from the start — US open style and means-plus-function caution, EP and CN two-part form with the preamble/characterizing split matched to your feature sort. Finally, the skill attacks its own output with four tests: prior-art, design-around, clarity (read it aloud), and specification support. A claim-set template, an eight-item drafting checklist, and a claim-quality rubric for grading claim 1 are included.
- It is a drafting method, not legal advice; a registered patent attorney or agent should review any claim set before filing.
- It does not perform a prior-art search — the prior-art test runs against references you already know.
- Patentability outcomes depend on the actual prior art and the examining office, which no drafting method can guarantee.
- Jurisdiction coverage is US, EP, and CN practice at the drafting-convention level, not jurisdiction-specific legal counsel.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected