--- name: linkfox-zhihuiya-cited-references description: 从智慧芽专利数据库查询专利的前向引用详情。当用户询问专利引用、被引用专利、引用文献、专利参考文献、前向引用、在先技术引用或想查看特定专利在申请过程中引用了哪些专利、非专利文献、patent cited references, forward citations, patent references, citation analysis, PatSnap时触发此技能。当用户提供专利ID或公开号并需要引用信息时，即使未明确说"前向引用"，任何关于专利引用了哪些参考文献的请求都适用。 --- # Zhihuiya Patent Forward Citation This skill guides you on how to query patent forward citation data from the Zhihuiya patent database, helping users discover the patents and non-patent literature cited by specific patents during their application process. ## Core Concepts **Forward citation** refers to the patents and non-patent literature that a given patent has cited in its application documents. This is a fundamental aspect of patent analysis — understanding what prior art a patent references helps assess its novelty, scope, and technological lineage. - **Patent citations** (`citedPatents`): Other patents referenced by the queried patent. - **Non-patent literature citations** (`citedOthers`): Academic papers, technical reports, and other non-patent documents referenced by the queried patent. ## Parameter Guide You must provide at least one of the following two parameters. If both are provided, `patentId` takes priority. | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | patentId | string | Conditionally | Patent ID(s). Multiple values separated by commas. Maximum 100 entries. | | patentNumber | string | Conditionally | Publication/announcement number(s). Multiple values separated by commas. Maximum 100 entries. | **Rules**: 1. At least one of `patentId` or `patentNumber` must be provided. 2. If both are present, `patentId` is used preferentially. 3. Multiple values are separated by commas (English commas). 4. Each parameter supports up to 100 entries per request. ## Response Fields | Field | Type | Description | |-------|------|-------------| | total | integer | Total number of records returned | | data | array | List of patent citation results | | data[].patentId | string | Patent ID of the queried patent | | data[].pn | string | Publication/announcement number | | data[].citedPatents | array | List of cited patent documents | | data[].citedOthers | array | List of cited non-patent literature | | columns | array | Column definitions for rendering | | costToken | integer | Tokens consumed by the query | | type | string | Rendering 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_cited_references.py` directly to run queries. ## Usage Examples **1. Query forward citations by publication number** ``` Look up the forward citations for patent US10000000B2. ``` Parameters: `{"patentNumber": "US10000000B2"}` **2. Query forward citations for multiple patents** ``` Find all citations for patents US10000000B2, US9876543B1, and EP3456789A1. ``` Parameters: `{"patentNumber": "US10000000B2,US9876543B1,EP3456789A1"}` **3. Query forward citations by patent ID** ``` Retrieve the cited references for patent ID 12345678. ``` Parameters: `{"patentId": "12345678"}` **4. Query forward citations using both identifiers** ``` Look up citations for patent ID 12345678 (publication number US10000000B2). ``` Parameters: `{"patentId": "12345678", "patentNumber": "US10000000B2"}` (patentId takes priority) ## Display Rules 1. **Present data clearly**: Show citation results in well-structured tables, separating patent citations from non-patent literature citations. 2. **Summarize counts**: Always state the total number of cited patents and cited non-patent literature items. 3. **No fabrication**: Only display data returned by the API. Do not infer or fabricate citation details. 4. **Error handling**: When a query fails, explain the reason based on the error response and suggest the user verify their patent ID or publication number. 5. **Batch results**: When querying multiple patents, organize results by patent so each patent's citations are clearly grouped. 6. **Empty results**: If a patent has no citations, explicitly inform the user rather than showing an empty table. ## User Expression & Scenario Quick Reference **Applicable** -- Patent citation queries: | User Says | Scenario | |-----------|----------| | "What patents does XX cite" | Forward citation lookup | | "Show me the references for patent XX" | Citation detail retrieval | | "What prior art is cited by XX" | Prior art reference query | | "List the cited literature for XX" | Non-patent literature lookup | | "Citation analysis for patent XX" | Combined patent + literature citation | | "What documents does patent XX reference" | General citation query | **Not applicable** -- Needs beyond forward citation data: - Backward/reverse citations (who cites this patent) - Patent validity or legal status - Patent family analysis - Patent full-text search - Patent classification or landscape 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. ## Handling Large Responses To avoid overflowing the agent context, persist the response to disk and extract only the fields you need: ``` python scripts/response_io.py run --script scripts/zhihuiya_cited_references.py --out-dir '' python scripts/response_io.py read --fields "" # or --path "" ``` > Pick `--out-dir` outside any git working tree (e.g. `/tmp/...` on Unix, `%TEMP%/...` on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done. `run` writes the full response to a file and emits only a schema preview + file path. `read` projects specific fields, with `--limit/--offset` for slicing and `--format json|jsonl|csv|table` for output. **When to prefer this pattern** — apply your judgment based on the response characteristics, e.g.: - High field count per record, or fields you don't need - Batch/paginated results (multiple items per call) - Long-text fields (descriptions, reviews, HTML, time series) - Output reused across later steps rather than consumed immediately For small, single-use responses, calling the main script directly is fine. ⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via `read`. --- *For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*