Zhihuiya Legal Status

从智慧芽（PatSnap）数据库查询专利法律状态信息。当用户提到专利法律状态、专利有效性核查、专利状态查询、专利事件历史、简单法律状态、转让、许可、质押、异议、诉讼、复审等法律事件、patent legal status, patent validity, patent events, transfer/lice...

Security Scan

The skill's code and docs require an API key (LINKFOXAGENT_API_KEY) and call external LinkFox endpoints, but the registry metadata does not declare any required credentials — this mismatch is incoherent and needs clarification before trusting the skill.

Purpose & Capability

The skill's stated purpose (querying Zhihuiya/PatSnap legal status) aligns with the included code and API references, but the registry metadata lists no required environment variables or primary credential while both the script and the API reference require LINKFOXAGENT_API_KEY. That missing declaration is inconsistent with the claimed capability.

Instruction Scope

SKILL.md and references/api.md describe calling https://tool-gateway.linkfox.com/zhihuiya/legalStatus with an Authorization header and give display/error-handling guidance. The runtime instructions and included script are narrowly scoped to sending patentId/patentNumber to that endpoint and returning results; they do not instruct reading unrelated files or exfiltrating other environment variables. However, the docs also reference a separate feedback endpoint (https://skill-api.linkfox.com) — the script does not call it, but the presence of a second external endpoint should be noted.

Install Mechanism

No install spec and the included Python script uses only stdlib modules. Nothing is downloaded or written to disk during install, so install risk is low.

Credentials

The code and API docs require an API key via the environment variable LINKFOXAGENT_API_KEY and will send it as an Authorization header to an external service. The registry metadata, however, declares no required env vars or primary credential — this omission is disproportionate and misleading. Requiring a single API key for remote queries would be reasonable, but the metadata should declare it explicitly. Users should verify the key's scope and revocability before supplying it.

Persistence & Privilege

always is false and the skill does not attempt to alter system or other-skill configuration. It does not request permanent persistence or elevated privileges.

What to consider before installing

Before installing: 1) Ask the publisher to update the skill metadata to explicitly list LINKFOXAGENT_API_KEY as a required credential (the code and API docs use it). 2) Verify you trust the domains tool-gateway.linkfox.com and skill-api.linkfox.com and confirm how to obtain the API key (the docs point to an internal Feishu wiki). 3) Only provide an API key with the minimal scope and one you can revoke; avoid putting high-privilege or shared credentials into the environment. 4) If you need higher assurance, request a publisher identity/homepage and provenance for this skill (who operates linkfox), or run the skill in an isolated environment. 5) Confirm whether the skill will (or may later be modified to) call the feedback endpoint or other external services and whether any user data will be retained or logged externally.

Zhihuiya Patent Legal Status

This skill guides you on how to query patent legal status information via the Zhihuiya (PatSnap) platform, helping users quickly determine the current legal standing and event history of one or more patents.

Core Concepts

The Zhihuiya Patent Legal Status tool returns three layers of legal information for each patent:

1. Simple Legal Status -- A high-level summary of the patent's current standing (e.g., Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration).
2. Legal Status -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).
3. Legal Events -- Specific legal actions that have occurred on the patent (e.g., Transfer, License, Pledge, Opposition, Litigation, Re-examination, Customs, Preservation, Invalid-procedure, Oral-procedure, Declassification, Double application, Trust).

Patent identification: Patents can be looked up by either patent ID or publication (announcement) number. When both are provided, patent ID takes priority. Multiple values can be submitted in a single request (comma-separated, up to 100).

Parameter Guide

Parameter	Required	Description
patentId	Conditionally	Patent ID. At least one of patentId or patentNumber must be provided. Comma-separated for multiple values, up to 100.
patentNumber	Conditionally	Publication (announcement) number. At least one of patentId or patentNumber must be provided. Comma-separated for multiple values, up to 100.

• If the user provides a publication number (e.g., CN115xxxxxxA, US11xxxxxxB2, EP3xxxxxxA1), use patentNumber.
• If the user provides an internal patent ID, use patentId.
• When both are supplied, patentId takes precedence.

Response Fields

Field	Description
patentId	The patent's internal ID
pn	Publication (announcement) number
simpleLegalStatus	High-level status: Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration
legalStatus	Detailed lifecycle status (Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, etc.)
eventStatus	Legal events (Transfer, License, Pledge, Opposition, Litigation, Re-examination, etc.)
legalDate	Date of the most recent legal status update

Usage Examples

1. Check whether a single patent is still active

Query the legal status for patent publication number CN115000000A.

2. Batch-check legal status for multiple patents

Look up the legal status for patents US11000000B2, EP3000000A1, and CN115000001A.

3. Identify legal events on a patent

Has patent CN115000000A been involved in any litigation, transfer, or pledge events?

4. Determine if a patent has expired or been revoked

Check if patent US10000000B1 is expired, revoked, or still in force.

5. Look up patents by patent ID

Query the legal status for patent IDs abc123, def456.

Display Rules

1. Present data clearly: Show results in a structured table. Include the publication number, simple legal status, detailed legal status, and legal events for each patent.
2. Translate status values: When the user's language preference is clear, present status labels in that language while keeping the canonical English value in parentheses for precision.
3. Highlight key findings: If the user is checking validity, prominently state whether each patent is Active, Inactive, or Pending at the top of the response.
4. Legal date context: When legalDate is available, include it so users know how recent the status information is.
5. Error handling: If the query fails or returns no results, explain the possible reasons (invalid patent number format, patent not found in database) and suggest the user double-check the input.
6. Volume notice: When querying many patents, present a summary table and note the total count returned.

Important Limitations

• Up to 100 patents per request: The maximum number of patent IDs or publication numbers in a single call is 100.
• At least one identifier required: Either patentId or patentNumber must be provided; the request will fail if both are empty.
• Patent ID priority: When both patentId and patentNumber are provided, the system uses patentId and ignores patentNumber.
• Data coverage: Results depend on the Zhihuiya (PatSnap) database coverage; some very recent filings may not yet be reflected.

User Expression & Scenario Quick Reference

Applicable -- Queries about patent legal standing and events:

User Says	Scenario
"Is this patent still valid/active"	Simple legal status check
"What is the legal status of patent XX"	Detailed status lookup
"Has this patent been transferred or licensed"	Legal event query
"Check if these patents are expired"	Batch validity check
"Any litigation on this patent"	Legal event filtering
"Patent legal status for CN115XXXXXXA"	Direct publication number lookup

Not applicable -- Needs beyond patent legal status:

• Patent search by keyword, classification, or applicant name
• Patent full-text or claims retrieval
• Patent valuation or commercial analysis
• Freedom-to-operate (FTO) analysis
• Patent family or citation analysis

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.