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

Linkfox Zhihuiya Simple Bibliography

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

Format Zhihuiya patent and IP search results into clean bibliographies for prior-art memos, diligence packets, and research appendices.

About

Linkfox skill that turns Zhihuiya patent and IP intelligence lookups into simple, consistently formatted bibliographies for research reports, prior-art reviews, and diligence documentation.

  • Zhihuiya IP source integration
  • Structured bibliography output
  • Prior-art research support
  • Agent-friendly citation workflow
  • Report-ready reference formatting

Linkfox Zhihuiya Simple Bibliography by the numbers

  • 234 all-time installs (skills.sh)
  • +35 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #489 of 1,879 Documentation 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-simple-bibliography

Add your badge

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

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

What it does

Format Zhihuiya patent and IP search results into clean bibliographies for prior-art memos, diligence packets, and research appendices.

Files

SKILL.mdMarkdownGitHub ↗

Zhihuiya Patent Simple Bibliography

This skill guides you on how to query simple bibliographic data for patents using the Zhihuiya patent database, helping users retrieve structured patent metadata efficiently.

Core Concepts

The Zhihuiya Simple Bibliography tool retrieves basic bibliographic (front-page) information for patents. Given one or more patent IDs or publication numbers, it returns structured metadata including title, abstract, applicants, inventors, assignees, classification codes, filing dates, priority claims, and citation references.

Lookup modes: You can look up patents by either patentId (Zhihuiya internal patent ID) or patentNumber (public publication/grant number). If both are supplied, patentId takes priority. Multiple values are separated by commas, with a maximum of 100 per request.

Parameter Guide

ParameterTypeRequiredDescription
patentIdstringConditionallyZhihuiya internal patent ID. Comma-separated for multiple values, max 100. At least one of patentId or patentNumber must be provided.
patentNumberstringConditionallyPublic publication/grant number (e.g., US11234567B2, CN115000000A). Comma-separated for multiple values, max 100. At least one of patentId or patentNumber must be provided.

Priority rule: When both patentId and patentNumber are present, the API uses patentId and ignores patentNumber.

Response Data Fields

FieldAPI NameDescription
Patent IDpatentIdZhihuiya internal patent identifier
TitletitlePatent title
AbstractabstractContentPatent abstract text
Publication NumberpublicationNumberPublication number
Publication/Grant NumberpnFull publication/grant number
Country CodecountryCountry code of the patent
Publication CountrypublicationCountryCountry where the patent was published
Publication DatepublicationDatePublication date
Publication KindpublicationKindKind code of the publication
Patent TypepatentTypeType of patent (e.g., invention, utility model, design)
Kind CodekindPatent kind code
Application NumberapplicationNoApplication number
Application DateapplicationDateApplication filing date
ApplicantsapplicantsList of applicants
InventorsinventorsList of inventors
AssigneesassigneesList of patent assignees/owners
Assignee AddressesassigneeAddressesList of assignee addresses
IPC MainipcMainMain IPC classification code
IPC FurtheripcFurtherAdditional IPC classification codes
CPC MaincpcMainMain CPC classification code
CPC FurthercpcFurtherAdditional CPC classification codes
LOClocLocarno classification codes (design patents)
GBCgbcGBC classification codes
Priority ClaimspriorityClaimsList of priority claim entries
PCT Application NopctApplicationNoPCT international application number
PCT Filing DatepctFilingDatePCT international filing date
PCT Entry DatepctEntryDatePCT national phase entry date
Cited PatentscitedPatentsList of cited patent references
Cited Non-PatentscitedNonPatentsList of cited non-patent literature

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_simple_bibliography.py directly to run queries.

Usage Examples

1. Look up a single patent by publication number

User: "Show me the bibliographic info for patent US11234567B2."
Action: Call with patentNumber = "US11234567B2"

2. Look up multiple patents by publication number

User: "Get the basic info for CN115000000A, EP4000000A1, and JP2023100000A."
Action: Call with patentNumber = "CN115000000A,EP4000000A1,JP2023100000A"

3. Look up patents by Zhihuiya patent ID

User: "Retrieve bibliography for patent IDs abc123 and def456."
Action: Call with patentId = "abc123,def456"

4. Retrieve inventor and applicant information

User: "Who are the inventors and applicants for patent US20230001234A1?"
Action: Call with patentNumber = "US20230001234A1", then extract the inventors and applicants fields from the response.

5. Check patent classification codes

User: "What IPC and CPC codes does patent EP3999999B1 have?"
Action: Call with patentNumber = "EP3999999B1", then present ipcMain, ipcFurther, cpcMain, and cpcFurther from the response.

6. Get patent abstract and citation references

User: "Show me the abstract and cited patents for CN114000000B."
Action: Call with patentNumber = "CN114000000B", then display abstractContent and citedPatents.

Display Rules

1. Present data clearly: Show bibliographic results in well-structured tables or grouped sections. For a single patent, use a key-value layout. For multiple patents, use a table with the most relevant columns. 2. Selective display: When results contain many fields, prioritize showing title, publication number, applicants, inventors, application date, publication date, IPC/CPC main codes, and abstract. Show additional fields only when the user specifically asks. 3. List fields: For array fields (inventors, applicants, assignees, classification codes, citations), present them as comma-separated values or bulleted lists depending on length. 4. Empty fields: Omit fields that are null or empty from the display rather than showing blank entries. 5. Error handling: When a query fails, explain the reason based on the error message and suggest the user verify the patent number or ID format. 6. Batch result notice: When querying many patents at once, remind the user that the maximum is 100 per request.

Important Limitations

  • Maximum batch size: Up to 100 patent IDs or publication numbers per request.
  • At least one identifier required: Either patentId or patentNumber must be provided; omitting both will cause an error.
  • patentId takes priority: If both parameters are supplied, only patentId is used.
  • Data scope: This tool returns simple bibliographic data only. It does not return full-text claims, detailed descriptions, legal status, or patent family information.

User Expression & Scenario Quick Reference

Applicable -- Patent bibliographic data retrieval:

User SaysScenario
"Look up patent XX" / "Get info for patent XX"Single patent bibliography lookup
"Who invented patent XX" / "Who is the applicant"Inventor / applicant retrieval
"What's the IPC code for XX" / "Classification of XX"Classification code lookup
"Show me the abstract of XX"Abstract retrieval
"When was patent XX filed" / "Publication date of XX"Date information lookup
"What patents does XX cite"Citation reference lookup
"Get bibliographic data for these patents: A, B, C"Batch bibliography query
"Patent basic info" / "Patent front page data"General bibliography retrieval

Not applicable -- Needs beyond simple bibliographic data:

  • Full-text patent claims or detailed description
  • Patent legal status or prosecution history
  • Patent family / equivalents analysis
  • Patent valuation or landscaping
  • Freedom-to-operate or infringement analysis
  • Patent search by keyword or semantic query (this tool requires specific patent identifiers)

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

Documentationresearchautomation

This week in AI coding

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

unsubscribe anytime.