Token导航 LogoToken导航

Agent Skill · 研究检索

hiarthur(hiarthur 搜索)

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

hiarthur 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 16,528。

总安装 7,128周安装 297GitHub Stars 1下载 2,376核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.0.2

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install hiarthur

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

搜索亚马逊产品并分析材料、设计和评论,以发现权衡和可能的失望。在交互式 GUI 中查看结果。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install hiarthur;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

hiarthur 怎么安装?

在终端执行 openclaw skills install hiarthur。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

hiarthur 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

hiarthur 需要什么权限?

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

hiarthur 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

hiarthur 用的人多吗?

公开数据是累计安装 7,128 次,近一周安装 297 次,下载 2,376 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

hiarthur 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
hiarthur

hiarthur 搜索 · 本页

7,1281需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
hiarthur
description
Search Amazon products and analyze materials, design, and reviews to uncover trade-offs and likely disappointments. See results in an interactive GUI.

HiArthur Product Search and Understanding

Overview

Two-endpoint API for intelligent product search and deep product analysis. Products are sourced from Amazon, but results go far beyond what Amazon returns directly — every product is analyzed through a multi-stage pipeline combining computer vision, LLMs, and symbolic reasoning to evaluate how well each product actually matches what the user is looking for and where it's likely to disappoint.

  • POST https://hiarthur.com/api/agents/search — find products matching a query. Each result is graded for fit against the user's requirements using vision + language models, not just keyword matching.
  • POST https://hiarthur.com/api/agents/product — deep-dive one product for failure-mode analysis (FMEA), feature summary, and review synthesis. Uses LLM reasoning over product details and images to surface likely disappointments.

Base URL: https://hiarthur.com/api

