printing-press-library

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Printing Press Library

Use this skill when a user asks for a CLI, agent skill, API wrapper, scraper, automation tool, or data source that may exist in the Printing Press Library.

The library is an open-source catalog of focused CLIs and matching agent skills generated from

mvanhorn/cli-printing-press

. This skill is the catalog front door. Do not install a random long-tail skill just because it exists. First identify the right tool, then install the focused skill or CLI only when it is useful for the task.

当用户请求可能存在于Printing Press Library中的CLI、Agent技能、API包装器、爬虫、自动化工具或数据源时，使用此技能。

该库是一个开源目录，包含由

mvanhorn/cli-printing-press

生成的专用CLI及对应的Agent技能。本技能是该目录的入口。不要仅仅因为某个长尾技能存在就随意安装。首先确定合适的工具，仅当它对任务有用时才安装该专用技能或CLI。

Default workflow

默认工作流程

Clarify the user goal only if needed.
- If the request names a service or website, search for that directly.
- If the request describes a job instead of a service, search by capability and domain.
- If the user's agent already has a safe built-in tool that solves the job, prefer that over installing another CLI.
Search the catalog with the library CLI first.
- Use
```
npx -y @mvanhorn/printing-press-library search <keyword>
```
  for human-readable result cards.
- Use
```
npx -y @mvanhorn/printing-press-library search <keyword> --json
```
  for agent-friendly parsing.
- Use
```
npx -y @mvanhorn/printing-press-library list --category <category> --json
```
  when the category is known.
- Each search result includes the canonical install command for that tool.
- Fall back to the GitHub repo or local clone only when
```
npx
```
  is unavailable or deeper inspection is needed.
Select deliberately.
- Prefer the candidate whose README/SKILL examples match the user's actual job, not merely the same website name.
- Check whether auth, cookies, paid APIs, OS-specific binaries, or browser automation are required before installing.
- Install the narrowest useful tool. Do not install a family of adjacent tools just because the search returned them.
Install through the library installer when the selected tool is useful.
- The primitive is
```
npx -y @mvanhorn/printing-press-library install <slug>
```
  .
- The install command installs both the CLI and the matching focused agent skill.
- ```
install <slug>
```
  is idempotent: re-running it on an already-installed tool refreshes the Go binary and overwrites/re-adds the focused skill in place.
- Behind the scenes, the installer uses
```
go install <module>@latest
```
  for the CLI and the Vercel Agent Skills-compatible
```
skills
```
  CLI to install the focused
```
pp-*
```
  skill globally from this repo.
- If the Go binary installs successfully but is not on the current process
```
PATH
```
  , treat that as a warning, not a failed skill install. The installer should still install the focused skill and print platform-specific PATH instructions.
- In agent/gateway environments, shell startup files may not affect the already-running process. Restart the session/gateway after PATH changes, or use a PATH-visible user bin directory such as
```
~/.local/bin
```
  when that is already exposed by the harness.
- In OpenClaw, this same install command installs the focused skill for OpenClaw; do not replace it with a separate repo-path skill install unless the user explicitly asks for skill-only installation.
- Pass
```
--cli-only
```
  or
```
--skill-only
```
  only when the user explicitly wants just one side.
Make the newly installed skill visible to the running agent.
- Most agent harnesses snapshot available skills at session start. After installing or refreshing a focused skill, start a fresh session or reload skills before trying to invoke it.
- In Hermes CLI sessions, use
```
/reload-skills
```
  when available, or exit and start a new
```
hermes
```
  session.
- In Hermes gateway sessions, use
```
/restart
```
  from the gateway chat or
```
hermes gateway restart
```
  from a shell so the gateway process reloads installed skills.
- In OpenClaw, assume the current agent session may not see newly installed skills until the OpenClaw session or gateway is restarted.
Verify before claiming success.
- If installing a CLI, run its
```
--help
```
  or an equivalent harmless command.
- If installing a skill, verify the destination harness can see it after the session reload/restart when the harness has a verification command.
- If using a credentialed CLI, confirm required environment variables without printing secrets.
Offer an efficient periodic update schedule after successful install or refresh.
- Because install/update is idempotent, it is safe to keep installed Printing Press CLIs and focused skills current with a scheduled job.
- Do not create a cron/scheduled job without explicit user approval; recurring jobs are durable side effects.
- Avoid one scheduled job per CLI as the default. Users may install many Printing Press tools, and per-tool jobs become noisy and hard to manage.
- Prefer one consolidated recurring job that runs
```
npx -y @mvanhorn/printing-press-library update
```
  , which refreshes every installed Printing Press CLI currently on PATH and its matching focused skill.
- Offer a per-tool job using
```
npx -y @mvanhorn/printing-press-library update <slug>
```
  only when the user explicitly wants a different cadence or policy for that one tool.
- Prefer quiet, low-frequency schedules such as weekly unless the user asks for something else.

仅在必要时明确用户目标。
- 如果请求中指定了服务或网站，直接搜索该目标。
- 如果请求描述的是一项工作而非具体服务，按功能和领域进行搜索。
- 如果用户的Agent已有内置的安全工具可以完成该任务，优先使用内置工具而非安装其他CLI。
首先使用库CLI搜索目录。
- 使用
```
npx -y @mvanhorn/printing-press-library search <keyword>
```
  获取人类可读的结果卡片。
- 使用
```
npx -y @mvanhorn/printing-press-library search <keyword> --json
```
  获取适合Agent解析的结构化结果。
- 当已知分类时，使用
```
npx -y @mvanhorn/printing-press-library list --category <category> --json
```
  。
- 每个搜索结果都包含该工具的标准安装命令。
- 仅当
```
npx
```
  不可用或需要更深入检查时，才退而使用GitHub仓库或本地克隆版本。
谨慎选择工具。
- 优先选择README/SKILL示例与用户实际任务匹配的候选工具，而非仅名称与网站相同的工具。
- 在安装前检查是否需要身份验证、Cookie、付费API、特定操作系统的二进制文件或浏览器自动化。
- 安装最贴合需求的工具。不要因为搜索结果返回了一系列相关工具就全部安装。
当所选工具有用时，通过库安装器进行安装。
- 基础命令为
```
npx -y @mvanhorn/printing-press-library install <slug>
```
  。
- 该安装命令会同时安装CLI和对应的专用Agent技能。
- ```
install <slug>
```
  具有幂等性：对已安装的工具重新运行该命令会刷新Go二进制文件，并原地覆盖/重新添加专用技能。
- 在后台，安装器使用
```
go install <module>@latest
```
  安装CLI，并使用兼容Vercel Agent Skills的
```
skills
```
  CLI从本仓库全局安装专用的
```
pp-*
```
  技能。
- 如果Go二进制文件安装成功但未在当前进程的
```
PATH
```
  中，将其视为警告而非技能安装失败。安装器仍应安装专用技能，并打印特定平台的PATH配置说明。
- 在Agent/网关环境中，shell启动文件可能不会影响已运行的进程。修改PATH后重启会话/网关，或使用已由工具暴露的PATH可见的用户bin目录，如
```
~/.local/bin
```
  。
- 在OpenClaw中，相同的安装命令会为OpenClaw安装专用技能；除非用户明确要求仅安装技能，否则不要替换为单独的仓库路径技能安装命令。
- 仅当用户明确只需要其中一项时，才添加
```
--cli-only
```
  或
```
--skill-only
```
  参数。
让新安装的技能对运行中的Agent可见。
- 大多数Agent工具会在会话开始时快照可用技能。安装或刷新专用技能后，需启动新会话或重新加载技能，然后再尝试调用它。
- 在Hermes CLI会话中，如果可用，使用
```
/reload-skills
```
  ，或退出并启动新的
```
hermes
```
  会话。
- 在Hermes网关会话中，从网关聊天使用
```
/restart
```
  ，或从shell运行
```
hermes gateway restart
```
  ，使网关进程重新加载已安装的技能。
- 在OpenClaw中，假设当前Agent会话可能无法立即看到新安装的技能，直到OpenClaw会话或网关重启。
在宣告成功前进行验证。
- 如果安装的是CLI，运行其
```
--help
```
  或其他无害命令。
- 如果安装的是技能，当工具具有验证命令时，在会话重新加载/重启后验证目标工具是否能识别该技能。
- 如果使用需要凭证的CLI，确认所需的环境变量已配置，但不要打印机密信息。
成功安装或刷新后，提供高效的定期更新计划。
- 由于安装/更新具有幂等性，通过定时任务保持已安装的Printing Press CLI和专用技能是安全的。
- 未经用户明确批准，不要创建cron/定时任务；重复任务是持久化的副作用。
- 默认情况下，避免为每个CLI创建单独的定时任务。用户可能安装多个Printing Press工具，每个工具单独的任务会变得繁琐且难以管理。
- 优先选择一个统一的重复任务，运行
```
npx -y @mvanhorn/printing-press-library update
```
  ，该命令会刷新当前PATH中所有已安装的Printing Press CLI及其对应的专用技能。
- 仅当用户明确希望为某个工具设置不同的更新频率或策略时，才提供针对单个工具的任务，使用
```
npx -y @mvanhorn/printing-press-library update <slug>
```
  。
- 优先选择安静、低频率的计划，如每周一次，除非用户要求其他频率。

What this skill is for

本技能的适用场景

Use this skill to discover CLIs and agent skills in the public Printing Press Library. Match the user's goal to the right library entry, use the library CLI to find the canonical install command, and install the selected tool only when it is useful for the task.

Good fits:

finding a purpose-built CLI for a named service
finding a scraper or data-source tool for a one-off research or automation task
installing a focused
```
pp-*
```
skill so future agents know how to use a specific CLI
refreshing already-installed Printing Press CLIs and skills

Poor fits:

replacing a safe built-in agent tool that already solves the task
installing broad tool bundles speculatively
credentialed account actions where the user has not approved external side effects
publishing, posting, booking, buying, emailing, or mutating third-party state without explicit approval

使用本技能发现公共Printing Press Library中的CLI和Agent技能。将用户目标与合适的库条目匹配，使用库CLI找到标准安装命令，并仅当工具对任务有用时才安装所选工具。

适合场景：

为指定服务寻找专用CLI
为一次性研究或自动化任务寻找爬虫或数据源工具
安装专用的
```
pp-*
```
技能，以便后续Agent知道如何使用特定CLI
刷新已安装的Printing Press CLI和技能

不适合场景：

替换已能完成任务的安全内置Agent工具
投机性地安装广泛的工具包
用户未批准外部副作用的凭证账户操作
未经明确批准就发布、发帖、预订、购买、发送邮件或修改第三方状态

Install primitive

安装基础命令

The Printing Press Library CLI is the canonical interface for installing catalog tools:

bash

npx -y @mvanhorn/printing-press-library install <slug>

That command installs both halves of a catalog entry:

the Go CLI binary
the matching focused
```
pp-*
```
agent skill

For the skill half, the installer shells out through the Vercel Agent Skills-compatible installer. Conceptually, it runs:

bash

npx -y skills@latest add mvanhorn/printing-press-library/cli-skills/pp-<slug> -g -y

So the catalog installer is still the right top-level command: it installs the CLI, then installs the focused skill globally using the same agent-skills mechanism rather than asking the agent to hand-roll a separate skill install path.

The install operation is idempotent and works as a reinstall for one tool. Re-running

install <slug>

uses

go install <module>@latest

for the binary and re-adds the focused skill non-interactively, overwriting the existing install in place. No uninstall-first step is needed.

If install warns that the binary directory is not on

PATH

, the binary and focused skill can still be installed successfully. Follow the printed platform-specific PATH instructions, then restart the running agent session or gateway if it inherits a fixed environment. On Unix-like systems where the harness already exposes

~/.local/bin

, a symlink can be a practical bridge:

bash

ln -sf "$(go env GOPATH)/bin/<tool>" "$HOME/.local/bin/<tool>"

Use

update

when the user asks to refresh or reinstall existing tools:

bash

npx -y @mvanhorn/printing-press-library update flight-goat
npx -y @mvanhorn/printing-press-library update

update <slug>

delegates to install semantics for that tool.

update

with no args discovers Printing Press CLIs currently on PATH and refreshes all of them, including their matching focused skills.

Because updates are idempotent, after a successful install or refresh, offer to create a recurring update job. Ask first; do not schedule it automatically. Prefer a single consolidated job over one job per CLI, because users may install many Printing Press tools and per-tool schedules become noisy fast.

For most users, schedule one quiet weekly job that refreshes every installed Printing Press CLI currently on PATH and its matching focused skill:

bash

npx -y @mvanhorn/printing-press-library update

Use a per-tool scheduled command only when the user explicitly wants a separate cadence or policy for one tool:

bash

npx -y @mvanhorn/printing-press-library update flight-goat

If the installed library CLI exposes

reinstall

, treat it as a convenience alias for

update

bash

npx -y @mvanhorn/printing-press-library reinstall flight-goat

Example:

bash

npx -y @mvanhorn/printing-press-library install flight-goat

Use the install line printed by

search

list

output. Do not synthesize harness-specific direct skill install commands as the default path; those are only for explicit skill-only workflows.

After install or update, assume the focused skill may not be visible to the currently running agent until skills are reloaded or the session restarts. Hermes CLI sessions can use

/reload-skills

or start a new session. Hermes gateway sessions should use

/restart

hermes gateway restart

. OpenClaw agents should restart the current session or gateway if the newly installed focused skill is not visible immediately.

Printing Press Library CLI是安装目录工具的标准接口：

bash

npx -y @mvanhorn/printing-press-library install <slug>

该命令会安装目录条目的两个部分：

Go CLI二进制文件
对应的专用
```
pp-*
```
Agent技能

对于技能部分，安装器通过兼容Vercel Agent Skills的安装器执行命令。从概念上讲，它运行：

bash

npx -y skills@latest add mvanhorn/printing-press-library/cli-skills/pp-<slug> -g -y

因此目录安装器仍是合适的顶层命令：它安装CLI，然后使用相同的agent-skills机制全局安装专用技能，而非让Agent手动构建单独的技能安装路径。

安装操作具有幂等性，可作为单个工具的重新安装。重新运行

install <slug>

会使用

go install <module>@latest

安装二进制文件，并以非交互方式重新添加专用技能，覆盖现有安装。无需先执行卸载步骤。

如果安装提示二进制目录不在

PATH

中，二进制文件和专用技能仍可成功安装。按照打印的特定平台PATH说明操作，然后重启运行中的Agent会话或网关（如果它继承了固定环境）。在类Unix系统中，如果工具已暴露

~/.local/bin

，符号链接是一个实用的解决方案：

bash

ln -sf "$(go env GOPATH)/bin/<tool>" "$HOME/.local/bin/<tool>"

当用户要求刷新或重新安装现有工具时，使用

update

命令：

bash

npx -y @mvanhorn/printing-press-library update flight-goat
npx -y @mvanhorn/printing-press-library update

update <slug>

会委托该工具的安装语义。不带参数的

update

会发现当前PATH中的所有Printing Press CLI，并刷新它们及其对应的专用技能。

由于更新具有幂等性，成功安装或刷新后，可以提议创建重复更新任务。先询问用户，不要自动安排。优先选择单个统一任务而非每个CLI单独的任务，因为用户可能安装多个Printing Press工具，每个工具单独的计划会很快变得繁琐。

对于大多数用户，安排一个安静的每周任务，刷新当前PATH中所有已安装的Printing Press CLI及其对应的专用技能：

bash

npx -y @mvanhorn/printing-press-library update

仅当用户明确希望为某个工具设置单独的更新频率或策略时，才使用针对单个工具的定时命令：

bash

npx -y @mvanhorn/printing-press-library update flight-goat

如果已安装的库CLI暴露了

reinstall

命令，将其视为

update

的便捷别名：

bash

npx -y @mvanhorn/printing-press-library reinstall flight-goat

示例：

bash

npx -y @mvanhorn/printing-press-library install flight-goat

使用

search

或

list

输出中打印的安装命令。不要默认合成特定工具的直接技能安装命令；这些仅适用于明确的仅安装技能的工作流。

安装或更新后，假设专用技能可能无法立即对当前运行的Agent可见，直到技能被重新加载或会话重启。Hermes CLI会话可以使用

/reload-skills

或启动新会话。Hermes网关会话应使用

/restart

或

hermes gateway restart

。如果新安装的专用技能无法立即可见，OpenClaw Agent应重启当前会话或网关。

Hermes-native usage

Hermes原生用法

Hermes can make Printing Press more useful than a plain skill installer because Hermes has native skills, profiles, gateway sessions, cron jobs, memory, and toolsets. Use those primitives instead of treating Hermes like a generic chat harness.

