---
name: linkfox-zhihuiya-cited-by
description: 从智慧芽（PatSnap）查询专利被引用数据，包括被引用次数和引用专利详情。当用户提到专利被引用、被引分析、专利影响力、引用频次、专利家族被引、前向引用、想了解哪些专利引用了某一专利、patent citations, citation count, patent influence, citation analysis, PatSnap时触发此技能。即使用户未明确提及"智慧芽"或"PatSnap"，只要其需求涉及查询某专利被引用次数或被哪些专利引用，也应触发此技能。
---

# Zhihuiya Patent Citations Explorer

This skill guides you on how to query patent citation data from Zhihuiya (PatSnap), helping users understand the citation landscape of specific patents.

## Core Concepts

Patent citation analysis reveals how influential a patent is within its technology domain. When Patent B references Patent A in its prior art section, Patent A is said to be "cited by" Patent B. A higher citation count generally indicates greater technological significance and broader industry influence.

**Key metrics**:
- **3-year citations** (`citedBy3y`): Number of times the patent was cited within 3 years of publication. Indicates early-stage impact.
- **5-year citations** (`citedBy5y`): Number of times the patent was cited within 5 years. Indicates medium-term influence.
- **Simple family citations** (`citedBySimpleFamily`): Count of simple patent family members that cite the patent.
- **INPADOC family citations** (`citedByInpadocFamily`): Count of INPADOC patent family members that cite the patent.
- **PatSnap family citations** (`citedByPatsnapFamily`): Count of PatSnap-defined patent family members that cite the patent.

## Parameter Guide

You must provide at least one of the following identifiers. If both are supplied, patent ID takes priority.

| Parameter | Description | Example |
|-----------|-------------|---------|
| patentId | Zhihuiya internal patent ID. Multiple IDs separated by commas (max 100). | abc123def456 |
| patentNumber | Publication / announcement number. Multiple numbers separated by commas (max 100). | US10123456B2, CN112345678A |

**Important**: At least one of `patentId` or `patentNumber` is required. When the user provides a publication number (e.g., "US10123456B2"), use `patentNumber`. When they provide internal IDs, use `patentId`.

## Usage Examples

**1. Single patent citation lookup by publication number**
Query: "How many citations does patent US10123456B2 have?"
```json
{
  "patentNumber": "US10123456B2"
}
```

**2. Multiple patents citation comparison**
Query: "Compare citations for CN112345678A and CN113456789B"
```json
{
  "patentNumber": "CN112345678A,CN113456789B"
}
```

**3. Lookup by patent ID**
Query: "Get citation data for patent ID abc123def456"
```json
{
  "patentId": "abc123def456"
}
```

**4. Batch query with multiple IDs**
Query: "Citation info for these patent IDs: id001, id002, id003"
```json
{
  "patentId": "id001,id002,id003"
}
```

## Display Rules

1. **Present data in tables**: Show citation results in clear, structured tables. Include the publication number, 3-year citations, 5-year citations, and family citation counts.
2. **Highlight key metrics**: When comparing multiple patents, highlight the one with the highest citation counts.
3. **Explain family types**: If the user is unfamiliar with patent families, briefly explain the difference between Simple, INPADOC, and PatSnap family definitions.
4. **Citing patent details**: If the response includes a `citedByPatents` array with details of citing patents, present them in a sub-table or expandable list.
5. **Error handling**: When a query fails, explain the reason based on the response and suggest checking whether the patent number or ID is correct.
6. **No subjective advice**: Present factual citation data without making judgments about patent value or investment decisions.
## 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_by.py` directly to run queries.

## User Expression & Scenario Quick Reference

**Applicable** -- Patent citation analysis scenarios:

| User Says | Scenario |
|-----------|----------|
| "How many times has this patent been cited" | Basic citation count |
| "Which patents cite this one" | Citing patent list |
| "Patent influence analysis" | Citation-based impact |
| "Compare citations between patents" | Multi-patent comparison |
| "3-year / 5-year citation count" | Time-windowed citation metrics |
| "Patent family citation data" | Family-level citation analysis |
| "Forward citations for patent X" | Synonym for cited-by lookup |

**Not applicable** -- Needs beyond patent citation data:
- Patent full-text search or semantic search
- Patent legal status or prosecution history
- Patent valuation or licensing recommendations
- Backward citations (references *made by* a patent)


**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.

<!-- LF_LARGE_RESPONSE_BLOCK -->
## 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_by.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
```

> 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`.
<!-- /LF_LARGE_RESPONSE_BLOCK -->

---
*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*