Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Zhihuiya Cited References

  • 161 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Helps with ai & agent building tasks.

About

linkfox-zhihuiya-cited-references is a Claude Code skill in the AI & Agent Building category.

  • linkfox-zhihuiya-cited-references
  • AI & Agent Building
  • AI-coding skill

Linkfox Zhihuiya Cited References by the numbers

  • 161 all-time installs (skills.sh)
  • Ranked #3,231 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-zhihuiya-cited-references

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs161
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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.

ParameterTypeRequiredDescription
patentIdstringConditionallyPatent ID(s). Multiple values separated by commas. Maximum 100 entries.
patentNumberstringConditionallyPublication/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

FieldTypeDescription
totalintegerTotal number of records returned
dataarrayList of patent citation results
data[].patentIdstringPatent ID of the queried patent
data[].pnstringPublication/announcement number
data[].citedPatentsarrayList of cited patent documents
data[].citedOthersarrayList of cited non-patent literature
columnsarrayColumn definitions for rendering
costTokenintegerTokens consumed by the query
typestringRendering 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 SaysScenario
"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.

<!-- 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_references.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/).

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.