Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

linkfox-zhihuiya-bibliographylinkfox 智慧芽参考书目

Agent Skill

linkfox-zhihuiya-bibliography 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,521

周安装

102

GitHub Stars

公开资料未说明

下载量

792
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkfox-zhihuiya-bibliography(linkfox 智慧芽参考书目)
来源仓库:https://github.com/linkfox-ai/linkfox-zhihuiya-bibliography
安装命令:
openclaw skills install linkfox-zhihuiya-bibliography
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkfox-zhihuiya-bibliography

简介

查询智慧芽中专利的著录信息,包括申请人、发明人与分类号。

  • 提供优先权、引用关系与审查员等书目细节。
  • 适用于专利家族梳理与技术脉络分析。
  • 数据来源于第三方数据库,请核实授权状态。
  • linkfox-zhihuiya-bibliography 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
linkfox-zhihuiya-bibliography
description
通过专利ID或公开号查询智慧芽专利数据库中的专利著录(书目)信息。当用户提到专利著录信息查询、专利书目信息、专利申请人查询、专利发明人查询、专利分类号、专利摘要获取、专利引用分析、专利优先权主张、专利申请引用、专利审查员信息、patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, PatSnap, patent citations时触发此技能。即使用户未明确提及"著录信息",只要其需求涉及通过专利ID或公开号查询特定专利的详细元数据,也应触发此技能。

Zhihuiya Patent Bibliography

This skill guides you on how to query patent bibliography (bibliographic) data from the Zhihuiya patent database, helping users retrieve detailed metadata for specific patents.

Core Concepts

Patent bibliography data (also called bibliographic data) is the structured metadata associated with a patent document. It includes the patent title, applicants, inventors, classification codes, priority claims, cited references, abstracts, and more. This tool allows querying by patent ID or publication number, returning comprehensive bibliographic records for up to 100 patents per request.

Patent types: The patentType field indicates the type of patent document:

  • APPLICATION -- Invention application (published but not yet granted)
  • PATENT -- Granted invention patent
  • UTILITY -- Utility model
  • DESIGN -- Design patent

Data Fields

FieldAPI NameDescription
Patent IDpatentIdInternal patent identifier
Publication NumberpnPublication/announcement number
Invention TitleinventionTitlePatent title with language info
AbstractsabstractsPatent abstract text
Patent TypepatentTypeAPPLICATION, PATENT, UTILITY, or DESIGN
ApplicantsapplicantsOriginal applicant(s)
AssigneesassigneesCurrent patent holder(s) / assignee(s)
InventorsinventorsInventor(s) listed on the patent
AgentsagentsPatent attorney / agent(s)
AgencyagencyFiling agency / patent firm
ExaminersexaminersPatent examiner(s)
Priority ClaimspriorityClaimsPriority right declarations
Application ReferenceapplicationReferenceApplication filing data
Publication ReferencepublicationReferencePublication data
Dates of Public AvailabilitydatesOfPublicAvailabilityPublic availability dates
IPC ClassificationclassificationIpcrInternational Patent Classification
CPC ClassificationclassificationCpcCooperative Patent Classification
UPC ClassificationclassificationUpcUS Patent Classification
LOC ClassificationclassificationLocLocarno Classification (designs)
FI ClassificationclassificationFiFI classification codes (Japan)
F-term ClassificationclassificationFtermF-term codes (Japan)
GBC ClassificationclassificationGbcGBC classification
Cited PatentsreferenceCitedPatentsPatent documents cited as references
Cited Non-Patent LiteraturereferenceCitedOthersNon-patent literature cited
Related DocumentsrelatedDocumentsDivisional / continuation application info
PCT Filing DatapctOrRegionalFilingDataPCT or regional phase filing data
PCT Publishing DatapctOrRegionalPublishingDataPCT or regional phase publication data
Estimated Expiry DateexdtEstimated patent expiration date (Zhihuiya)

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

Parameter Guide

The tool accepts two parameters. At least one must be provided; if both are supplied, patentId takes priority.

ParameterWhen to UseFormat
patentIdWhen the user provides an internal Zhihuiya patent IDComma-separated string, up to 100 IDs
patentNumberWhen the user provides a publication/announcement numberComma-separated string, up to 100 numbers

Tips for Identifying Input Type

  • If the user provides something like US10123456B2, CN112345678A, EP3456789B1, or WO2023123456A1, treat it as a publication number and use patentNumber.
  • If the user provides a purely numeric or opaque identifier that does not match standard publication number patterns, treat it as a patent ID and use patentId.
  • When the user provides multiple patents, join them with commas (no spaces around commas).

Usage Examples

1. Look up a single patent by publication number

User: "Show me the bibliography for US10123456B2"
Action: Call with patentNumber = "US10123456B2"

2. Look up multiple patents by publication number

User: "Get bibliographic data for CN112345678A, EP3456789B1, and US20210012345A1"
Action: Call with patentNumber = "CN112345678A,EP3456789B1,US20210012345A1"

3. Look up a patent by internal ID

User: "Query bibliography for patent ID 8fa3b2c1-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
Action: Call with patentId = "8fa3b2c1-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

4. Batch lookup of patents

User: "I have a list of 20 publication numbers, look up all their inventors and assignees"
Action: Call with patentNumber = "<comma-separated list>"
Then extract and present inventors and assignees from the results.

Display Rules

  1. Present data clearly: Show query results in well-structured tables or organized sections. For each patent, highlight the most commonly needed fields: title, applicants/assignees, inventors, filing/publication dates, classification codes, and abstract.
  2. Respect the query scope: Only display the fields the user asked about. If they asked for "inventors", do not dump the entire bibliography unless requested.
  3. Patent type labels: Translate patentType codes into human-readable labels (APPLICATION = Invention Application, PATENT = Granted Invention, UTILITY = Utility Model, DESIGN = Design Patent).
  4. Multi-patent results: When results contain multiple patents, use a summary table first, then expand details per patent if the user wants more.
  5. Error handling: When a query returns an error or empty results, explain clearly and suggest the user verify their patent ID or publication number.
  6. No subjective analysis: Present factual bibliographic data without speculative legal or commercial interpretations.

User Expression & Scenario Quick Reference

Applicable -- Patent bibliography / metadata lookups:

User SaysScenario
"Look up patent info for XX"Single patent bibliography
"Who are the inventors of patent XX"Inventor lookup
"Who owns patent XX", "current assignee"Assignee / applicant query
"What IPC/CPC class is patent XX"Classification lookup
"Show me the abstract of patent XX"Abstract retrieval
"What patents does XX cite"Citation analysis
"When does patent XX expire"Expiry date query
"Get bibliography for these patents: A, B, C"Batch lookup
"Patent details", "patent metadata"General bibliography

Not applicable -- Needs beyond patent bibliography:

  • Full-text patent search by keyword or semantic query
  • Patent landscape / analytics reports
  • Patent valuation or legal status tracking
  • Freedom-to-operate or infringement analysis
  • Patent family tree exploration (unless specific publication numbers are given)

Boundary judgment: When users say "find patents about X" or "search for patents in field Y", that is a patent search task, not a bibliography lookup. This skill only applies when the user already has a patent ID or publication number and wants to retrieve its metadata.

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.


*For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.*

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

97.83%
按下载量换算775

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills