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

Linkfox Zhihuiya Fulltext Image

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

Helps with ai & agent building tasks.

About

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

  • linkfox-zhihuiya-fulltext-image
  • AI & Agent Building
  • AI-coding skill

Linkfox Zhihuiya Fulltext Image by the numbers

  • 232 all-time installs (skills.sh)
  • +35 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #2,675 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-fulltext-image

Add your badge

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

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

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Zhihuiya Patent Fulltext Image

This skill guides you on how to retrieve fulltext images (drawings, figures, diagrams) from patent documents using the Zhihuiya patent data service, helping users access and analyze visual content within patents.

Core Concepts

Patent fulltext images are the figures, drawings, and diagrams embedded in patent documents. They are essential for understanding the technical details of an invention. This tool queries the Zhihuiya patent database and returns image metadata including download paths and image types for a given patent.

Lookup methods: You can look up images by either patent ID (an internal identifier) or publication number (the publicly visible patent number such as US20230012345A1 or CN115000000A). At least one of these must be provided.

Parameter Guide

ParameterAPI NameRequiredDescriptionExample
Patent IDpatentIdNo*Internal patent identifier8a7b6c5d-...
Publication NumberpatentNumberNo*Public patent publication/grant numberUS20230012345A1
LimitlimitNoMaximum number of images to return (max 100, default 100)50
OffsetoffsetNoPagination offset for image results0
*At least one of patentId or patentNumber must be provided.

Response Fields

FieldDescription
totalTotal number of image records available
dataArray of image entries
data[].patentIdPatent identifier
data[].pnPublication/grant number
data[].fulltextImagePathURL path to download the image
data[].imageTypeType/category of the image
columnsColumn rendering metadata
costTokenToken cost of the request
typeRendering 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_fulltext_image.py directly to run queries.

Usage Examples

1. Get all images for a patent by publication number

Retrieve fulltext images for patent US20230012345A1.

Parameters: {"patentNumber": "US20230012345A1"}

2. Get images for a patent by patent ID

Fetch the drawings for patent ID abc123def456.

Parameters: {"patentId": "abc123def456"}

3. Paginated retrieval of images

Get the first 20 images for patent CN115000000A.

Parameters: {"patentNumber": "CN115000000A", "limit": "20", "offset": "0"}

4. Get the next page of images

Get images 21-40 for patent CN115000000A.

Parameters: {"patentNumber": "CN115000000A", "limit": "20", "offset": "20"}

Display Rules

1. Present data clearly: Show image results in a structured table with image type, download path, and patent number 2. Image links: Always present fulltextImagePath values as clickable links so users can view or download images directly 3. Pagination notice: When total exceeds the number of returned results, inform the user that more images are available and offer to fetch the next page 4. Error handling: When a query fails, explain the reason and suggest verifying the patent ID or publication number 5. No fabrication: Never invent patent IDs, publication numbers, or image URLs -- only display data returned by the API 6. Total count: Always mention the total number of images available for the patent

Important Limitations

  • Image limit: Each request returns a maximum of 100 images
  • Identifier required: At least one of patentId or patentNumber must be supplied
  • All parameters are strings: Even numeric values like limit and offset must be passed as strings

User Expression & Scenario Quick Reference

Applicable -- Requests involving patent visual content:

User SaysScenario
"Show me the drawings for patent XX"Fulltext image retrieval
"Get the figures from this patent"Fulltext image retrieval
"Download patent images for XX"Fulltext image retrieval
"What diagrams does patent XX contain"Fulltext image listing
"How many figures are in patent XX"Image count query
"Show me the technical drawings"Fulltext image retrieval

Not applicable -- Needs beyond patent fulltext images:

  • Patent text/abstract/claims search
  • Patent family or citation analysis
  • Patent legal status queries
  • Patent assignee or inventor search
  • General image search unrelated to patents

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