Hermes可以让Printing Press比普通技能安装器更有用，因为Hermes具有原生技能、配置文件、网关会话、定时任务、内存和工具集。使用这些基础功能，不要将Hermes视为通用聊天工具。

Install and reload in Hermes

在Hermes中安装并重新加载

After installing or updating a focused tool, make sure Hermes can actually see the new skill before invoking it:

bash

npx -y @mvanhorn/printing-press-library install <slug>

Then reload based on where Hermes is running:

Hermes CLI: run
```
/reload-skills
```
if available, or start a fresh
```
hermes
```
session.
Hermes gateway: run
```
/restart
```
in the gateway chat, or run
```
hermes gateway restart
```
from a shell.
Named profiles: install and reload in the same profile that will use the skill. A skill installed under one Hermes home/profile may not be visible to another.

When checking a local Hermes install, useful commands are:

bash

hermes skills list
hermes skills inspect <skill-or-url>
hermes config path
hermes config env-path
hermes profile list

Use these commands for diagnostics only. The catalog installer remains the default path for installing Printing Press catalog entries unless the user explicitly asks for a Hermes-only skill install.

安装或更新专用工具后，确保Hermes在调用技能前能实际看到新技能：

bash

npx -y @mvanhorn/printing-press-library install <slug>

然后根据Hermes的运行位置进行重新加载：

Hermes CLI：如果可用，运行
```
/reload-skills
```
，或启动新的
```
hermes
```
会话。
Hermes网关：在网关聊天中运行
```
/restart
```
，或从shell运行
```
hermes gateway restart
```
。
命名配置文件：在将使用该技能的同一配置文件中安装并重新加载。在一个Hermes主目录/配置文件下安装的技能可能无法在另一个配置文件中可见。

检查本地Hermes安装时，有用的命令包括：

bash

hermes skills list
hermes skills inspect <skill-or-url>
hermes config path
hermes config env-path
hermes profile list

仅将这些命令用于诊断。除非用户明确要求仅安装Hermes技能，否则目录安装器仍是安装Printing Press目录条目的默认路径。

Hermes profiles

Hermes配置文件

Hermes profiles isolate config, skills, cron jobs, sessions, and memory. If the user mentions a profile, workspace, or separate assistant identity, do not assume the default profile.

Before diagnosing "skill not found" problems, check:

which Hermes profile is active
which
```
HERMES_HOME
```
the installer targeted
whether the skill exists under that profile's
```
skills/
```
directory
whether the CLI or gateway was restarted after installation

A common failure mode is installing a focused skill into one profile and then trying to use it from another. That is not a Printing Press failure; it is an install-target mismatch.

Hermes配置文件会隔离配置、技能、定时任务、会话和内存。如果用户提到配置文件、工作区或单独的助手身份，不要默认使用默认配置文件。

在诊断“技能未找到”问题前，检查：

哪个Hermes配置文件处于活动状态
安装器针对的是哪个
```
HERMES_HOME
```
该配置文件的
```
skills/
```
目录下是否存在该技能
安装后是否重启了CLI或网关

常见的失败模式是将专用技能安装到一个配置文件中，然后尝试从另一个配置文件使用它。这不是Printing Press的问题，而是安装目标不匹配。

Hermes toolsets

Hermes工具集

Most Printing Press CLIs require shell execution, so Hermes needs terminal access to run them. If Hermes cannot use a newly installed CLI, check whether the active platform/session has the

terminal

toolset enabled.

Do not enable broad tool access blindly. If the task only needs a built-in web/search/file tool, prefer the built-in tool over installing and running a third-party CLI.

大多数Printing Press CLI需要shell执行，因此Hermes需要终端访问才能运行它们。如果Hermes无法使用新安装的CLI，检查活动平台/会话是否启用了

terminal

工具集。

不要盲目启用广泛的工具访问。如果任务仅需要内置的网页/搜索/文件工具，优先使用内置工具而非安装并运行第三方CLI。

Hermes cron updates

Hermes定时更新

For Hermes users who want installed Printing Press tools kept current, recommend one consolidated scheduled update job rather than per-tool sprawl:

text

Schedule: weekly, quiet hours preferred
Prompt: Run `npx -y @mvanhorn/printing-press-library update`, summarize any changes, and stay quiet if nothing changed.

If using Hermes' cron tool or CLI, create the job only after explicit user approval. Recurring jobs are durable side effects.

A good Hermes cron prompt is self-contained:

text

Refresh installed Printing Press tools by running `npx -y @mvanhorn/printing-press-library update`. Report only updated tools, failures, or missing prerequisites. Do not print secrets. If nothing changed and there were no errors, say so briefly.

Use a per-tool schedule only when the user explicitly wants a different cadence or risk policy for one tool.

对于希望保持已安装的Printing Press工具为最新版本的Hermes用户，建议使用一个统一的定时更新任务而非每个工具单独的任务：

text

计划：每周一次，首选非高峰时段
提示：运行`npx -y @mvanhorn/printing-press-library update`，总结任何更改；如果没有更改则保持静默。

如果使用Hermes的定时工具或CLI，仅在获得用户明确批准后创建任务。重复任务是持久化的副作用。

一个好的Hermes定时提示应独立完整：

text

通过运行`npx -y @mvanhorn/printing-press-library update`刷新已安装的Printing Press工具。仅报告更新的工具、失败情况或缺失的先决条件。不要打印机密信息。如果没有更改且没有错误，简要说明即可。

仅当用户明确希望为某个工具设置不同的更新频率或风险策略时，才使用针对单个工具的计划。

Hermes memory and session search

Hermes内存和会话搜索

Hermes may remember durable user preferences, environment conventions, and known credential locations. Use that context to avoid making the user repeat setup details, but do not store volatile install results such as PR numbers, commit SHAs, one-off downloaded files, or "installed tool X today" as memory.

Good memory candidates after repeated Printing Press use:

the user's preferred Hermes profile for tool installs
stable secret-manager conventions
a durable workspace path convention
a recurring policy such as "prefer consolidated weekly updates over per-tool jobs"

Bad memory candidates:

a specific temporary branch or PR number
a one-time search result
an installed version that will be stale soon
raw API keys, cookies, tokens, or session headers

When the user asks what was installed or decided previously, prefer Hermes session search over guessing.

Hermes可能会记住持久化的用户偏好、环境约定和已知凭证位置。使用这些上下文避免让用户重复设置细节，但不要将易变的安装结果（如PR编号、提交SHA、一次性下载的文件或“今日安装了工具X”）存储为内存。

多次使用Printing Press后适合存储为内存的内容：

用户用于工具安装的首选Hermes配置文件
稳定的密钥管理器约定
持久化的工作区路径约定
重复策略，如“优先选择统一的每周更新而非每个工具单独的任务”

不适合存储为内存的内容：

特定的临时分支或PR编号
一次性搜索结果
很快会过时的已安装版本
原始API密钥、Cookie、令牌或会话头

当用户询问之前安装或决定了什么时，优先使用Hermes会话搜索而非猜测。

Search tactics

搜索策略

Use the library CLI as the default catalog index. Human-readable search cards include an

install:

line with the canonical install command:

bash

npx -y @mvanhorn/printing-press-library search <keyword>

Use JSON when scripting or when structured ranking is useful:

bash

npx -y @mvanhorn/printing-press-library search <keyword> --json

Examples:

bash

npx -y @mvanhorn/printing-press-library search flights
npx -y @mvanhorn/printing-press-library search espn --json
npx -y @mvanhorn/printing-press-library list --category travel --json

Use repository inspection only as a fallback when

npx

is unavailable, when the CLI result is ambiguous, or when deeper README/SKILL details are needed before choosing a candidate:

bash

rg -i "<service-or-capability>" registry.json library cli-skills

If the registry shape differs, prefer the npm CLI output instead of hand-parsing generated catalog files. Facts beat vibes; official interfaces beat archaeology.

使用库CLI作为默认目录索引。人类可读的搜索卡片包含带有标准安装命令的

install:

行：

bash

npx -y @mvanhorn/printing-press-library search <keyword>

编写脚本或需要结构化排序时使用JSON格式：

bash

npx -y @mvanhorn/printing-press-library search <keyword> --json

示例：

bash

npx -y @mvanhorn/printing-press-library search flights
npx -y @mvanhorn/printing-press-library search espn --json
npx -y @mvanhorn/printing-press-library list --category travel --json

仅当

npx

不可用、CLI结果不明确或在选择候选工具前需要更深入的README/SKILL细节时，才将仓库检查作为备选方案：

bash

rg -i "<service-or-capability>" registry.json library cli-skills

如果注册表结构不同，优先使用npm CLI输出而非手动解析生成的目录文件。事实胜于直觉；官方接口优于手动分析。

Selection rules

选择规则

Prefer a candidate when:

It names the target service directly.
Its README/SKILL examples match the user's requested job.
It has documented auth and setup requirements the user can satisfy.
It supports the user's OS/runtime.
It can be verified with a harmless command before any external side effects.

Avoid a candidate when:

It is only vaguely adjacent to the task.
It requires credentials the user does not have.
It is a scraper for a site where the user's task needs official-account data and the skill cannot authenticate.
A safer built-in API/tool already solves the task.
The task is high-risk, paid, public-facing, or privacy-sensitive and the user has not approved the external action.

优先选择以下候选工具：

直接命名目标服务的工具。
README/SKILL示例与用户请求的任务匹配的工具。
有用户可以满足的已记录身份验证和设置要求的工具。
支持用户操作系统/运行时的工具。
可以在产生任何外部副作用前通过无害命令验证的工具。

避免选择以下候选工具：

仅与任务略微相关的工具。
需要用户没有的凭证的工具。
针对某个网站的爬虫，但用户的任务需要官方账户数据且该技能无法进行身份验证的工具。
已有更安全的内置API/工具可以完成任务的工具。
任务具有高风险、付费、公开或隐私敏感性质，且用户未批准外部操作的工具。

Safety and credentials

安全与凭证

Never print API keys, cookies, tokens, or session headers.
Do not ask the user to paste secrets into chat if a local secret manager or environment file is available.
Treat third-party CLIs as code execution. Install only the focused tool needed for the task.
Do not publish, post, email, buy, book, or mutate external state unless the user explicitly approves that action.

For Hermes users, prefer Hermes' normal environment file or the user's existing secret manager. To find the Hermes env path, use:

bash

hermes config env-path

Confirm that required variables are present without echoing their values. If a focused skill says a key is optional or required only for one feature, preserve that distinction; do not make the whole tool sound credential-gated.

永远不要打印API密钥、Cookie、令牌或会话头。
如果本地密钥管理器或环境文件可用，不要要求用户将机密信息粘贴到聊天中。
将第三方CLI视为代码执行。仅安装完成任务所需的专用工具。
除非用户明确批准，否则不要发布、发帖、发送邮件、购买、预订或修改外部状态。

对于Hermes用户，优先使用Hermes的常规环境文件或用户现有的密钥管理器。要查找Hermes环境路径，使用：

bash

hermes config env-path

确认所需变量已存在，但不要回显其值。如果专用技能说明某个密钥是可选的或仅对某一功能是必需的，保留该区别；不要让整个工具听起来需要凭证才能使用。

Verification checklist

验证清单

Before reporting success:

The selected candidate directly matches the user's requested job.
The install command came from
```
search
```
,
```
list
```
, or documented Printing Press CLI behavior.
The CLI was verified with
```
--help
```
or another harmless command.
The agent harness was reloaded/restarted if a newly installed skill must be visible immediately.
Required credentials were checked without printing secrets.
No external side effect was performed without explicit approval.
For Hermes, the relevant profile/session/gateway was considered when diagnosing visibility.

报告成功前：

所选候选工具直接匹配用户请求的任务。
安装命令来自
```
search
```
、
```
list
```
或已记录的Printing Press CLI行为。
CLI已通过
```
--help
```
或其他无害命令验证。
如果新安装的技能需要立即可见，已重新加载/重启Agent工具。
已检查所需凭证，但未打印机密信息。
未经明确批准，未执行任何外部副作用。
对于Hermes，诊断可见性问题时已考虑相关配置文件/会话/网关。

README behavior on ClawHub

ClawHub上的README行为

ClawHub renders

SKILL.md

(or

skill.md

) as the skill readme. A separate

README.md

in the skill folder is not the published readme. Put user-facing ClawHub documentation in this file.

ClawHub会将

SKILL.md

（或

skill.md

）渲染为技能的README。技能文件夹中的单独

README.md

不是发布的README。将面向用户的ClawHub文档放在此文件中。