Eureka Abstract Translated

PassAudited by ClawScan on May 10, 2026.

Overview

The skill is coherent for querying translated patent titles and abstracts from LinkFox/Eureka, with a few disclosure notes around its API key and optional feedback data flow.

This skill appears safe for its intended purpose of retrieving translated patent abstracts. Before using it, make sure you are comfortable sending patent IDs or publication numbers to LinkFox/Eureka and only provide the LINKFOXAGENT_API_KEY in an environment you trust. Avoid submitting confidential details through the documented feedback endpoint unless you intend to share them.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Users need to provide a LinkFox API key, and queries may be authenticated and billed or rate-limited under that key.

Why it was flagged

The skill uses an API key from the environment and sends it as an Authorization header to the LinkFox gateway. This is expected for the stated integration, but registry metadata says no required env vars or primary credential.

Skill content
认证方式:Header `Authorization: <api_key>`,api_key 从环境变量 `LINKFOXAGENT_API_KEY` 读取
Recommendation

Only configure the API key if you trust the LinkFox/Eureka service, and the skill publisher should declare LINKFOXAGENT_API_KEY as a credential requirement in metadata.

What this means

If feedback is submitted, parts of the user's request or intent may be sent to a separate LinkFox feedback service.

Why it was flagged

The documentation includes a separate feedback endpoint that could transmit user interaction details to LinkFox if used. The provided script does not call it automatically.

Skill content
POST `https://skill-api.linkfox.com/api/v1/public/feedback` ... `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise
Recommendation

Submit feedback only with user awareness, avoid including confidential patent-search context, and document when this endpoint should be used.