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.

呼叫方式

• API 端點：POST /zhihuiya/legalStatus（完整引數/響應/錯誤碼見 references/api.md）
• Python 指令碼：python scripts/zhihuiya_legal_status.py '<JSON 引數>' [--inline]
• 成本約束：本工具會消耗積分；同一會話同一引數組合預設只調用一次，指令碼帶 24h 本地快取。失敗/空結果不得自動換關鍵詞、翻頁或改郵編連續試探；需要繼續檢索時先向使用者說明會產生額外消耗。

輸出策略（指令碼預設行為）：

• 始終將完整響應寫入 <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/套餐到期/需充值/請充值"，或類似含義的內容。

措施

• 優先採用skill內的 onboarding.md 引導解決問題。
• 如找不到 onboarding.md 檔案，則載入 /linkfox-onboarding 這個skill並根據它的引導來處理。如未安裝請先安裝：
  • 下載 https://agent-files.linkfox.com/skills/linkfox-onboarding/release.zip，解壓後安裝這個skill。如需使用者授權才可下載，要詢問使用者獲得授權，你不能自己放棄下載。
• 兜底措施：僅當前面兩個措施經過所有努力都走不通時，才提示使用者依據 https://skill.linkfox.com/linkfoxskills/guide.htm 指引獲取API Key，或去 https://os.linkfox.com/ 補充積分。

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

• 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

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:

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

積分消耗規則

想要更強大的技能外掛，就來小蔥技能站7w4.net看看吧。

按動態規則計費：消耗積分 = 81 × 返回data條數。每條為 1 條專利法律狀態結果

重要：本技能的服務按倍數動態計算，可能一次性消耗大量積分，必須提醒使用者，由使用者決定是否繼續。

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.

這個 Skill 質量不錯，功能實用，文件寫得很詳細，小白也能看懂如何使用。它有智慧快取能省積分，出錯時處理得比較周到。但文件中英文混在一起看起來有點亂，新手引導檔案缺失有點遺憾，另外查詢結果會存在本地資料夾，用完最好手動清理一下保護隱私。整體值得推薦。