This skill guides you on how to query translated patent claims from the Eureka patent data platform, enabling users to retrieve claim texts in Chinese, English, or Japanese for one or more patents.
Core Concepts
Patent claims define the legal scope of protection granted by a patent. This tool retrieves the translated text of patent claims from the Eureka platform, supporting three languages: Chinese (cn), English (en), and Japanese (jp). You can look up patents by their internal patent ID or by their publication (announcement) number.
Family patent substitution: When claims are unavailable for a specific patent, the tool can optionally substitute claims from a related family patent. This is controlled by the replaceByRelated parameter.
Parameter Guide
| Parameter | Type | Required | Description |
|---|---|---|---|
| patentId | string | At least one of patentId or patentNumber | Internal patent ID. Separate multiple IDs with commas. Up to 100 patents per request. |
| patentNumber | string | At least one of patentId or patentNumber | Publication (announcement) number. Separate multiple numbers with commas. Up to 100 patents per request. |
| replaceByRelated | integer | No | Whether to substitute claims from a family patent when unavailable. 1 = yes, 0 = no. Default 0. |
| lang | string | No | Target translation language. en = English (default), cn = Chinese, jp = Japanese. |
Key Rules
- At least one identifier is required: You must provide either
patentIdorpatentNumber(or both). If both are supplied,patentIdtakes priority. - Batch queries: Multiple patents can be queried at once by separating values with commas, up to 100 per request.
- Default language is English: When the user does not specify a language, use
en. - Family fallback: Set
replaceByRelatedto1only when the user explicitly wants substitute claims from a family patent if the original is missing.
Response Fields
| Field | Description |
|---|---|
| total | Number of patent records returned |
| data | Array of patent objects (see below) |
| data[].patentId | Internal patent ID |
| data[].pn | Publication (announcement) number |
| data[].claims | Translated patent claims text |
| data[].pnRelated | Publication number of the substitute family patent (only present when family substitution was used) |
| costToken | Tokens consumed by this request |
Usage Examples
1. Get English claims for a single patent by publication number
Show me the English claims for patent CN112345678A.
Parameters: patentNumber = "CN112345678A", lang = "en"
2. Get Chinese claims for multiple patents
Get the Chinese translation of claims for US20210012345A1 and EP3456789B1.
Parameters: patentNumber = "US20210012345A1,EP3456789B1", lang = "cn"
3. Get Japanese claims with family patent fallback
Get Japanese claims for JP2021123456A. If unavailable, try a family patent.
Parameters: patentNumber = "JP2021123456A", lang = "jp", replaceByRelated = 1
4. Query by patent ID
Get claims for patent ID 84a1b2c3 in English.
Parameters: patentId = "84a1b2c3", lang = "en"
5. Batch query with fallback enabled
Translate claims for these patents: CN112345678A, US20200012345A1, EP3456789B1. Use family patents if needed.
Parameters: patentNumber = "CN112345678A,US20200012345A1,EP3456789B1", lang = "en", replaceByRelated = 1
Display Rules
- Present claims clearly: Show the translated claim text with proper formatting. If multiple patents are returned, separate each patent's claims with its publication number as a heading.
- Family substitution notice: When
pnRelatedis present in the response, clearly inform the user that the claims were sourced from a related family patent and show the substitute publication number. - Language notice: State the language of the returned claims so the user knows which translation they are viewing.
- Large results: When multiple patents are returned, summarize the count and show a few representative entries, reminding the user of the total.
- Error handling: When a query fails, explain the reason based on the error response and suggest checking the patent ID or publication number.
How to Call
- API Endpoint：
POST /tool-eureka/claimDataTranslated(For complete parameters/responses/error codes, seereferences/api.md） - Python Script：
python scripts/eureka_claim_translated.py '<JSON 参数>' [--inline] - Cost Constraints: This tool consumes credits; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the postal code to probe continuously; if you need to continue searching, first explain to the user that additional consumption will be incurred.
Output Strategy (Script Default Behavior)：
- Alwayswrite the complete response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-eureka-claim-translated-<timestamp>.json（<cwd>is the working directory when the script is executed, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;Writing to /tmp is prohibited, and if the current directory is not writable, report an error) - Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
- Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, length of the largest list field + first 3 samples) - Add
--inlineto force full printing to stdout (also written to disk)
Data Reading Suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.
Resolve Authentication and Credit Issues
When the following abnormal situations occur, take the following measures to handle them:
Abnormal Situation
- API Key not configured: The environment variable is not configured
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient credits or balance: The message contains "insufficient credit balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.
Measures
- Prefer using onboarding.md within the skill to guide problem resolution.
- If the onboarding.md file cannot be found, load the /linkfox-onboarding skill and handle it according to its guidance. If not installed, please install it first:
- Fallback measure: only when all efforts with the previous two measures have failed, prompt the user to follow the https://skill.linkfox.com/linkfoxskills/guide.htm guidance to obtain an API Key, or go to https://os.linkfox.com/ to add credits.
Important Limitations
- At least one identifier required: Either
patentIdorpatentNumbermust be provided; otherwise the query will fail. - Batch limit: A maximum of 100 patents per request.
- Language support: Only Chinese (
cn), English (en), and Japanese (jp) are supported. - Family substitution: Substitute claims are only returned when
replaceByRelatedis set to1and the original claims are unavailable. - No claim analysis: This tool returns raw translated text only; it does not analyze or compare claims.
User Expression & Scenario Quick Reference
Applicable -- Queries related to patent claim text and translation:
| User Says | Scenario |
|---|---|
| "Show me the claims for patent XX" | Single patent claim lookup |
| "Translate claims to Chinese/Japanese" | Claim translation |
| "What does patent XX claim?" | Claim content retrieval |
| "Get claims for these patents: XX, YY" | Batch patent claim lookup |
| "Claims unavailable, try family patent" | Family patent substitution |
| "Patent rights scope of XX" | Claim text retrieval |
Not applicable -- Needs beyond patent claim translation:
- Patent search or discovery (finding patents by keyword)
- Patent citation or legal status analysis
- Patent abstract or description retrieval
- Patent portfolio analytics or statistics
Boundary -- Edge cases:
- If the user asks for "patent text" without specifying claims, clarify whether they want claims, abstract, or description.
- If the user provides more than 100 patents, split into multiple batches.
Credit Consumption Rules
Billed according to dynamic rules: credits consumed = 81 × max(number of returned items, 1).
Important: The services of this skill are dynamically calculated by a multiplier and may consume a large number of credits at once. The user must be reminded, and the user decides whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.