Patent Claim Analysis

    1

    Splits patent claims, charts every limitation against what you build, and names the cheapest design-around.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Patent Claim Analysis

    Example session with this skill installed

    Analyze US7979296B2. Compare it against a new ticket system that has a GUI and a store but only syncs to one legacy database on a single fixed schedule. Give me a design-around.

    • Read your context and instructions
    • Compiled the patent claim analysis

    Patent US7979296B2: 20 claims total, 2 independent claims.

    Element Chart: Claim 1

    #Claim element (verbatim, shortened)Accused featureStatusNote
    1work item storage holding tasks from a workflow processticket storeliteralsame function
    2GUI presenting items and accepting inputdashboard GUIliteral
    3interface accepting items from a plurality of independent providersAPI connectorsliteral
    4item type registry tracking handling by typemetadata tagsequivalentcheck if it tracks handling logic
    5custom attribute retriever, staggered sync across two legacy systems with independent timingsingle fixed syncabsentsystem uses one source and one timing

    Verdict

    Claim 1 is not infringed. Element 5 is a conjunctive requirement for "two legacy systems" and "staggered sync," both of which are absent in the accused product. Since Claim 1 is the independent parent, the narrower dependent claims (2-20) are also not infringed by this specific architecture.

    Design-Around Recommendations

    Maintain Single-Source Sync: The simplest defense is to avoid adding a second legacy source. The claim specifically requires "two legacy systems."
    2.

    Unified Timing: If a second source is added, use a global synchronization clock rather than "independent timing per connector."
    3.

    Change Preamble Subject: Move the sync logic to a stateless worker that does not qualify as a "computer readable medium" as defined in the preamble.

    Next steps

    • Verify if the "metadata tags" in the accused feature truly function as a "type registry."
    • Document the single-source architecture in the technical specification as a conscious design choice.
    • Note that this analysis lacks prosecution history and does not constitute legal advice.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most patent tools summarise the abstract. The abstract does not decide anything. The claims do.

    This skill reads a patent the way it has to be read. It fetches the text from Google Patents, separates independent from dependent claims, identifies the transitional phrase that controls scope (comprising is open, consisting of is closed), and turns every limitation into a row you can answer: literal, equivalent, or absent.

    What you get back

    • Claim count and how many are independent. The fastest read on how narrow the patent really is.
    • One element chart per independent claim, with the element, your feature, and a status you can defend.
    • A verdict tied to specific rows, not to the abstract.
    • A design-around list ordered by cost, from "leave out the missing element" to "licence it".
    • For EPO two-part claims, the split between what the applicant conceded was known and what is actually being claimed as new.

    It also handles the job people confuse with this one: extracting the architecture a patent teaches, including the stated alternatives in the description that almost nobody reads.

    Two scripts, no dependencies

    Python standard library only. Nothing to install.

    • patent_fetch.py makes one read-only request to patents.google.com and saves the HTML plus plain text.
    • claims_split.py parses US, EP and WO/OCR claim markup into JSON: number, dependencies, transitional phrase, preamble, limitations.

    Tested against granted US patents (US7979296B2, 20 claims), US applications (US20220237532A1, 9 claims), EPO two-part claims (EP1000000A1, 11 claims) and OCR'd WIPO filings (WO2014152996A1, 13 claims).

    Why not just prompt it yourself

    A generic prompt anchors on the title and the abstract, which carry no legal weight, and it silently skips limitations. The failure mode is confident and wrong. This skill forces the limitations-first order and refuses to conclude before the chart exists.

    Known limits

    No prosecution history, no jurisdiction-specific doctrine, no legal opinion. It is the technical analysis an attorney wants on the table before the conversation starts, not a replacement for one.

    Built by the author of patent-research-mcp, the open-source MCP server for the same pipeline. If you already run it, the skill tells the agent when and how to drive it.

    No prosecution history or file wrapper analysis. Not a substitute for a patent attorney. Requires patent numbers or Google Patents URLs.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    python3

    Permissions

    Terminal / Shell
    Network Access
    Write Files
    Read Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill performs a granular technical breakdown of patent claims into individual limitations, allowing you to map specific product features against the 'legal fence' of a patent to identify design-arounds. Unlike generic summaries, it focuses on the literal architecture and technical requirements that define infringement.

    The package includes the core analysis logic, a structured reporting framework, and the `patent_fetch.py` script for automated data retrieval. You also receive documentation for integrating the optional `patent-research-mcp` server for high-volume workflows.

    Yes, while it includes a Python script for automation, you can manually input claims and product specs through any LLM interface that supports file uploads or long-form text processing. The skill is optimized for agents that can execute Python code for the most efficient parsing.

    The skill analyzes the 'four corners' of the patent document, including the claims and technical description, but it does not account for the prosecution history (file wrapper) or external legal precedents. It is designed as a technical engineering tool, not a substitute for a legal opinion from a qualified patent attorney.

    This skill is highly effective for Freedom-to-Operate (FTO) screenings, as it uses 'element charting' to determine if your product lacks at least one limitation of an independent claim—the key to avoiding literal infringement.

    New in Technical Documentation