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

Linkfox Zhihuiya Abstract Image

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

Helps with ai & agent building tasks.

About

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

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

Linkfox Zhihuiya Abstract Image by the numbers

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

Add your badge

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

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

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Zhihuiya Patent Abstract Image

This skill guides you on how to retrieve abstract images (drawings) from the Zhihuiya patent database, helping users quickly obtain the illustrative figures associated with specific patents.

Core Concepts

Abstract images (abstract drawings) are the representative figures attached to a patent document's abstract section. They provide a quick visual overview of the invention. This tool queries the Zhihuiya patent database and returns download paths for these images.

Lookup logic: You must provide at least one of two identifiers -- a patent ID or a publication number. If both are provided, patent ID takes priority. You can query up to 100 patents in a single request by separating values with commas.

Parameter Guide

ParameterAPI NameRequiredDescriptionExample
Patent IDpatentIdConditionally (one of the two must be provided)Internal patent identifier; multiple values separated by commas, max 1005e6f7a8b9c
Publication NumberpatentNumberConditionally (one of the two must be provided)Patent publication/announcement number; multiple values separated by commas, max 100CN115059423A, US11234567B2
  • At least one of patentId or patentNumber must be supplied.
  • If both are supplied, patentId takes precedence.
  • Multiple values are separated by commas (English commas), with an upper limit of 100.

Response Fields

FieldAPI NameDescription
Patent IDpatentIdThe internal patent identifier
Publication NumberpnThe publication/announcement number
Abstract Drawing PathabstractDrawingPathURL path to the abstract image file
TotaltotalTotal number of records returned
Cost TokencostTokenTokens consumed by the query

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

Usage Examples

1. Single patent lookup by publication number

Retrieve the abstract image for patent CN115059423A.

2. Multiple patents lookup by publication number

Get abstract drawings for patents US11234567B2, EP3456789A1, and CN115059423A.

3. Lookup by patent ID

Fetch the abstract image for patent ID 5e6f7a8b9c.

4. Batch lookup with mixed identifiers

I have the following patent IDs: abc123, def456. Please get their abstract images.

Display Rules

1. Show the image: When the response includes an abstractDrawingPath, display the image directly using Markdown image syntax so the user can see the drawing inline. 2. Patent identification: Always show the publication number (pn) alongside each image so the user knows which patent each drawing belongs to. 3. Missing images: If a patent has no abstract drawing (empty abstractDrawingPath), explicitly inform the user that no abstract image is available for that patent. 4. Batch results: When multiple patents are queried, present results in a clear, organized list or table format. 5. Error handling: When a query fails, explain the reason based on the response and suggest the user verify their patent IDs or publication numbers. 6. No subjective analysis: Present the retrieved images and metadata without adding subjective patent analysis or legal interpretations.

User Expression & Scenario Quick Reference

Applicable -- Patent abstract image retrieval:

User SaysScenario
"Show me the abstract image for patent XX"Single patent image lookup
"Get the drawings for these patents"Batch patent image lookup
"What does the patent figure look like"Abstract drawing retrieval
"Retrieve patent illustrations for XX"Image download path retrieval
"I need the abstract drawing for publication number XX"Lookup by publication number

Not applicable -- Needs beyond abstract image retrieval:

  • Full patent text or claims analysis
  • Patent search by keyword or classification
  • Patent legal status or family information
  • Patent citation or prior art analysis
  • Patent valuation or infringement 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_abstract_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.