Results can optionally be handed off to a GUI (e.g. https://hiarthur.com/c/<conversation_id> or https://hiarthur.com/product/f7e2a9c1b3d4) where users can browse results visually and continue the conversation interactively.


When to Use This Skill

Use this skill when you need to:

  • Find products that match detailed user requirements
  • Evaluate trade-offs between competing products
  • Identify likely durability or design problems
  • Understand why a product might disappoint buyers
  • Compare products beyond simple ratings or keywords

Quick-Start: End-to-End Flow

Step 1 — Start a new search

POST /api/agents/search

{
  "type": "new",
  "search_query": "noise cancelling headphones for travel",
  "search_top_brands": true
}

Response:

{
  "conversation_id": "a1b2c3d4-...",
  "logical_search_id": "ls_abc123",
  "products": [
    {
      "product": {
        "description": "Sony WH-1000XM5 Wireless Noise Canceling Headphones",
        "brand": "Sony",
        "location": "product/f7e2a9c1b3d4",
        "price": 328.0,
        "rating": 4.6,
        "reviews_count": 12450
      },
      "explainer": "Strong noise canceling with long battery life, well suited for travel.",
      "match_grade": "Excellent"
    }
  ],
  "can_fetch_more": true
}

Step 2 — Fetch more results (pagination)

Reuse conversation_id and logical_search_id exactly as returned.

POST /api/agents/search

{
  "type": "continue",
  "conversation_id": "a1b2c3d4-...",
  "logical_search_id": "ls_abc123"
}

Repeat while can_fetch_more is true. A continue response with products: [] is valid (more may come on the next continue). Stop when can_fetch_more is false.

Step 3 — Deep-dive a product

Use a product.location value exactly as returned by search.

POST /api/agents/product

{
  "location": "product/f7e2a9c1b3d4"
}

Response:

{
  "fmea": {
    "unmitigated_failure_modes": [
      {
        "failure_name": "Headband cushion flattens over time",
        "likelihood": {
          "level": "medium",
          "reasoning": "Foam compression builds with daily wear, so most regular users will notice reduced comfort within months."
        },
        "impact": "annoying",
        "timeline": "within_a_year",
        "summary": "The headband padding can compress with regular use, making the headphones less comfortable for long listening sessions.",
        "evidence": [
          "Foam headband cushion visible in images",
          "No mention of memory foam or replaceable pads"
        ]
      }
    ],
    "mitigated_failure_modes": [
      {
        "failure_name": "Poor noise canceling on wind",
        "ownership_experience": "Multipoint wind-noise reduction",
        "reasoning": "Multiple microphones and adaptive ANC algorithms reduce wind interference compared to single-mic designs.",
        "evidence": [
          "Adaptive ANC with multiple external microphones",
          "Wind noise reduction mode listed in features"
        ]
      }
    ],
    "quality_summary": "These headphones prioritize audio quality and noise canceling performance. Most disappointment comes from comfort degradation over time rather than core functionality."
  },
  "features_summary": "Paragraph summarizing key product features based on listing data.",
  "reviews_summary": "Paragraph synthesizing themes and patterns from customer reviews."
}

Search Endpoint — Full Field Reference

New Search (type: "new")

Full example with all optional fields:

{
  "type": "new",
  "search_query": "noise cancelling headphones for travel",
  "search_top_brands": true,
  "trim_query": "Over-ear wireless headphones with active noise canceling and long battery life for airplane use",
  "brands": ["Sony", "Bose"],
  "search_filters": {
    "price_min": 100,
    "price_max": 400,
    "rating_min": 4.0,
    "reviews_min": 500
  },
  "search_sort": "relevance"
}
FieldTypeRequiredDefaultDescription
type"new"yes—Discriminator.
search_querystringyes—Broad retrieval query sent to the product catalog. Should be precise, user-intent-aligned, and include all key attributes (color, size, material, use case, gender).
search_top_brandsbooleanyes—When true, restricts results to recognized top brands in the category. Default to true for electronics, appliances, clothing, tools, beauty, home/kitchen. Default to false for books, media.
trim_querystringnosame as search_querySimilarity-trimming query. After retrieval, products with low similarity to this string are removed. Should be a fluent, attribute-rich, natural-language description optimized for matching product titles and images. More descriptive than search_query. See examples below.
conversation_idUUID stringnoserver-generatedOmit to let the server create a new conversation. Supply to attach this search to an existing conversation.
brandsstring[]no[]Explicit brand-name constraints. Only populate when the user names specific brands. Use canonical names with proper capitalization (e.g., ["Nike", "Adidas"]).
search_filtersobjectnonullAll sub-fields optional and nullable: price_min (number), price_max (number), rating_min (number), reviews_min (integer). No extra keys allowed.
search_sortenum stringnonull"relevance", "price_low", "price_high", or "best_sellers".
search_query vs trim_query

search_query drives broad catalog retrieval. trim_query is applied after retrieval as a similarity filter — products with low similarity to it are removed.

trim_query should read like a grounded, attribute-rich product description:

  • "A men's sleeveless hooded vest made of shiny metallic fabric with a full zipper front."
  • "A 12-pack of chocolate-flavored protein shakes, each bottle containing 20 grams of protein."
  • "A thick purple yoga mat made of dense non-slip foam, measuring one inch in thickness."
  • "A 10-inch nonstick frying pan with a ceramic coating and induction-compatible base."
  • "Wireless Bluetooth 5.3 earbuds with noise-canceling features and at least 40 hours of battery life."

When omitted, trim_query defaults to search_query. Only set it when you have a more descriptive version.

Continue Search (type: "continue")

FieldTypeRequiredDescription
type"continue"yesDiscriminator.
conversation_idUUID stringyesExact value from the prior search response.
logical_search_idstringyesExact value from the prior search response.

Search Response

{
  "conversation_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "logical_search_id": "ls_abc123",
  "products": [
    {
      "product": {
        "description": "Sony WH-1000XM5 Wireless Noise Canceling Headphones",
        "brand": "Sony",
        "location": "product/f7e2a9c1b3d4",
        "price": 328.0,
        "rating": 4.6,
        "reviews_count": 12450
      },
      "explainer": "Strong noise canceling with long battery life, well suited for travel.",
      "match_grade": "Excellent"
    }
  ],
  "can_fetch_more": true
}
FieldTypeDescription
conversation_idstringStable conversation identifier. Reuse for continue requests and frontend handoff.
logical_search_idstringIdentifies this search session for pagination. Reuse for continue requests.
productsarrayProductWithExplainer objects. May be empty (valid on continue).
can_fetch_morebooleanThe only pagination signal. true = more results available via continue.

Each products[] entry:

FieldTypeDescription
product.descriptionstringProduct title/description.
product.brandstring or nullBrand name if known.
product.locationstringOpaque product identifier (format: product/<cache_key>). Preserve exactly for /agents/product calls and frontend handoff.
product.pricenumber or nullPrice in dollars.
product.ratingnumber or nullStar rating (e.g., 4.6).
product.reviews_countinteger or nullNumber of customer reviews.
explainerstringHuman-readable rationale for the fit grade. May be empty.
match_gradestringCanonical fit label. One of: "Excellent", "Good", "Partial", "Low".

Match Grade Semantics

GradeMeaning
ExcellentAll user requirements confirmed by evidence. All numeric constraints pass.
GoodAll critical requirements confirmed, none contraindicated. Constraints pass or pass within tolerance.
PartialAt least one critical requirement is unconfirmed, missing, or contraindicated, OR some numeric constraints fail.
LowAny requirement is contraindicated, OR no requirements could be evaluated.

Product Endpoint — Deep Analysis

Request

{ "location": "product/<cache_key>" }

Use only a location value returned by /api/agents/search. Never invent locations. Request model uses extra = "forbid".

Response

FieldTypeDescription
fmeaobjectFailure Mode and Effects Analysis. See structure below.
features_summarystringParagraph summarizing key product features.
reviews_summarystringParagraph synthesizing themes from customer reviews.

FMEA Structure

The fmea object describes how a product is likely to disappoint a buyer over time, framed as failure modes rather than feature ratings.

unmitigated_failure_modes — array, typically 3 entries, ordered by expected regret impact (likelihood x impact x immediacy):

FieldTypePossible Values
failure_namestringConcise description of what goes wrong.
likelihood.levelstring"low", "medium", "high"
likelihood.reasoningstringProduct-specific probability rationale with expected incidence.
impactstring"cosmetic", "annoying", "performance_loss", "unusable"
timelinestring"immediate", "within_a_year", "over_a_year"
summarystring1–2 sentences on real-use customer impact.
evidencestring[]Concrete cues from listing, specs, or images.

mitigated_failure_modes — array, 0–3 entries: common category failures that the product's design intentionally addresses.

FieldTypeDescription
failure_namestringThe common failure that is unlikely here.
ownership_experiencestringShort positive reframe (max ~6 words, e.g., "Long cord with easy rewind").
reasoningstringWhat design choices reduce this risk.
evidencestring[]Concrete cues from listing.

quality_summary — string: A calm, informed paragraph synthesizing dominant risks, design priorities, disappointment timeline, fixability, and who the product is likely to satisfy vs. frustrate.


Error Handling

StatusEndpointCauseSuggested Action
400/agents/productInvalid location format (empty, malformed, or contains path separators).Verify the location was copied verbatim from a search result.
404/agents/search (continue)logical_search_id not found or expired from cache.Start a new search with type: "new".
404/agents/productProduct cache key or destination not found. May have expired.Re-run search to get a fresh location.
422BothSchema validation failure: missing required field, wrong type, or extra key present.Fix request body. All request models use extra = "forbid".
500BothUnhandled internal error.Retry once with backoff. If persistent, report as a service issue.
502/agents/searchSearch backend did not return a final result, or returned an invalid payload.Retry once. If persistent, the upstream search service may be degraded.

Safety Rules

  1. Send JSON request bodies only.
  2. Never include extra fields — all request models use extra = "forbid" and will reject unknown keys with 422.
  3. Never invent product locations. Only use location values returned by /api/agents/search.
  4. Preserve conversation_id, logical_search_id, and product.location exactly as returned. Do not trim, modify, or regenerate.
  5. For type: "new", omit conversation_id to let the server generate one.
  6. All endpoints use the base URL https://hiarthur.com/api.

Frontend Handoff

  • Open c/<conversation_id> in a browser to resume that conversation within a GUI.
  • Open a returned product location in a browser to open the product information and see product images in a GUI.
  • Keep all backend-derived IDs and locations unchanged during handoff URL construction.

Recommended Agent Usage Pattern

  1. Call /agents/search with type: "new".
  2. Inspect the returned products.
  3. If more candidates are needed, call /agents/search with type: "continue".
  4. When a specific product requires deeper analysis, call /agents/product.

平台分布

OpenClaw

89.67%
按下载量换算2,131

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills