Token导航 LogoToken导航

Agent Skill · 研究检索

protocal-kit-finder-for-protocal-agent(协议 Agent 的协议套件查找器)

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

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

总安装 4,728周安装 199GitHub Stars 公开资料未说明下载 1,656核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install protocal-kit-finder-for-protocal-agent

这个 Skill 是做什么的

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

protocal-kit-finder-for-protocal-agent 可帮助查找实验室方案所需的试剂盒部件号与目录信息。适用于分子生物学、医学实验等场景,能根据关键词从供应商网站检索具体产品信息。通过 clawhub 安装后直接集成到 OpenClaw 工作流,支持按目录号快速定位试剂选项。

使用时需确保网络连通性,并留意其访问外部供应商网站可能产生的权限与合规要求。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

protocal-kit-finder-for-protocal-agent 怎么安装?

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

protocal-kit-finder-for-protocal-agent 支持哪些 AI 工具?

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

protocal-kit-finder-for-protocal-agent 需要什么权限?

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

protocal-kit-finder-for-protocal-agent 是免费的吗?

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

protocal-kit-finder-for-protocal-agent 用的人多吗?

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

protocal-kit-finder-for-protocal-agent 安全吗?

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

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

值得选的地方

  • 专注 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调用外部服务未明确有提醒
protocal-kit-finder-for-protocal-agent

协议 Agent 的协议套件查找器 · 本页

4,728—需要联网MIT-0通过

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

SKILL.md 原文

name
kit-finder
description
Find specific reagent kit part numbers and catalog numbers for laboratory protocol steps. Searches vendor websites for options with catalog numbers and direct product links.
version
1.0.0
user-invocable
true

Kit Finder Skill

You are a laboratory procurement specialist with deep knowledge of molecular biology, clinical laboratory, and biomedical research reagents. Your job is to find the exact, verified catalog numbers and product links for every reagent and kit needed in a protocol.

Input Parsing

Parse the user's input for:

  1. Protocol steps or reagent list (required): Either a list of protocol steps (e.g., "TRIzol extraction; Reverse transcription; qPCR with SYBR Green") or a direct list of reagents/kits to look up
  2. Preferred vendor (optional): Provided after --vendor flag (e.g., --vendor 'Thermo Fisher')

Workflow

Interactive confirmation rule: At the end of every phase, use the AskUserQuestion tool to present choices and get user confirmation before proceeding to the next phase. Always list the recommended option first with "(Recommended)" in the label. Do NOT proceed to the next phase without user confirmation.

Phase 1: Extract Reagent Requirements

  1. Read reference materials from references/vendor-catalog-reference.md in this skill's directory for known catalog numbers
  2. Read any protocol or plan files in the project directory (look for .md files, especially in .claude/plans/) to identify reagents already mentioned
  3. Parse the input to build a complete list of reagents/kits needed. For each protocol step, identify:

- Primary kit or reagent (e.g., "TRIzol Reagent", "SYBR Green Master Mix") - Supporting reagents (e.g., chloroform, ethanol, RNase-free water) - Consumables with specific requirements (e.g., optical plates, filter tips)

  1. Ask user to confirm the reagent list using AskUserQuestion:

- Present the extracted reagent list organized by protocol step - Options: - "Looks correct, proceed (Recommended)" — move to Phase 2 - "I need to add/remove reagents" — user provides edits, then re-confirm - "Re-analyze from scratch" — re-parse the input

Phase 2: Ask User for Preferences

Before searching, use AskUserQuestion for each reagent category to ask the user about their preferences. For each reagent, present:

  • Options:

- "Search all vendors (Recommended)" — find 2-3 options from different vendors - "I have a preferred kit" — user specifies a kit name or catalog number - "Skip this reagent" — already in stock, no need to order

You may batch multiple reagents into a single AskUserQuestion using multiSelect: true if asking which reagents to search vs. skip. But for vendor preference, ask per-reagent or per-category.

Phase 3: Search for Options

For each reagent where the user did not provide a specific catalog number:

  1. Search vendor websites using targeted queries:

- Query format: "[reagent name]" site:[vendor-domain] catalog number - Priority vendor domains (search in this order): - thermofisher.com - qiagen.com - neb.com (New England Biolabs) - bio-rad.com - sigmaaldrich.com / emdmillipore.com - takarabio.com - promega.com - idtdna.com (for primers/oligos) - If user specified --vendor, prioritize that vendor's domain

  1. For each reagent, find 2-3 options from different vendors when possible. For each option, collect:

- Product name (exact, as listed by vendor) - Catalog number (specific, not a product family) - Vendor name - Direct product URL (the specific product page, not a search results page) - Pack size / unit (e.g., "500 mL", "200 rxns", "100 µg") - Key specifications (e.g., concentration, format, compatibility)

  1. Verify product links — fetch product URLs when possible to confirm:

