What makes 睿观-实用新型专利检测 notable?

1K downloads. Trust evidence available

How should 睿观-实用新型专利检测 be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

睿观-实用新型专利检测

基于产品信息检测和搜索相似的实用新型/发明专利。当用户提到实用新型专利检测、专利侵权风险、专利相似度搜索、专利排查、发明专利查询、专利风险评估、TRO（临时限制令）风险分析、utility patent, invention patent detection, patent infringement risk, patent search, TRO risk, Ruiguan时触发此技能。即使用户未明确说"实用新型专利"，只要其需求涉及在目标市场销售前检查产品是否可能侵犯已有的实用新型/发明专利，也应触发此技能。 Skill: 睿观-实用新型专利检测 Owner: linkfox-ai Summary: 基于产品信息检测和搜索相似的实用新型/发明专利。当用户提到实用新型专利检测、专利侵权风险、专利相似度搜索、专利排查、发明专利查询、专利风险评估、TRO（临时限制令）风险分析、utility patent, invention patent detection, patent infringement risk, patent search, TRO risk, Ruiguan时触发此技能。即使用户未明确说"实用新型专利"，只要其需求涉及在目标市场销售前检查产品是否可能侵犯已有的实用新型/发明专利，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:23:48.606Z | user Update from 1.0.6 to 1.0.7 v1.0.6 | 2

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

1.0.7

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.7release · observed Sep 14, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-ruiguan-utility-patent-detection

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-ruiguan-utility-patent-detection/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

105,331 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: linkfox-ruiguan-utility-patent-detection
description: 基于产品信息检测和搜索相似的实用新型/发明专利。当用户提到实用新型专利检测、专利侵权风险、专利相似度搜索、专利排查、发明专利查询、专利风险评估、TRO（临时限制令）风险分析、utility patent, invention patent detection, patent infringement risk, patent search, TRO risk, Ruiguan时触发此技能。即使用户未明确说"实用新型专利"，只要其需求涉及在目标市场销售前检查产品是否可能侵犯已有的实用新型/发明专利，也应触发此技能。
---

# Ruiguan Utility Patent Detection

This skill guides you on how to search for similar utility (invention) patents based on a product's title, description, and target selling region. It helps cross-border e-commerce sellers identify potential patent infringement risks before listing products.

## Core Concepts

**Utility patent** (also called invention patent) protects new and useful inventions or functional improvements. Unlike design patents that protect appearance, utility patents protect how a product works, its structure, or its composition. Infringing on a utility patent can lead to product removal, lawsuits, or TRO orders.

**Similarity score**: Each returned patent includes a `similarity` field (0 to 1). A higher value means the patent is more closely related to the queried product. Patents with high similarity scores deserve careful review.

**TRO risk indicators**: Two boolean fields flag enforcement history:
- `troCase` -- whether the patent has a history of TRO enforcement actions
- `troHolder` -- whether the patent holder is known for initiating TRO cases

Patents flagged with either indicator require extra caution.

**Patent validity**: The `patentValidity` field shows whether a patent is `Active` or `Invalid`. Only active patents pose infringement risk.

## Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| productTitle | string | Yes | Product title (max 1000 characters) |
| productDescription | string | Yes | Product description (max 1000 characters) |
| region | string | Yes | Target selling country/region code, comma-separated for multiple. Currently supports: US. Default: `US` |
| topNumber | integer | Yes | Number of patent results to return. Range: 10--200. Default: `100` |

### Parameter Guidelines

1. **productTitle**: Use the product's actual listing title or a concise descriptive title. Be specific rather than generic -- "portable USB-C fast charger 65W" is better than "charger".
2. **productDescription**: Include key features, materials, mechanisms, and technical attributes. The more detail provided, the more accurate the similarity matching.
3. **region**: Currently only `US` is supported. Always set to `US` unless the user specifies otherwise.
4. **topNumber**: Default is 100. Increase to 200 for a broader search when doing thorough patent clearance. Decrease to 10--20 for a quick preliminary scan.

## 调用方式

- **API 端点**：`POST /ruiguan/utilityPatentDetection`（完整参数/响应/错误码见 `references/api.md`）
- **Python 脚本**：`python scripts/ruiguan_utility_patent_detection.py '<JSON 参数>' [--inline]`
- **成本约束**：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得

_meta.json

{
  "ownerId": "kn7dmc1t4j28hem1twwyav85p182pb1j",
  "slug": "linkfox-ruiguan-utility-patent-detection",
  "version": "1.0.7",
  "publishedAt": 1789363428606
}

references/api.md

# 睿观-发明专利检测 API 参考

## 调用规范

- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/ruiguan/utilityPatentDetection`
- **请求方式**：POST，Content-Type: application/json
- **认证方式**：Header `Authorization: <api_key>`，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和算力问题** 处理）

## 请求参数

POST Body（JSON）：

| 参数 | 类型 | 必填 | 说明 |
|------|------|------|------|
| productTitle | string | 是 | 产品标题，最大1000字符 |
| productDescription | string | 是 | 产品描述，最大1000字符 |
| region | string | 是 | 商品想要售卖的国家/地区代码，多个用逗号分隔，当前支持 US。默认 `US` |
| topNumber | integer | 是 | 召回数量，范围：10--200，默认 `100` |


## 响应结构

| 字段 | 类型 | 说明 |
|------|------|------|
| total | integer | 记录数 |
| detectId | string | 检测ID |
| costToken | integer | 消耗token |
| type | string | 渲染的样式 |
| columns | array | 渲染的列定义 |
| data | array | 专利列表（详见下方） |

### 专利对象字段

| 字段 | 类型 | 说明 |
|------|------|------|
| globalUtilityId | string | 专利ID |
| title | string | 发明专利标题 |
| titleCn | string | 发明专利标题（中文） |
| similarity | number | 产品与该专利的相似度（0--1） |
| patentValidity | string | 专利有效性：`Active`（有效）或 `Invalid`（无效） |
| applicationNumber | string | 申请号 |
| applicationDate | string | 申请日（yyyy-MM-dd） |
| publicationNumber | string | 公开号 |
| publicationDate | string | 公开日（yyyy-MM-dd） |
| estimatedDueDate | string | 预估到期日（yyyy-MM-dd） |
| region | string | 受理局 |
| patentAbstract | string | 摘要 |
| patentAbstractCn | string | 摘要（中文） |
| claims | string | 权利要求 |
| claimsCn | string | 权利要求（中文） |
| specification | string | 说明书 |
| specificationCn | string | 说明书（中文） |
| inventors | array | 发明家和国家拼接，数组格式 |
| inventorAddresses | array | 发明人地址，数组格式 |
| applicants | array | 申请人和国家拼接，数组格式 |
| applicantAddresses | array | 权利人地址，数组格式 |
| priorityNumber | array | 优先权号，数组格式 |
| relatedPublicationDate | array | 首次公开日（yyyy-MM-dd），数组格式 |
| patentImageUrl | string | 专利封面图 |
| images | array | 专利附图 |
| classNumList | array | 类别号路径列表，格式：classNum1 > classNum2 > classNum3 |
| cpcKindRaw | array | CPC分类（原始 JSONArray） |
| troCase | boolean | 是否有TRO维权史 |
| troHolder | boolean | 是否是TRO权利人的专利 |

## 错误码

正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。

| errcode | 含义 | 处理建议 |
|---------|------|----------|
| 200 | 成功 | 正常解析业务字段 |
| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和算力问题** 处理。 |
| 402 | 算力或余额不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和算力问题** 处理。 |
| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |

错误响应示例：

```json
{
    "errcode": 401,
    "errmsg": "authorized error"
}
```

## curl 示例

```bash
curl -X POST https://tool-gateway.linkfox.com/ruiguan/utilityPatentDetection \
  -H "Authorization: $LINKFOXAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"productTitle": "便携式USB-C 65W氮化镓快充充电器", "productDescription": "一款紧凑型65W氮化镓USB-C快充充电器，配备可折叠插脚，支持PD3.0和QC4.0协议，双USB-C端口和一个USB-A端口，适用于笔记本电脑、手机和平板电脑。", "region": "US", "topNumber": 100}'
```

---

## Feedback API

> This endpoint is **separate** from the tool API above. Do not mix the

references/onboarding.md

# 解决认证和算力问题

调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。

**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。
1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册
2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册
3. 手机号路径：
   - `python scripts/onboarding.py send-code <phone>` → 展示 JSON 里的 phone/agreements
   - 收到验证码后：`python scripts/onboarding.py login <phone> <code>`
   - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：
     - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY "<key>"`
     - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.zshrc && source ~/.zshrc`
     - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.bashrc && source ~/.bashrc`
     - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可

**billing 场景**：`errcode=402` 或消息含 `算力/余额/quota/insufficient/充值/套餐到期`。
- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选
- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）
- `python scripts/onboarding.py order <plan_id> <method>` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）
- 已付款可选调 `python scripts/onboarding.py query <order_id>`，不主动轮询

排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。

skill-card.md

## Description:

Searches for similar US utility and invention patents from product information to help cross-border e-commerce sellers review patent and TRO risk before listing.

This skill is ready for commercial/non-commercial use.

## Publisher:

[linkfox-ai](https://clawhub.ai/user/linkfox-ai)

### License/Terms of Use:

MIT-0

## Use Case:

External sellers and their agents use this skill to check product titles and descriptions against similar US utility or invention patents before selling. It helps prioritize patent records for review, highlight TRO indicators, and avoid presenting similarity results as legal conclusions.

### Deployment Geography for Use:

Global; patent search coverage is currently limited to US patents.

## Known Risks and Mitigations:

Risk: Product descriptions, patent-query context, API credentials, and session metadata may be sent to LinkFox services.

Mitigation: Use the skill only with approved data, avoid confidential pre-launch product details without approval, and store API keys in a secure secret manager or environment configuration.

Risk: Endpoint override environment variables can redirect credential-bearing requests.

Mitigation: Use default LinkFox endpoints unless the override target is fully controlled and trusted.

Risk: Billing and payment actions may consume credits or create orders.

Mitigation: Review plan, payment method, and order details before paying; require user confirmation before additional high-cost calls.

Risk: Patent similarity results can be mistaken for legal advice or a definitive infringement determination.

Mitigation: Present results factually, distinguish active from invalid patents, and recommend patent-attorney review for legal conclusions.

Risk: Complete API responses are automatically persisted in the working directory.

Mitigation: Keep the workspace access-controlled and remove saved patent-search outputs when they are no longer needed.

## Reference(s):

- [ClawHub Skill Page](https://clawhub.ai/linkfox-ai/skills/linkfox-ruiguan-utility-patent-detection)
- [API Reference](references/api.md)
- [Authentication and Billing Onboarding](references/onboarding.md)
- [Ruiguan Utility Patent Detection API](https://tool-gateway.linkfox.com/ruiguan/utilityPatentDetection)

## Skill Output:

**Output Type(s):** [text, markdown, JSON, shell commands, configuration, guidance]

**Output Format:** [Markdown guidance with patent-result tables, shell commands, and JSON API responses saved to local files.]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Full API responses are persisted under the working directory; large responses may be summarized unless inline output is requested.]

## Skill Version(s):

1.0.7 (source: server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and co

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.