← Back to Skills Marketplace
linkfox-ai

Eureka Claim Translated

by linkfox-ai · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
59
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install linkfox-eureka-claim-translated
Description
通过Eureka专利数据平台获取翻译后的专利权利要求。当用户询问专利权利要求、权利要求翻译、查看特定语言（中文、英文或日文）的权利要求、通过专利ID或公开号查询专利权利、分析权利要求文本、Eureka权利要求、claim translation, patent claim translation, Eureka...
README (SKILL.md)

Eureka Patent Claim Translation

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

  1. At least one identifier is required: You must provide either patentId or patentNumber (or both). If both are supplied, patentId takes priority.
  2. Batch queries: Multiple patents can be queried at once by separating values with commas, up to 100 per request.
  3. Default language is English: When the user does not specify a language, use en.
  4. Family fallback: Set replaceByRelated to 1 only 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

  1. 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.
  2. Family substitution notice: When pnRelated is present in the response, clearly inform the user that the claims were sourced from a related family patent and show the substitute publication number.
  3. Language notice: State the language of the returned claims so the user knows which translation they are viewing.
  4. Large results: When multiple patents are returned, summarize the count and show a few representative entries, reminding the user of the total.
  5. Error handling: When a query fails, explain the reason based on the error response and suggest checking the patent ID or publication number.

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/eureka_claim_translated.py directly to run queries.

Important Limitations

  • At least one identifier required: Either patentId or patentNumber must 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 replaceByRelated is set to 1 and 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.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. 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.

Usage Guidance
This skill appears to implement exactly what it claims (fetch translated patent claims from LinkFox), but the registry metadata failed to declare that the skill needs an API key (LINKFOXAGENT_API_KEY). Before installing: 1) Confirm you trust the provider and domain (tool-gateway.linkfox.com and skill-api.linkfox.com) and read their documentation. 2) Verify where to obtain the API key (the SKILL.md and references point to a Feishu wiki) and ensure the key has appropriate scope/limits. 3) Do not reuse high-privilege credentials; create a limited API key for this skill. 4) Ask the publisher to update the skill metadata to list LINKFOXAGENT_API_KEY as a required env var so the registry accurately reflects its needs. If you cannot verify the provider or obtain a scoped key, treat the skill as untrusted.
Capability Analysis
Type: OpenClaw Skill Name: linkfox-eureka-claim-translated Version: 1.0.0 The skill is designed to retrieve and translate patent claims from the Eureka platform using a dedicated API gateway (tool-gateway.linkfox.com). The Python script (eureka_claim_translated.py) follows standard practices for API interaction, including environment-based credential management and basic input validation, with no evidence of malicious execution, data exfiltration, or harmful prompt injection.
Capability Tags
requires-sensitive-credentials
Capability Assessment
ℹ Purpose & Capability
Name, description, SKILL.md, references/api.md, and the script all align: the skill queries LinkFox's Eureka claimDataTranslated endpoint to return translated patent claims. That capability is coherent with the stated purpose. However, the skill metadata declares no required environment variables despite the implementation requiring an API key, which is a mismatch.
✓ Instruction Scope
The SKILL.md instructs the agent to call the LinkFox tool gateway and to run the included script; it does not instruct reading unrelated files or secrets beyond the API key. It documents language/fallback rules and display/error handling. No instructions request broader system access.
✓ Install Mechanism
There is no install spec (instruction-only with one helper script). Nothing is downloaded or written during install; risk from installation is minimal.
⚠ Credentials
The implementation requires a single API key via the environment variable LINKFOXAGENT_API_KEY to authenticate requests to https://tool-gateway.linkfox.com, which is appropriate for the functionality. However, the skill's declared requirements list zero required env vars — the missing declaration is an incoherence and could lead users to inadvertently provide credentials elsewhere or miss that the skill needs an external credential. No unrelated or excessive credentials are requested.
✓ Persistence & Privilege
The skill is not marked always:true and does not request elevated/persistent platform privileges. It does perform network calls when invoked, which is expected for an API-backed skill.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install linkfox-eureka-claim-translated
  3. After installation, invoke the skill by name or use /linkfox-eureka-claim-translated
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug linkfox-eureka-claim-translated
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Eureka Claim Translated?

通过Eureka专利数据平台获取翻译后的专利权利要求。当用户询问专利权利要求、权利要求翻译、查看特定语言（中文、英文或日文）的权利要求、通过专利ID或公开号查询专利权利、分析权利要求文本、Eureka权利要求、claim translation, patent claim translation, Eureka... It is an AI Agent Skill for Claude Code / OpenClaw, with 59 downloads so far.

How do I install Eureka Claim Translated?

Run "/install linkfox-eureka-claim-translated" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Eureka Claim Translated free?

Yes, Eureka Claim Translated is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Eureka Claim Translated support?

Eureka Claim Translated is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Eureka Claim Translated?

It is built and maintained by linkfox-ai (@linkfox-ai); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463815 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259802 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200680 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191345 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190333 · by oswalpalash

💬 Comments