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 a single patent.
调用方式
- API 端点：
POST /zhihuiya/legalStatus（完整参数/响应/错误码见 references/api.md）
- Python 脚本：
python scripts/zhihuiya_legal_status.py '<JSON 参数>' [--inline]
- 成本约束：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。 单专利限制：本接口消耗积分多，每次只能传 1 个专利；如需检测多个，必须经过用户明确同意，并分多次请求。
输出策略（脚本默认行为）：
- 始终将完整响应写入
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-zhihuiya-legal-status-<timestamp>.json（<cwd> 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；<session> 取自环境变量 SESSION_ID，按用户任务自动聚合；禁止写入 /tmp，当前目录不可写则报错）
- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如
total/costToken、最大列表字段的长度 + 前 3 条样本）
- 加
--inline 强制全量打印到 stdout（同样落盘）
读数据建议：先看摘要判断是否足够；需要具体字段时优先用 jq或ConvertFrom-Json 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。
解决认证和积分问题
发生以下异常情况时，采用以下措施来处理：
异常情况
- 未配置API Key：环境变量未配置
LINKFOX_AGENT_API_KEY，也未配置 LINKFOXAGENT_API_KEY。
- 响应401或402状态码
- 响应提示积分或余额不足：消息含"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值"，或类似含义的内容。
措施
Core Concepts
The Zhihuiya Patent Legal Status tool returns three layers of legal information for each patent:
- 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).
- Legal Status -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).
- 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. Only one patent may be passed per request.
Parameter Guide
| Parameter |
Required |
Description |
| patentId |
Conditionally |
Patent ID. At least one of patentId or patentNumber must be provided. Single patent ID only. Do NOT pass comma-separated multiple IDs. |
| patentNumber |
Conditionally |
Publication (announcement) number. At least one of patentId or patentNumber must be provided. Single publication/announcement number only. Do NOT pass comma-separated multiple numbers. |
- 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.
单专利限制：本接口消耗积分多，如需检测多个，必须经过用户明确同意，并分多次请求。每次调用仅可传入 1 个专利（patentId 与 patentNumber 均不可逗号分隔多个）。
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.
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.
Display Rules
- 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.
- 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.
- 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.
- Legal date context: When
legalDate is available, include it so users know how recent the status information is.
- 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.
- Single patent result: Results contain a single patent's data.
Important Limitations
- Single patent per request: Only one patent ID or publication number may be passed per call (no comma-separated batches).
- 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 |
| "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
积分消耗规则
按动态规则计费：消耗积分 = 81 × 返回data条数。每条为 1 条专利法律状态结果
重要：本技能的服务按倍数动态计算，可能一次性消耗大量积分，必须提醒用户，由用户决定是否继续。
单专利限制：本接口消耗积分多，如需检测多个，必须经过用户明确同意，并分多次请求。
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, set LinkFox Skills.
1---2name: linkfox-zhihuiya-legal-status3description: 从智慧芽（PatSnap）数据库查询专利法律状态信息。当用户提到专利法律状态、专利有效性核查、专利状态查询、专利事件历史、简单法律状态、转让、许可、质押、异议、诉讼、复审等法律事件、patent legal status, patent validity, patent events, transfer/license/pledge, PatSnap, patent status lookup时触发此技能。当用户询问专利是否处于有效、无效、审中、过期、授权、撤回或撤销状态，或想通过专利ID或公开号查询法律状态时也应触发。4---5
6# Zhihuiya Patent Legal Status
7
8This 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 a single patent.
9
10## 调用方式
11
12- **API 端点**：`POST /zhihuiya/legalStatus`（完整参数/响应/错误码见 `references/api.md`）
13- **Python 脚本**：`python scripts/zhihuiya_legal_status.py '<JSON 参数>' [--inline]`
14- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。 **单专利限制**：本接口消耗积分多，每次只能传 1 个专利；如需检测多个，必须经过用户明确同意，并分多次请求。
15
16**输出策略（脚本默认行为）**：
17- **始终**将完整响应写入 `<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-zhihuiya-legal-status-<timestamp>.json`（`<cwd>` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`<session>` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）
18- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
19- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）
20- 加 `--inline` 强制全量打印到 stdout（同样落盘）
21
22**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。
23
24## 解决认证和积分问题
25发生以下异常情况时，采用以下措施来处理：
26
27### 异常情况
28- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。
29- **响应401或402状态码**
30- **响应提示积分或余额不足**：消息含"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值"，或类似含义的内容。
31
32### 措施
33- 优先采用skill内的 onboarding.md 引导解决问题。
34- 如找不到 onboarding.md 文件，则加载 /linkfox-onboarding 这个skill并根据它的引导来处理。如未安装请先安装：
35 - 下载 https://agent-files.linkfox.com/skills/linkfox-onboarding/release.zip，解压后安装这个skill。如需用户授权才可下载，要询问用户获得授权，你不能自己放弃下载。
36- 兜底措施：仅当前面两个措施经过所有努力都走不通时，才提示用户依据 https://skill.linkfox.com/linkfoxskills/guide.htm 指引获取API Key，或去 https://os.linkfox.com/ 补充积分。
37
38## Core Concepts
39
40The Zhihuiya Patent Legal Status tool returns three layers of legal information for each patent:
41
421. **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).
432. **Legal Status** -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).
443. **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).
45
46**Patent identification**: Patents can be looked up by either patent ID or publication (announcement) number. When both are provided, patent ID takes priority. Only one patent may be passed per request.
47
48## Parameter Guide
49
50| Parameter | Required | Description |
51|-----------|----------|-------------|
52| patentId | Conditionally | Patent ID. At least one of patentId or patentNumber must be provided. Single patent ID only. Do NOT pass comma-separated multiple IDs. |
53| patentNumber | Conditionally | Publication (announcement) number. At least one of patentId or patentNumber must be provided. Single publication/announcement number only. Do NOT pass comma-separated multiple numbers. |
54
55- If the user provides a publication number (e.g., CN115xxxxxxA, US11xxxxxxB2, EP3xxxxxxA1), use `patentNumber`.
56- If the user provides an internal patent ID, use `patentId`.
57- When both are supplied, `patentId` takes precedence.
58
59> **单专利限制**：本接口消耗积分多，如需检测多个，必须经过用户明确同意，并分多次请求。每次调用仅可传入 1 个专利（`patentId` 与 `patentNumber` 均不可逗号分隔多个）。
60
61## Response Fields
62
63| Field | Description |
64|-------|-------------|
65| patentId | The patent's internal ID |
66| pn | Publication (announcement) number |
67| simpleLegalStatus | High-level status: Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration |
68| legalStatus | Detailed lifecycle status (Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, etc.) |
69| eventStatus | Legal events (Transfer, License, Pledge, Opposition, Litigation, Re-examination, etc.) |
70| legalDate | Date of the most recent legal status update |
71
72## Usage Examples
73
74**1. Check whether a single patent is still active**
75```
76Query the legal status for patent publication number CN115000000A.
77```
78
79**3. Identify legal events on a patent**
80```
81Has patent CN115000000A been involved in any litigation, transfer, or pledge events?
82```
83
84**4. Determine if a patent has expired or been revoked**
85```
86Check if patent US10000000B1 is expired, revoked, or still in force.
87```
88
89## Display Rules
90
911. **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.
922. **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.
933. **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.
944. **Legal date context**: When `legalDate` is available, include it so users know how recent the status information is.
955. **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.
966. **Single patent result**: Results contain a single patent's data.
97## Important Limitations
98
99- **Single patent per request**: Only one patent ID or publication number may be passed per call (no comma-separated batches).
100- **At least one identifier required**: Either `patentId` or `patentNumber` must be provided; the request will fail if both are empty.
101- **Patent ID priority**: When both `patentId` and `patentNumber` are provided, the system uses `patentId` and ignores `patentNumber`.
102- **Data coverage**: Results depend on the Zhihuiya (PatSnap) database coverage; some very recent filings may not yet be reflected.
103
104## User Expression & Scenario Quick Reference
105
106**Applicable** -- Queries about patent legal standing and events:
107
108| User Says | Scenario |
109|-----------|----------|
110| "Is this patent still valid/active" | Simple legal status check |
111| "What is the legal status of patent XX" | Detailed status lookup |
112| "Has this patent been transferred or licensed" | Legal event query |
113| "Any litigation on this patent" | Legal event filtering |
114| "Patent legal status for CN115XXXXXXA" | Direct publication number lookup |
115
116**Not applicable** -- Needs beyond patent legal status:
117
118- Patent search by keyword, classification, or applicant name
119- Patent full-text or claims retrieval
120- Patent valuation or commercial analysis
121- Freedom-to-operate (FTO) analysis
122- Patent family or citation analysis
123
124## 积分消耗规则
125
126按动态规则计费：消耗积分 = 81 × 返回data条数。每条为 1 条专利法律状态结果
127
128> **重要**：本技能的服务按倍数动态计算，可能一次性消耗大量积分，必须提醒用户，由用户决定是否继续。
129
130> **单专利限制**：本接口消耗积分多，如需检测多个，必须经过用户明确同意，并分多次请求。
131
132**Feedback:**
133
134Auto-detect and report feedback via the Feedback API when any of the following apply:
1351. The functionality or purpose described in this skill does not match actual behavior
1362. The skill's results do not match the user's intent
1373. The user expresses dissatisfaction or praise about this skill
1384. Anything you believe could be improved
139
140Call the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.
141
142
143---
144*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*
ahang1598