Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Zhihuiya Description

v1.0.0

通过专利ID或公开号从智慧芽专利数据库获取专利说明书(描述)数据。当用户提到专利说明书、专利全文、专利技术描述、专利实施方式详情、智慧芽说明书数据、patent specification, patent full text, technical description, embodiment details,...

0· 78·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for linkfox-ai/linkfox-zhihuiya-description.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Zhihuiya Description" (linkfox-ai/linkfox-zhihuiya-description) from ClawHub.
Skill page: https://clawhub.ai/linkfox-ai/linkfox-zhihuiya-description
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install linkfox-zhihuiya-description

ClawHub CLI

Package manager switcher

npx clawhub@latest install linkfox-zhihuiya-description
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill's stated purpose (fetch patent descriptions from Zhihuiya) matches the included code and docs: they call https://tool-gateway.linkfox.com/zhihuiya/descriptionData. However, the registry metadata declares no required environment variables or primary credential, yet both references/api.md and scripts/zhihuiya_description_data.py require an API key (LINKFOXAGENT_API_KEY). That metadata omission is an incoherence users should be aware of.
Instruction Scope
SKILL.md and the included script restrict behavior to constructing and POSTing JSON queries for patentId/patentNumber to the LinkFox tool gateway and formatting results. There is no instruction to read unrelated system files or exfiltrate arbitrary data. The docs also reference a separate feedback endpoint (https://skill-api.linkfox.com) for optional feedback submission; this is noted but not used by the main script.
Install Mechanism
This is instruction-only with an included utility script; there is no install spec or remote download. No archives or third-party package installs are performed by the skill itself, so installation risk is low.
!
Credentials
The script and API docs require an API key via the environment variable LINKFOXAGENT_API_KEY (used in Authorization header). Requesting a single service API key is proportionate to the stated function, but the skill registry metadata does not declare this required environment variable — a mismatch that could mislead users about secrets the skill needs. The API key grants access to an external service and should be disclosed in metadata and vetted by the user.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always:false). It does not attempt to modify other skills or system configuration. Autonomous invocation is enabled by default (normal) and not by itself a problem.
What to consider before installing
This skill will send patent IDs/publication numbers to an external service (tool-gateway.linkfox.com) and requires you to provide an API key in the environment variable LINKFOXAGENT_API_KEY — but the registry metadata did not list that requirement. Before installing: (1) verify you trust the LinkFox endpoints and owner (no homepage provided), (2) do not put highly sensitive credentials into the environment unless you trust the service, (3) ask the publisher to update the registry to declare LINKFOXAGENT_API_KEY and documentation about where the key comes from, and (4) consider testing in a sandbox environment and inspecting network traffic if you need stronger assurance.

Like a lobster shell, security has layers — review code before you run it.

latestvk97acb17esvw903hrmeghb80cx8424n9
78downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Zhihuiya Patent Description Data

This skill guides you on how to query patent description (specification) data from the Zhihuiya patent database, helping users retrieve the full-text description content of specific patents.

Core Concepts

A patent description (also called the specification) is the detailed technical document that accompanies a patent filing. It discloses how the invention works, preferred embodiments, and other technical details required by patent law. This tool queries the Zhihuiya database to return description data for one or more patents identified by their internal patent ID or public publication number.

Identifier priority: When both a patent ID and a publication number are provided for the same query, the patent ID takes precedence.

Family substitution: If the description for a given patent is unavailable, the tool can optionally return the description from a related family member patent instead.

Parameters

ParameterTypeRequiredDescription
patentIdstringConditionallyInternal patent ID. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100.
patentNumberstringConditionallyPublication / announcement number. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100.
replaceByRelatedstringNoWhether to substitute a family patent's description when the target patent's description is unavailable. 1 = yes, 0 = no.

Response Fields

FieldTypeDescription
totalintegerNumber of patent records returned
dataarrayList of patent description objects
data[].patentIdstringPatent ID
data[].pnstringPublication number
data[].pnRelatedstringPublication number of the substitute family patent (only present when family substitution is used)
data[].descriptionarrayDescription / specification content sections
columnsarrayColumn definitions for rendering
costTokenintegerTokens consumed by the query
typestringRendering style hint

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/zhihuiya_description_data.py directly to run queries.

How to Build Queries

Querying by Publication Number

When users provide a patent publication number (e.g., CN115099012A, US20230012345A1), pass it via the patentNumber parameter:

patentNumber: "CN115099012A"

Querying by Patent ID

When users provide internal Zhihuiya patent IDs, pass them via the patentId parameter:

patentId: "abc123def456"

Batch Queries

Both patentId and patentNumber accept comma-separated values for batch lookups (up to 100):

patentNumber: "CN115099012A,US20230012345A1,EP4123456A1"

Family Substitution

When a patent's description is not available in the database and the user still wants content, enable family substitution:

patentNumber: "CN115099012A"
replaceByRelated: "1"

Usage Examples

1. Look up a single patent description by publication number

patentNumber: "CN115099012A"

2. Look up descriptions for multiple patents at once

patentNumber: "CN115099012A,US20230012345A1"

3. Look up with family substitution enabled

patentNumber: "CN115099012A"
replaceByRelated: "1"

4. Look up by patent ID

patentId: "some-patent-id"

Display Rules

  1. Present data faithfully: Show the returned description content clearly without altering technical details or adding subjective interpretation.
  2. Structured output: When the description contains multiple sections (background, summary, detailed description, claims, etc.), present them with clear headings for readability.
  3. Family substitution notice: If the response includes a pnRelated field, explicitly inform the user that the description was sourced from a related family patent and state the substitute publication number.
  4. Batch results: When multiple patents are returned, clearly separate each patent's content with its publication number as a heading.
  5. Error handling: When a query fails or returns no data, explain the reason and suggest the user verify the patent ID or publication number.
  6. Large content warning: Patent descriptions can be very long. Summarize key sections first and offer to show the full text if the user wants it.

Important Limitations

  • Identifier requirement: At least one of patentId or patentNumber must be provided; the tool cannot search by keyword or applicant name.
  • Batch limit: A maximum of 100 patents can be queried in a single request.
  • Availability: Not all patents have descriptions available in the database. Use replaceByRelated: "1" to attempt family substitution when needed.
  • Priority rule: If both patentId and patentNumber are supplied, patentId takes precedence.

User Expression & Scenario Quick Reference

Applicable -- Queries about patent description / specification content:

User SaysScenario
"Show me the description of patent XX"Single patent description lookup
"Get the full specification for these patents"Batch patent description retrieval
"I need the detailed text of CN115099012A"Lookup by publication number
"Can you find a family patent's description instead"Family substitution query
"What does this patent describe technically"Description content review

Not applicable -- Needs beyond patent description data:

  • Patent search by keyword, applicant, or classification
  • Patent claim analysis or claim chart generation
  • Patent legal status or prosecution history
  • Patent landscape or statistical analysis
  • Freedom-to-operate or infringement opinions

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, set LinkFox Skills.

Comments

Loading comments...