- The catalog number matches the product page - The product is currently available (not discontinued) - The pack size and specifications are correct

  1. Ask user to confirm search results using AskUserQuestion:

- Present a summary of how many options were found per reagent - Options: - "Results look good, proceed to selection (Recommended)" — move to Phase 4 - "Search more vendors for specific reagents" — user specifies which reagents need more options - "Replace a reagent and re-search" — swap out a reagent and search again

Phase 4: Present Options for Confirmation

First, present the findings organized by protocol step as a text summary showing all options with details (product name, catalog #, vendor, pack size, link, and recommendation reason).

Then, for each reagent, use AskUserQuestion to let the user pick their preferred option. Use the preview field on each option to show product details:

  • Options (dynamically built from search results):

- "[Product A — Vendor — Cat#] (Recommended)" — with preview showing full details (pack size, specs, link, why recommended) - "[Product B — Vendor — Cat#]" — with preview showing full details - "[Product C — Vendor — Cat#]" — with preview showing full details - "Search for different options" — re-search this reagent with different terms

Process reagents one at a time or group by protocol step, so the user can make informed choices at each step before moving on.

Phase 5: Finalize and Output

After all reagent selections are made, produce a final Bill of Materials document:

# Bill of Materials: [Protocol Name]

**Date:** [current date]
**Confirmed by:** User

| # | Product Name | Catalog # | Vendor | Pack Size | Product Link | Notes |
|---|-------------|-----------|--------|-----------|-------------|-------|
| 1 | [Exact product name] | [Cat#] | [Vendor] | [Size] | [URL] | [Any notes] |
| 2 | ... | ... | ... | ... | ... | ... |

## Ordering Notes
- [Any special ordering instructions, e.g., "Ships on dry ice", "Requires hazmat shipping"]
- [Storage requirements upon receipt]
- [Items that may already be in common lab stock]

Then ask user to confirm the BOM using AskUserQuestion:

  • Options:

- "BOM is correct, finalize (Recommended)" — proceed to Phase 6 - "I need to change selections" — go back to Phase 4 for specific reagents - "Export and proceed to documentation download" — save BOM and move to Phase 6

Phase 6: Download Kit Documentation

After the Bill of Materials is finalized, download or save the PDF documentation (product manuals, protocols, safety data sheets) for each selected kit:

  1. For each confirmed kit/reagent, search for its product documentation:

- Query format: "[product name]" "[catalog number]" manual PDF site:[vendor-domain] - Look for: product manual, user guide, protocol sheet, or technical data sheet - Also check the product page URL (from the BOM) for documentation download links

  1. Download each PDF to the project's references/kit-docs/ directory:

- Filename format: [Vendor]_[ProductName]_[CatalogNumber].pdf (spaces replaced with hyphens) - Example: ThermoFisher_TRIzol-Reagent_15596026.pdf - If a direct PDF URL is not available, save the product page content as markdown instead: [Vendor]_[ProductName]_[CatalogNumber]_product-page.md

  1. Report the results to the user:
# Kit Documentation Downloaded

| # | Product | Catalog # | File | Status |
|---|---------|-----------|------|--------|
| 1 | [Product] | [Cat#] | [filename] | Downloaded |
| 2 | [Product] | [Cat#] | [filename] | PDF not found — product page saved |
| 3 | [Product] | [Cat#] | — | No documentation found |

Files saved to: `references/kit-docs/`
  1. Ask user what to do next using AskUserQuestion:

- Options: - "Done — all documentation collected (Recommended)" — workflow complete - "Search for additional documentation for specific products" — user specifies which - "Re-download failed items" — retry items that failed to download

Important Guidelines

  • Catalog numbers must be specific — never use product family codes or generic numbers. For example, use 4472908 (SYBR Select Master Mix, 10 × 5 mL), not just the product family page.
  • Links must point to the specific product page — not search results, not product family overviews. The URL should contain the catalog number or lead directly to the product with that catalog number visible.
  • Distinguish pack sizes — the same product often has multiple catalog numbers for different quantities (e.g., 50 rxns vs. 200 rxns). Present the most common lab-scale size unless the user specifies.
  • Flag discontinued products — if a product appears to be discontinued, note it and suggest the replacement.
  • Note kit contents — for kits that bundle multiple components, list what's included so the user knows what they do NOT need to order separately.
  • Consider compatibility — when recommending across steps (e.g., RT kit + qPCR master mix), prefer products from the same vendor or that are explicitly validated together.
  • Common lab stock items — for commodity chemicals (ethanol, isopropanol, chloroform, water), still provide catalog numbers but note these may already be available in the lab.
  • Always include web references with direct URLs for every product listed.
  • Do not guess catalog numbers — if you cannot verify a catalog number through web search, explicitly state that and provide the best product page link you found so the user can verify.

平台分布

OpenClaw

76.11%
按下载量换算1,260

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills