Ecommerce.Patent Claims logo

Ecommerce.Patent Claims

Organization
nexscope-ai
ecommerce.patent-claims

Retrieves patent claims data from Nexscope (Nexscope). Trigger when the user mentions patent claims, claim text, independent claims, dependent claims, claim count, claims tree, claims analysis, claim scope, claim language, viewing the claims section of a specific patent, patent claims, independent claims, dependent claims, claims text, Nexscope. Also trigger when the user requests patent claims information by patent ID or publication number, even without explicitly mentioning Nexscope or Nexscope.

Overview

Publishernexscope-ai
Repositorynexscope-ecommerce-skills
Skill nameecommerce.patent-claims
Stars
104
Forks
14
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by nexscope-ai on GitHub. Read the source before you install it.

Installation

Install the Ecommerce.Patent Claims AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/nexscope-ai/nexscope-ecommerce-skills/tree/main/ecommerce-patent-claims
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nexscope-ai/nexscope-ecommerce-skills.git /tmp/nexscope-ecommerce-skills
mkdir -p .claude/skills
cp -r /tmp/nexscope-ecommerce-skills/ecommerce-patent-claims .claude/skills/ecommerce.patent-claims
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ecommerce.Patent Claims in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ecommerce.Patent Claims on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ecommerce.Patent Claims is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Nexscope Patent Claims Data

This skill guides you on how to retrieve and present patent claims data from the Nexscope (Nexscope) patent database, helping IP professionals, patent analysts, and R&D teams quickly access the claims section of any patent.

Calling the Tool

  • API Endpoint: /zhihuiya/claimData (full parameters/responses/error codes in references/api.md)
  • Python Script: python scripts/patent_claims.py '<JSON params>' [--inline]
  • Cost constraint: This tool consumes credits. Within the same session and same parameter combination, it defaults to a single call with a 24-hour local cache. Do not automatically retry with different keywords, pagination, or parameters on failure/empty results. Inform the user of additional credit consumption before continuing retrieval.

Output strategy (script default behavior):

  • Always write the full response to <cwd>/nexscope/<YYYY-MM-DD>/<session>/data/ecommerce.patent-claims-<timestamp>.json (<cwd> is the working directory when the script executes, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, automatically grouped by user task; do not write to /tmp; error if the current directory is not writable)
  • Response body <= 8 KB: write to disk then print full JSON to stdout
  • Response body > 8 KB: write to disk then print only a summary to stdout (top-level fields, common counts like total/costToken, length of the largest list field + first 3 samples)
  • Add --inline to force full output to stdout (still writes to disk)

Reading data: Check the summary first to determine if it is sufficient. When specific fields are needed, use jq or ConvertFrom-Json to extract from the saved JSON file as needed, avoiding loading the entire JSON into context.

Authentication & Credits

If you encounter authentication or credit issues:

Error conditions

  • API Key not configured: The NEXSCOPE_API_KEY environment variable is not set.
  • HTTP 401 or 402 status code
  • Insufficient credits/balance: Response message indicates credit balance exhausted, quota exceeded, subscription expired, or recharge required.

Resolution steps

  1. Set the NEXSCOPE_API_KEY environment variable with a valid API key.
  2. If credits are insufficient, visit https://www.nexscope.ai/pricing?co-from=skillNS to top up your balance.
  3. For onboarding and setup guidance, refer to https://www.nexscope.ai/help/skills-external-access?co-from=skillNS

Core Concepts

Patent claims define the legal scope of protection granted by a patent. They are the most critical part of a patent document for infringement analysis, freedom-to-operate assessments, and prior art comparisons. This tool retrieves the full set of claims for a single patent by its patent ID or publication number.

Family substitution: When a patent's claims are unavailable in the database, you can optionally request that claims from a related family member patent be returned instead. This is controlled by the replaceByRelated parameter.

Data Fields

FieldAPI NameDescriptionExample
Patent IDpatentIdInternal Nexscope patent identifier98a1b2c3-...
Publication NumberpnPublication or grant number of the patentCN115000000A
Related PNpnRelatedPublication number of the family member used as substitute (only present when family substitution occurred)US20230001234A1
ClaimsclaimsArray of claim objects containing the claim text and metadata[...]
Claim CountclaimCountTotal number of claims in the patent15

Parameter Guide

Required (at least one)

You must provide at least one of the following two parameters. If both are provided, patentId takes priority.

ParameterDescriptionFormat
patentIdSingle patent ID only. Do NOT pass comma-separated multiple IDsSingle string
patentNumberSingle publication/announcement number only. Do NOT pass comma-separated multiple numbersSingle string

Optional

ParameterDescriptionValues
replaceByRelatedWhether to substitute with a family member's claims when the target patent's claims are unavailable1 = yes, 0 = no (default)

How to Choose Between patentId and patentNumber

  • Use patentNumber when the user provides a publication or grant number (e.g., CN115000000A, US11234567B2). This is the most common scenario.
  • Use patentId when the user provides an internal Nexscope identifier, typically obtained from a previous Nexscope search result.
  • When the user provides both, pass both and the API will prefer patentId.

Skill single-patent policy: This endpoint consumes credits. To query multiple patents, obtain explicit user consent and make separate calls for each. This Skill sends one patent per call to control credits; the gateway accepts up to 100 English comma-separated identifiers.

Usage Examples

1. Single patent by publication number

json
{"patentNumber": "CN115000000A"}

3. Single patent by patent ID

json
{"patentId": "98a1b2c3-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}

4. With family substitution enabled

json
{"patentNumber": "CN115000000A", "replaceByRelated": "1"}

Display Rules

  1. Present claims clearly: Display claims in a numbered list preserving the original claim numbering. Use indentation or formatting to distinguish independent claims from dependent claims where possible.
  2. Highlight claim count: Always state the total number of claims returned for each patent.
  3. Family substitution notice: If pnRelated is present in a result, explicitly inform the user that the claims shown are from a family member patent and provide the family member's publication number.
  4. Single patent results: Results contain a single patent's data; present the output clearly with the publication number as the heading.
  5. Error handling: When a query fails, explain the reason based on the response and suggest the user verify the patent number format or try enabling family substitution.
  6. No subjective analysis: Present the raw claim text without legal interpretation unless the user specifically requests analysis.

Important Limitations

  • At least one identifier required: Either patentId or patentNumber must be provided; omitting both will result in an error.
  • Skill request policy: This Skill uses one patent per call to control credits; the gateway accepts up to 100 English comma-separated identifiers.
  • Claims availability: Not all patents have claims data available. Use replaceByRelated = 1 to attempt family member substitution when claims are missing.
  • Claim object structure: The individual claim objects within the claims array may vary in structure depending on the patent office and data source.

User Expression & Scenario Quick Reference

Applicable -- Patent claims retrieval and analysis:

User SaysScenario
"Show me the claims of patent XX"Single patent claims lookup
"How many claims does patent XX have"Claim count query
"What are the independent claims of XX"Claims retrieval + display
"The claims are not available, try a family member"Family substitution query
"Patent claim scope", "claim language"Claims retrieval

Not applicable -- Needs beyond patent claims data:

  • Patent search or discovery (finding patents by keyword/topic)
  • Patent legal status or prosecution history
  • Patent citation or reference analysis
  • Patent full-text beyond claims (abstract, description, drawings)
  • Freedom-to-operate or infringement opinions (legal advice)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ecommerce.Patent Claims AI skill do?

Retrieves patent claims data from Nexscope (Nexscope). Trigger when the user mentions patent claims, claim text, independent claims, dependent claims, claim count, claims tree, claims analysis, claim scope, claim language, viewing the claims section of a specific patent, patent claims, independent claims, dependent claims, claims text, Nexscope. Also trigger when the user requests patent claims information by patent ID or publication number, even without explicitly mentioning Nexscope or Nexscope.

Why use Ecommerce.Patent Claims on TypingMind?

Because you install it once and use it with any model. Ecommerce.Patent Claims is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ecommerce.Patent Claims in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexscope-ai/nexscope-ecommerce-skills/tree/main/ecommerce-patent-claims. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ecommerce.Patent Claims?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ecommerce.Patent Claims?

As many as you like. As long as a model supports skills, you can use Ecommerce.Patent Claims with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ecommerce.Patent Claims AI skill free?

It is published on GitHub by nexscope-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