一键在 Manus 中运行任何 Skill

inkbox-credential-use

星标29

分支8

更新时间2026年6月29日 07:02

Use when the user asks the agent to "log into X", "get the API key for Y", "fetch the SSH key for Z", or "give me the TOTP code for service A". Hermes does not expose Inkbox vault tools; explain the limitation and do not invent credential access.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

inkbox-ai

inkbox-ai/hermes-agent-plugin

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Inkbox credential use

OpenClaw exposes Inkbox vault tools. Hermes social-tier does not register credential vault tools, so this plugin cannot list, fetch, or generate credentials/TOTP codes through Inkbox.

Hermes tool availability

There is no inkbox_credentials_list, inkbox_credentials_get_login, inkbox_credentials_get_api_key, inkbox_credentials_get_ssh_key, or inkbox_totp_code tool in Hermes.
Do not claim that you checked the vault or retrieved a credential.
If the user needs vault access, direct them to Inkbox Console or a host/plugin tier that exposes the Inkbox vault tools.

Prerequisites

The user must provide credentials through an approved host mechanism outside this Hermes Inkbox plugin.
Do not ask the user to paste secrets into chat unless they explicitly choose that path and the current host policy allows it.

Workflow

State the limitation. Say that this Hermes installation does not expose Inkbox vault tools.
Offer a safe path. Ask the user to configure the needed credential through the host's supported secret mechanism or Inkbox Console.
Avoid plaintext echo. If credentials arrive through another tool, use them for the requested action and do not repeat plaintext unless the user explicitly asked to see it.

Hygiene

Don't fake vault access. No Inkbox vault tool is available in Hermes.
Don't paste plaintext into chat. When another approved credential source exists, use it without repeating secrets.
Don't store secrets in session memory. Treat credentials as transient.

Errors

Error	Meaning
Missing credential tool	This Hermes plugin tier does not expose Inkbox vault tools.
User asks for a secret by name	Ask them to configure it through the host's supported secret path or Inkbox Console.

What this skill does NOT cover

Creating, updating, or deleting secrets — there's no plugin tool for this in agent-scoped mode.
Granting access to secrets — admin-only via the Inkbox Console.
TOTP setup — initial TOTP config also happens in the Console.

When you need more — raw Inkbox docs

If a payload shape, secret type, vault behavior, or TOTP detail isn't covered here, go to the source:

https://inkbox.ai/llms.txt — LLM-friendly index of every Inkbox doc page.
https://inkbox.ai/docs/all.md — the full Inkbox documentation concatenated as one markdown file.

Especially useful when checking the exact fields on LoginPayload, APIKeyPayload, SSHKeyPayload, KeyPairPayload, OtherPayload, or TOTPCode rather than guessing.

同仓库更多 Skills

同仓库

inkbox-imessage-responder

inkbox-ai/hermes-agent-plugin

Use when the user asks to send an iMessage, reply on iMessage, or explain how to reach the agent over iMessage — also use automatically when an inbound `imessage.received` event arrives from Inkbox. Handles the connect/router model, the recipient-first rule, and tapback reactions.

2026-07-1429

inkbox-email-triage

inkbox-ai/hermes-agent-plugin

Use when an inbound email arrives at the agent's Inkbox mailbox or when the user asks the agent to send/reply to email. Hermes can send and reply from current inbound context, but does not expose mailbox queue/read/forward/archive tools.

2026-07-1029

inkbox-sms-responder

inkbox-ai/hermes-agent-plugin

Use when the user asks to send a text, reply to an SMS, or process the SMS queue — also use automatically when an inbound `text.received` event arrives from Inkbox. Handles per-conversation context, opt-in/opt-out gates, and the 10DLC carrier propagation window.

2026-07-1029

inkbox-outbound-calling

inkbox-ai/hermes-agent-plugin

Use when the user asks the agent to place an outbound Inkbox phone call, call a phone number/contact, or call someone with a specific purpose or opening message.

2026-07-0329

inkbox-webhook-providers

inkbox-ai/hermes-agent-plugin

Use when adding support for verifying a new inbound-webhook source (a third-party service that will POST signed events to this agent's /webhook endpoint), or when asked how the plugin decides whether an incoming webhook is authentic. Explains the webhook_providers registry and how to onboard a new provider.

2026-07-0129

inkbox-call-review

inkbox-ai/hermes-agent-plugin

Use when the user asks about Inkbox calls, call transcripts, missed calls, or follow-up work. Hermes can use current live/post-call context, but does not expose historical call-read tools.

2026-06-2929

name	inkbox-credential-use
description	Use when the user asks the agent to "log into X", "get the API key for Y", "fetch the SSH key for Z", or "give me the TOTP code for service A". Hermes does not expose Inkbox vault tools; explain the limitation and do not invent credential access.
user-invocable	false

Inkbox credential use

OpenClaw exposes Inkbox vault tools. Hermes social-tier does not register credential vault tools, so this plugin cannot list, fetch, or generate credentials/TOTP codes through Inkbox.

Hermes tool availability

There is no inkbox_credentials_list, inkbox_credentials_get_login, inkbox_credentials_get_api_key, inkbox_credentials_get_ssh_key, or inkbox_totp_code tool in Hermes.
Do not claim that you checked the vault or retrieved a credential.
If the user needs vault access, direct them to Inkbox Console or a host/plugin tier that exposes the Inkbox vault tools.

Prerequisites

The user must provide credentials through an approved host mechanism outside this Hermes Inkbox plugin.
Do not ask the user to paste secrets into chat unless they explicitly choose that path and the current host policy allows it.

Workflow

State the limitation. Say that this Hermes installation does not expose Inkbox vault tools.
Offer a safe path. Ask the user to configure the needed credential through the host's supported secret mechanism or Inkbox Console.
Avoid plaintext echo. If credentials arrive through another tool, use them for the requested action and do not repeat plaintext unless the user explicitly asked to see it.

Hygiene

Don't fake vault access. No Inkbox vault tool is available in Hermes.
Don't paste plaintext into chat. When another approved credential source exists, use it without repeating secrets.
Don't store secrets in session memory. Treat credentials as transient.

Errors

Error	Meaning
Missing credential tool	This Hermes plugin tier does not expose Inkbox vault tools.
User asks for a secret by name	Ask them to configure it through the host's supported secret path or Inkbox Console.

What this skill does NOT cover

Creating, updating, or deleting secrets — there's no plugin tool for this in agent-scoped mode.
Granting access to secrets — admin-only via the Inkbox Console.
TOTP setup — initial TOTP config also happens in the Console.

When you need more — raw Inkbox docs

If a payload shape, secret type, vault behavior, or TOTP detail isn't covered here, go to the source:

https://inkbox.ai/llms.txt — LLM-friendly index of every Inkbox doc page.
https://inkbox.ai/docs/all.md — the full Inkbox documentation concatenated as one markdown file.

Especially useful when checking the exact fields on LoginPayload, APIKeyPayload, SSHKeyPayload, KeyPairPayload, OtherPayload, or TOTPCode rather than guessing.