· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →ailuntz v0.6.1
按名称调用网站、发布、模型与 SSH 凭据
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
配置 Keybook:请询问我现有凭据 YAML 的绝对路径,在本地检查格式,只保存路径。
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Keybook 是供本机已授权任务使用的凭据目录。首次使用时,告诉它你现有凭据 YAML 文件的绝对路径;它会在本地检查格式,只保存路径。以后无需反复粘贴密码或 API Key,直接让 AI 继续原任务即可。 需要登录网站时,可查找 web 分类中的用户名、邮箱、指定密码变体和 PIN;需要本机授权时,可分别查找 system 中的 macOS 登录密码或登录钥匙串密码。发布 npm 包、上传 Hugging Face 模型或数据集、推送 Docker 镜像、操作 GitHub/GitLab、部署 Cloudflare 时,可按名称查找 services 中对应的令牌。调用 OpenRouter、ModelScope 等模型 API 时,查找 llm 中的密钥;连接已授权的 SSH 主机时,查找 ssh 中的私钥文件路径。实际可用条目取决于你自己的 YAML,Keybook 不会假定某个服务已配置。 Keybook 先搜索条目名称,再用随包脚本把选定值注入可信目标程序的环境变量,并继续任务。list/search 只返回名称,get 始终遮盖值,run 隐藏子进程输出并只报告状态;不会在对话中展示明文。SSH 条目是文件路径,由目标程序传给 SSH 客户端。你自行维护本地 YAML;插件不会创建、加密或同步它,也不提供浏览器自动填充。需要本机终端与 Node.js 22+。
Language: Chinese · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: configure-yaml description: Configure Keybook with the absolute path to an existing local credentials YAML file. Use when the user asks to set up or change the YAML path, or when a credential task finds Keybook uninitialized. Do not prompt merely because the plugin was installed. --- # Configure Keybook YAML Respond in the user's language. This skill collects a file path, never YAML contents or credential values. 1. If the user already supplied a path, use it. Otherwise, ask one focused question for the absolute path to their **existing local YAML file**. When a native user-input tool supports free text, use it with no made-up path choices; otherwise ask directly in the conversation. Explain briefly that only the path is needed and the file stays local. Ask only once: if an asynchronous input tool acknowledges that it displayed the question, that acknowledgment is not the user's path. Do not repeat the question in a chat message. If no independent work remains, end the turn and resume setup when the user replies. Do not infer a path from examples, old notes, or filesystem searches. 2. Resolve the bundled script at `../keybook/scripts/keybook.mjs` relative to this SKILL.md. Requires local shell access and Node.js 22+. Run `node "<script>" init --file "<user-provided-path>"`. Pass the path as a single argument using an argv-based process call or proper shell quoting; never interpolate untrusted path text into shell code. The command validates the existing file and saves only its path in `~/.config/keybook/config.json` (or `KEYBOOK_CONFIG_HOME/config.json`); it does not create or edit the YAML. 3. Run `node "<script>" doctor --json` and report only whether the file is valid, its category and entry counts, and any permission warning. Do not show credential values. If validation fails, report the safe error and ask the user to correct the path or file locally; do not read the YAML into the conversation. For credential use after setup, follow the sibling [Keybook skill](../keybook/SKILL.md). If a configured file already works and the user has not asked to change it, continue the task without asking for a new path.
--- name: keybook description: Use Keybook when an authorized task needs credentials from the user's local YAML file. Find website logins; macOS login or keychain passwords; npm, Hugging Face, Docker, GitHub/GitLab or Cloudflare tokens; model API keys such as OpenRouter or ModelScope; and SSH private-key paths. Search names and pass only the selected value to a trusted local process without printing it. Use before asking the user to paste a secret, and when the user asks which credential names are configured. --- # Keybook Respond in the user's language. Requires local shell access; explain if unavailable. Continue the authorized task after using credentials. If invoked without a concrete task, explain the categories without reading values. - `web`: website credentials named `web_username`, `web_email`, `web_password_with_special_char`, `web_password`, `web_fallback_password` and `web_pin`. For example, `web.web_username`. These entries are for websites, not the operating system or keychain. - `system`: local machine credentials. `system.macos_login_password` is the macOS user login password; `system.macos_keychain_password` is the login-keychain password. Keep them separate even if equal; never substitute one for the other or fall back to website passwords. - `services`: tokens for npm publishing, Hugging Face model/dataset uploads, Docker registry pushes, GitHub/GitLab access and Cloudflare deployment. Discover the actual stored name; do not assume every service is configured. - `llm`: model provider keys, for example `llm.modelscope`. - `ssh`: private-key file paths, for example `ssh.default_key`; values are paths, never inline private keys. 1. Use the bundled [scripts/keybook.mjs](scripts/keybook.mjs) with Node.js 22+. Resolve its absolute path relative to this SKILL.md; do not hardcode a cache/version directory. Below, `node "<script>"` means that bundled file. Do not install or invoke a global npm package. If Node or local shell access is unavailable, explain the missing runtime. 2. Run `node "<script>" doctor --json`. If uninitialized, follow the sibling [configure-yaml skill](../configure-yaml/SKILL.md) to ask for the existing YAML file's absolute path, validate it, and save only the path in `~/.config/keybook/config.json` (or `KEYBOOK_CONFIG_HOME/config.json`). The user can change the path with `init --file` or override it for one command with `--file`. Never ask for the file contents. Do not guess paths or import old notes. 3. Use `node "<script>" search <name> --json` or `list <category> --json`. These return names only. Quote names containing spaces and qualify ambiguous names. 4. Use `node "<script>" run --env API_KEY=llm.modelscope -- node your-script.mjs`. Choose the actual variable consumed by the trusted target program; this example assumes the script reads `API_KEY`. Repeat `--env` for multiple entries. Some CLIs require an additional configuration file to consume tokens; do not assume every CLI reads an arbitrary variable. 5. `run` disables child input/output and returns status only. `get` always masks values; the CLI has no plaintext output mode. Users who need to view a value can open their YAML themselves outside the AI conversation. Do not use shell echo, file reads, or browser tool arguments to return secrets into the conversation. If a task requires visible results, make the consumer persist only reviewed, nonsecret results separately; never persist or read raw credential-bearing logs. Do not claim the tool prevents a target process from storing or sending secrets. Missing, empty or placeholder values stop execution: tell the user which entry needs updating in the original YAML. On failure, report the safe status and distinguish known authentication errors, insufficient permissions, network problems and verification challenges. A nonzero exit alone does not prove expiration. Remind the user to update expired, revoked or incorrect credentials when supported by service evidence; do not invent a diag
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugins_6ab477295a3081918fce6282c1273661
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.