[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVP8DGS8WHVBY6G8VQME8D":3,"skill-same:01M7AVP8DGS8WHVBY6G8VQME8D":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":5,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7AVP8DGS8WHVBY6G8VQME8D","hermesone",null,"Install, update, and manage the Hermes One desktop app via the `hermesone` npm package. Use when a user wants to set up Hermes One, install or upgrade it from the command line, check the installed version, preview a release before installing, pin a specific version, or drive the installer programmatically from Node. Triggers on mentions of hermesone, Hermes One, Hermes Desktop (the former name), or installing\u002Fupdating the Hermes app.","CrawlrrAI\u002Fskills","CrawlrrAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F318571425?v=4","01M7AV5K63KCJW0GCHVKBVHW2D","01M7AV5K6R2732K7FRMXGV1PRX",0,"ISC","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fhermesone\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hermesone\ndescription: Install, update, and manage the Hermes One desktop app via the `hermesone` npm package. Use when a user wants to set up Hermes One, install or upgrade it from the command line, check the installed version, preview a release before installing, pin a specific version, or drive the installer programmatically from Node. Triggers on mentions of hermesone, Hermes One, Hermes Desktop (the former name), or installing\u002Fupdating the Hermes app.\nlicense: ISC\ncompatibility: Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64\u002Fx64), Windows (setup.exe), Linux (.AppImage). The interactive UI needs a TTY; in non-interactive contexts it falls back to plain output. Works in Claude Code and any environment with a shell and npm.\nmetadata:\n  author: fathah\n  version: \"0.2.0\"\n---\n\n# Hermesone: Install & Update Hermes One\n\n`hermesone` (v0.2.0) is the npm package that installs and updates the **Hermes One** desktop app. It detects the host OS\u002Farch, downloads the matching GitHub release, **verifies its sha512 checksum**, and installs it — on macOS the signed app goes straight into `\u002FApplications`, ready to launch (no drag step). It ships a CLI and a programmatic API.\n\n> ⚠️ **This installs and runs third-party native code on the user's machine.** The package mitigates this — it verifies every download against the publisher's sha512 manifest (and refuses to run an unverified build), and in an interactive terminal it asks for confirmation first — but installing software is still a host-level action. See [Safety & approval](#safety--approval).\n\n- **Homepage:** https:\u002F\u002Fhermesone.org\n- **Package repository:** https:\u002F\u002Fgithub.com\u002Fhermesonehq\u002Fhermesonejs\n- **App releases pulled from:** [`fathah\u002Fhermes-desktop`](https:\u002F\u002Fgithub.com\u002Ffathah\u002Fhermes-desktop) (GitHub releases)\n\n> **Naming:** the app is **Hermes One** (formerly \"Hermes Desktop\"). The GitHub repo it's released from is still named `fathah\u002Fhermes-desktop`, and the installed macOS bundle is `Hermes One.app` — so you'll see both names. Use \"Hermes One\" with users; the `hermes-desktop` slug is just where the release assets live.\n\n> **Why this lives in Bankr Skills.** Hermes One is building toward an agent economy, with [Bankr](https:\u002F\u002Fbankr.bot) as the primary transaction layer for agent payments. This skill is the entry point: it gets Hermes One installed and current on the host so an agent can participate. **Today** the package does install\u002Fupdate\u002Fversion only — no accounts, keys, or onchain actions. Bankr-settled transactions and agent-economy hooks are **on the roadmap** and will be documented here as they ship.\n\n## Safety & approval\n\nInstalling or updating Hermes One modifies the host. The package enforces two guardrails for you: it **verifies sha512** before installing (fail-closed — it refuses if no published checksum is found), and on an interactive terminal it shows a confirmation prompt with the release, size, and checksum status. Still follow these rules:\n\n- **Require explicit user approval before any install or update.** Never trigger one as a silent side effect of another task or an autonomous workflow.\n- **In non-interactive\u002Fagent contexts the confirm prompt is skipped** (and `--yes` does the same). There, *you* are the approval gate: run [`hermesone plan`](#preview-a-release) first, show the user the resolved release\u002Fasset\u002Fsize\u002Fsha512, get a yes, then run `install`.\n- **Don't override verification.** Only set `HERMESONE_ALLOW_UNVERIFIED=1` if the user explicitly accepts installing a build with no published checksum.\n- **Pin what you install** (`@0.2.0` for the package; a release tag for the app) when reproducibility matters — see [Pinning](#pin-a-specific-release).\n\n## Recommended flow\n\nInstalling the npm package no longer installs the app as a side effect (see [Postinstall behavior](#postinstall-behavior)). The clean path is: install the CLI, preview, then install on confirmation.\n\n```bash\n# 1. Install the CLI (no host change — the app is not installed yet).\nnpm install -g hermesone@0.2.0\n\n# 2. Preview the exact release that would be installed.\nhermesone plan\n\n# 3. Install. Interactive terminals show a confirmation prompt + live progress;\n#    non-interactive contexts proceed (add --yes to be explicit) and print plain lines.\nhermesone install\n```\n\n`hermesone update` is safe to run repeatedly — it no-ops when already current and only downloads when a newer release exists.\n\n## Preview a release\n\n`hermesone plan [tag]` resolves and prints what *would* be installed — release tag, asset, size, and the expected sha512 — **without downloading or installing anything**. Use it to show the user before asking them to approve an install.\n\n## CLI reference\n\n```\nhermesone \u003Ccommand> [tag]\n```\n\n| Command          | Description                                                                          |\n| ---------------- | ------------------------------------------------------------------------------------ |\n| `install [tag]`  | Download, verify (sha512), and install Hermes One — latest, or a pinned release tag. |\n| `update [tag]`   | Update Hermes One if a newer release is available (no-op when current).              |\n| `plan [tag]`     | Show what would be downloaded (tag, asset, size, expected checksum). No changes.     |\n| `version`        | Print the installed Hermes One version, or a \"not installed\" message.                |\n| `help`           | Show usage.                                                                          |\n\n| Flag \u002F Env                     | Effect                                                                       |\n| ------------------------------ | ---------------------------------------------------------------------------- |\n| `-y`, `--yes`                  | Skip the confirmation prompt (for non-interactive\u002Fscripted installs).        |\n| `HERMESONE_VERSION=\u003Ctag>`      | Pin the release tag (same as the `[tag]` argument).                          |\n| `HERMESONE_ALLOW_UNVERIFIED=1` | Proceed even if no published checksum is found. Not recommended.            |\n\nIn an interactive terminal, `install` renders a confirmation box, a live download progress bar, and per-step status (resolve → download → verify → install). In a non-interactive context it prints plain status lines and never blocks. Color honors `NO_COLOR`.\n\n## What gets installed per OS\n\n| OS      | Artifact             | Behavior                                                                                          |\n| ------- | -------------------- | ------------------------------------------------------------------------------------------------- |\n| macOS   | `*-mac.zip` (signed) | Verified, unzipped, installed into `\u002FApplications` (or `~\u002FApplications`), then launched — no drag. Updates replace in place. |\n| Windows | `*-setup.exe`        | Verified, then the installer is launched.                                                         |\n| Linux   | `*.AppImage`         | Verified, marked executable, then launched.                                                       |\n\n## Pin a specific release\n\n`install`\u002F`update` use the **latest** release by default. To install a known build, pass a tag or set the env var:\n\n```bash\nhermesone install v0.6.35\nHERMESONE_VERSION=v0.6.35 hermesone install\n```\n\n## Checksum verification (built in)\n\nEach download is verified against the base64 sha512 published in the release's electron-builder manifest (`latest-mac.yml` \u002F `latest.yml` \u002F `latest-linux.yml`). On mismatch the file is deleted and nothing is installed. If a release publishes no checksum for the asset, `install` refuses unless `HERMESONE_ALLOW_UNVERIFIED=1` is set. You do not need to verify manually — surface the result from `plan` to the user and let the package enforce it.\n\n## Programmatic API\n\n```ts\nimport { plan, install, update, getInstalledVersion } from \"hermesone\";\n\n\u002F\u002F Preview without downloading — show this to the user for approval.\nconst p = await plan();                       \u002F\u002F { tag, asset, url, size, sha512 }\n\n\u002F\u002F Install (verifies sha512 before installing). Optionally pin a tag, and\u002For\n\u002F\u002F subscribe to progress events to render your own UI.\nawait install({\n  tag: \"v0.6.35\",\n  onProgress: (e) => console.log(e.phase),    \u002F\u002F resolve|download|verify|extract|launch|installed...\n});\n\nawait update();                                \u002F\u002F no-op if already current\nconst current = await getInstalledVersion();   \u002F\u002F e.g. \"0.6.35\", or null\n```\n\nAlso exported: `fetchRelease`, `parseChecksums`, `selectAsset`, `getTarget`, `isNewer`, and types `Release`, `ReleaseAsset`, `State`, `Target`, `InstallOptions`, `InstallPlan`, `ProgressEvent`. The library prints nothing on its own — all output is driven by your `onProgress` handler.\n\n## Version tracking\n\n- The installed version is detected from the app on disk first. On macOS this reads `CFBundleShortVersionString` from `Hermes One.app\u002FContents\u002FInfo.plist` (`\u002FApplications` and `~\u002FApplications`), so manual installs are recognized too.\n- Otherwise it falls back to `~\u002F.hermesone\u002Fstate.json`, written after each install\u002Fupdate done through this tool.\n- `version` returns `null` (CLI prints \"Hermes One is not installed.\") when neither source yields a version.\n\n## Postinstall behavior\n\n`npm install hermesone` **does not** download or launch the app — running an installer as a silent side effect of `npm install` is surprising, so it's opt-in. After installing the package it prints the next step (`npx hermesone install`). Controls:\n\n| Env (set before `npm install`) | Effect                                                            |\n| ------------------------------ | ---------------------------------------------------------------- |\n| _(none)_                       | Prints guidance; does not install the app.                       |\n| `HERMESONE_AUTO_INSTALL=1`     | Runs the install automatically during postinstall.               |\n| `HERMESONE_SKIP_INSTALL=1`     | Silences the postinstall notice entirely.                        |\n\n## Troubleshooting\n\n| Symptom                                                | Cause \u002F fix                                                                                                                                |\n| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |\n| `No published checksum found for \u003Casset>`              | The release has no sha512 manifest entry for this asset. Prefer a release that does; only override with `HERMESONE_ALLOW_UNVERIFIED=1` if the user accepts it. |\n| `Checksum mismatch for \u003Casset>`                        | The download didn't match the published sha512 — the file was deleted and nothing installed. Retry; if it persists, the release\u002Fasset may be compromised or corrupted. |\n| `Failed to fetch release ...: 403`                     | GitHub API rate limit (unauthenticated). Wait and retry.                                                                                   |\n| `No Hermes One build available for \u003Cplatform>\u002F\u003Carch>`  | The release has no asset for this OS\u002Farch. Check the [releases page](https:\u002F\u002Fgithub.com\u002Ffathah\u002Fhermes-desktop\u002Freleases).                   |\n| Prompt didn't appear \u002F it just proceeded               | Not a TTY (CI, pipe, agent). That's expected — it runs non-interactively. Use `plan` first to gate, or `--yes` to be explicit.            |\n| `version` says not installed after a manual install    | Only macOS auto-detects from disk. On Windows\u002FLinux, install once via this tool so `~\u002F.hermesone\u002Fstate.json` is written.                   |\n\n## Notes & guardrails\n\n- **Host-level code execution.** Install\u002Fupdate download a native build from `fathah\u002Fhermes-desktop` and run it. The package verifies sha512 and (interactively) prompts, but only run it on explicit user intent — never automatically from an agent workflow.\n- **Preview, then install.** Use `plan` to show the release\u002Fasset\u002Fsize\u002Fsha512; in non-interactive contexts that preview is your approval gate.\n- **No credentials.** The tool needs no API key or account and performs no onchain or payment actions.\n","# Hermesone: Install & Update Hermes One\n\n`hermesone` (v0.2.0) is the npm package that installs and updates the **Hermes One** desktop app. It detects the host OS\u002Farch, downloads the matching GitHub release, **verifies its sha512 checksum**, and installs it — on macOS the signed app goes straight into `\u002FApplications`, ready to launch (no drag step). It ships a CLI and a programmatic API.\n\n> ⚠️ **This installs and runs third-party native code on the user's machine.** The package mitigates this — it verifies every download against the publisher's sha512 manifest (and refuses to run an unverified build), and in an interactive terminal it asks for confirmation first — but installing software is still a host-level action. See [Safety & approval](#safety--approval).\n\n- **Homepage:** https:\u002F\u002Fhermesone.org\n- **Package repository:** https:\u002F\u002Fgithub.com\u002Fhermesonehq\u002Fhermesonejs\n- **App releases pulled from:** [`fathah\u002Fhermes-desktop`](https:\u002F\u002Fgithub.com\u002Ffathah\u002Fhermes-desktop) (GitHub releases)\n\n> **Naming:** the app is **Hermes One** (formerly \"Hermes Desktop\"). The GitHub repo it's released from is still named `fathah\u002Fhermes-desktop`, and the installed macOS bundle is `Hermes One.app` — so you'll see both names. Use \"Hermes One\" with users; the `hermes-desktop` slug is just where the release assets live.\n\n> **Why this lives in Bankr Skills.** Hermes One is building toward an agent economy, with [Bankr](https:\u002F\u002Fbankr.bot) as the primary transaction layer for agent payments. This skill is the entry point: it gets Hermes One installed and current on the host so an agent can participate. **Today** the package does install\u002Fupdate\u002Fversion only — no accounts, keys, or onchain actions. Bankr-settled transactions and agent-economy hooks are **on the roadmap** and will be documented here as they ship.\n\n## Safety & approval\n\nInstalling or updating Hermes One modifies the host. The package enforces two guardrails for you: it **verifies sha512** before installing (fail-closed — it refuses if no published checksum is found), and on an interactive terminal it shows a confirmation prompt with the release, size, and checksum status. Still follow these rules:\n\n- **Require explicit user approval before any install or update.** Never trigger one as a silent side effect of another task or an autonomous workflow.\n- **In non-interactive\u002Fagent contexts the confirm prompt is skipped** (and `--yes` does the same). There, *you* are the approval gate: run [`hermesone plan`](#preview-a-release) first, show the user the resolved release\u002Fasset\u002Fsize\u002Fsha512, get a yes, then run `install`.\n- **Don't override verification.** Only set `HERMESONE_ALLOW_UNVERIFIED=1` if the user explicitly accepts installing a build with no published checksum.\n- **Pin what you install** (`@0.2.0` for the package; a release tag for the app) when reproducibility matters — see [Pinning](#pin-a-specific-release).\n\n## Recommended flow\n\nInstalling the npm package no longer installs the app as a side effect (see [Postinstall behavior](#postinstall-behavior)). The clean path is: install the CLI, preview, then install on confirmation.\n\n```bash\n# 1. Install the CLI (no host change — the app is not installed yet).\nnpm install -g hermesone@0.2.0\n\n# 2. Preview the exact release that would be installed.\nhermesone plan\n\n# 3. Install. Interactive terminals show a confirmation prompt + live progress;\n#    non-interactive contexts proceed (add --yes to be explicit) and print plain lines.\nhermesone install\n```\n\n`hermesone update` is safe to run repeatedly — it no-ops when already current and only downloads when a newer release exists.\n\n## Preview a release\n\n`hermesone plan [tag]` resolves and prints what *would* be installed — release tag, asset, size, and the expected sha512 — **without downloading or installing anything**. Use it to show the user before asking them to approve an install.\n\n## CLI reference\n\n```\nhermesone \u003Ccommand> [tag]\n```\n\n| Command          | Description                                                                          |\n| ---------------- | ------------------------------------------------------------------------------------ |\n| `install [tag]`  | Download, verify (sha512), and install Hermes One — latest, or a pinned release tag. |\n| `update [tag]`   | Update Hermes One if a newer release is available (no-op when current).              |\n| `plan [tag]`     | Show what would be downloaded (tag, asset, size, expected checksum). No changes.     |\n| `version`        | Print the installed Hermes One version, or a \"not installed\" message.                |\n| `help`           | Show usage.                                                                          |\n\n| Flag \u002F Env                     | Effect                                                                       |\n| ------------------------------ | ---------------------------------------------------------------------------- |\n| `-y`, `--yes`                  | Skip the confirmation prompt (for non-interactive\u002Fscripted installs).        |\n| `HERMESONE_VERSION=\u003Ctag>`      | Pin the release tag (same as the `[tag]` argument).                          |\n| `HERMESONE_ALLOW_UNVERIFIED=1` | Proceed even if no published checksum is found. Not recommended.            |\n\nIn an interactive terminal, `install` renders a confirmation box, a live download progress bar, and per-step status (resolve → download → verify → install). In a non-interactive context it prints plain status lines and never blocks. Color honors `NO_COLOR`.\n\n## What gets installed per OS\n\n| OS      | Artifact             | Behavior                                                                                          |\n| ------- | -------------------- | ------------------------------------------------------------------------------------------------- |\n| macOS   | `*-mac.zip` (signed) | Verified, unzipped, installed into `\u002FApplications` (or `~\u002FApplications`), then launched — no drag. Updates replace in place. |\n| Windows | `*-setup.exe`        | Verified, then the installer is launched.                                                         |\n| Linux   | `*.AppImage`         | Verified, marked executable, then launched.                                                       |\n\n## Pin a specific release\n\n`install`\u002F`update` use the **latest** release by default. To install a known build, pass a tag or set the env var:\n\n```bash\nhermesone install v0.6.35\nHERMESONE_VERSION=v0.6.35 hermesone install\n```\n\n## Checksum verification (built in)\n\nEach download is verified against the base64 sha512 published in the release's electron-builder manifest (`latest-mac.yml` \u002F `latest.yml` \u002F `latest-linux.yml`). On mismatch the file is deleted and nothing is installed. If a release publishes no checksum for the asset, `install` refuses unless `HERMESONE_ALLOW_UNVERIFIED=1` is set. You do not need to verify manually — surface the result from `plan` to the user and let the package enforce it.\n\n## Programmatic API\n\n```ts\nimport { plan, install, update, getInstalledVersion } from \"hermesone\";\n\n\u002F\u002F Preview without downloading — show this to the user for approval.\nconst p = await plan();                       \u002F\u002F { tag, asset, url, size, sha512 }\n\n\u002F\u002F Install (verifies sha512 before installing). Optionally pin a tag, and\u002For\n\u002F\u002F subscribe to progress events to render your own UI.\nawait install({\n  tag: \"v0.6.35\",\n  onProgress: (e) => console.log(e.phase),    \u002F\u002F resolve|download|verify|extract|launch|installed...\n});\n\nawait update();                                \u002F\u002F no-op if already current\nconst current = await getInstalledVersion();   \u002F\u002F e.g. \"0.6.35\", or null\n```\n\nAlso exported: `fetchRelease`, `parseChecksums`, `selectAsset`, `getTarget`, `isNewer`, and types `Release`, `ReleaseAsset`, `State`, `Target`, `InstallOptions`, `InstallPlan`, `ProgressEvent`. The library prints nothing on its own — all output is driven by your `onProgress` handler.\n\n## Version tracking\n\n- The installed version is detected from the app on disk first. On macOS this reads `CFBundleShortVersionString` from `Hermes One.app\u002FContents\u002FInfo.plist` (`\u002FApplications` and `~\u002FApplications`), so manual installs are recognized too.\n- Otherwise it falls back to `~\u002F.hermesone\u002Fstate.json`, written after each install\u002Fupdate done through this tool.\n- `version` returns `null` (CLI prints \"Hermes One is not installed.\") when neither source yields a version.\n\n## Postinstall behavior\n\n`npm install hermesone` **does not** download or launch the app — running an installer as a silent side effect of `npm install` is surprising, so it's opt-in. After installing the package it prints the next step (`npx hermesone install`). Controls:\n\n| Env (set before `npm install`) | Effect                                                            |\n| ------------------------------ | ---------------------------------------------------------------- |\n| _(none)_                       | Prints guidance; does not install the app.                       |\n| `HERMESONE_AUTO_INSTALL=1`     | Runs the install automatically during postinstall.               |\n| `HERMESONE_SKIP_INSTALL=1`     | Silences the postinstall notice entirely.                        |\n\n## Troubleshooting\n\n| Symptom                                                | Cause \u002F fix                                                                                                                                |\n| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |\n| `No published checksum found for \u003Casset>`              | The release has no sha512 manifest entry for this asset. Prefer a release that does; only override with `HERMESONE_ALLOW_UNVERIFIED=1` if the user accepts it. |\n| `Checksum mismatch for \u003Casset>`                        | The download didn't match the published sha512 — the file was deleted and nothing installed. Retry; if it persists, the release\u002Fasset may be compromised or corrupted. |\n| `Failed to fetch release ...: 403`                     | GitHub API rate limit (unauthenticated). Wait and retry.                                                                                   |\n| `No Hermes One build available for \u003Cplatform>\u002F\u003Carch>`  | The release has no asset for this OS\u002Farch. Check the [releases page](https:\u002F\u002Fgithub.com\u002Ffathah\u002Fhermes-desktop\u002Freleases).                   |\n| Prompt didn't appear \u002F it just proceeded               | Not a TTY (CI, pipe, agent). That's expected — it runs non-interactively. Use `plan` first to gate, or `--yes` to be explicit.            |\n| `version` says not installed after a manual install    | Only macOS auto-detects from disk. On Windows\u002FLinux, install once via this tool so `~\u002F.hermesone\u002Fstate.json` is written.                   |\n\n## Notes & guardrails\n\n- **Host-level code execution.** Install\u002Fupdate download a native build from `fathah\u002Fhermes-desktop` and run it. The package verifies sha512 and (interactively) prompts, but only run it on explicit user intent — never automatically from an agent workflow.\n- **Preview, then install.** Use `plan` to show the release\u002Fasset\u002Fsize\u002Fsha512; in non-interactive contexts that preview is your approval gate.\n- **No credentials.** The tool needs no API key or account and performs no onchain or payment actions.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":26},{"author":24,"version":25},"fathah","0.2.0","Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64\u002Fx64), Windows (setup.exe), Linux (.AppImage). The interactive UI needs a TTY; in non-interactive contexts it falls back to plain output. Works in Claude Code and any environment with a shell and npm.","main","f9529dc2bfe073cfeb4f152284acc99c322f62ce","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills","https:\u002F\u002Fgithub.com\u002FCrawlrrAI","2026-08-19 20:13:42",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add CrawlrrAI\u002Fskills --skill hermesone",{"tool":38,"command":39},"bunx","bunx skills add CrawlrrAI\u002Fskills --skill hermesone",{"tool":41,"command":42},"pnpm","pnpm dlx skills add CrawlrrAI\u002Fskills --skill hermesone","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fhermesone\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"catalog.json","REFERENCE","参考文档",1809,"https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fhermesone\u002Fcatalog.json",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"hermesone.svg","ASSET","资产文件",8653,"https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fhermesone\u002Fhermesone.svg",[59,67,74,81,88,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AVVRQRP6G52EJ87F8YRS3J","rhagent","Trade and post on rhagent.bot via Bankr. EVERY claimed fill (Bankr Terminal, @bankrbot on X — tweet, reply, or mention — DM, or any other surface) MUST trade-post to rhagent.bot BEFORE the reply. Use via bankr_terminal or bankr_x+source_url; reply MUST paste post_url + ticker_url. Explorer\u002FBlockscout alone is a failure. Robinhood Chain swaps (ETH\u002FUSDG only, never USDC), copy-trade, App crypto\u002Fagentic. Triggers on rhagent, rhagents, rhagent.bot, trade-post, Copy this trade, Robinhood Chain, bankr_x, bankr_terminal.","MIT","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Frhagent\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AVSX1PMSP2XG35CHXJHV8Z","opensea-wallet","Set up and configure wallet signing providers for OpenSea transactions. Supports Privy, Turnkey, Fireblocks, Bankr, and local private keys. Required for executing trades (opensea-marketplace) and token swaps (opensea-swaps).","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fopensea\u002Fopensea-wallet\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AVSNPYYJWXXXMYSBW8CXRW","opensea-tool-sdk","Build, register, and gate AI-callable tool endpoints using the OpenSea Tool Registry (ERC-8257) on Base. Scaffold HTTPS tools with JSON Schema interfaces, register them onchain, gate access via NFT ownership or x402 pay-per-call (USDC), and call gated tools. For querying OpenSea marketplace data use opensea-api instead.","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fopensea\u002Fopensea-tool-sdk\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AVSH292KE97TPRD7NP7CTT","opensea-swaps","Swap ERC20 tokens across supported chains via OpenSea's cross-chain DEX aggregator. Get quotes with optimal routing, check token balances, and execute swaps. For NFT trading use opensea-marketplace, for querying token data use opensea-api.","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fopensea\u002Fopensea-swaps\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7AVSBJ2THSF024V3E4ZPVSJ","opensea-marketplace","Buy and sell NFTs on OpenSea's Seaport marketplace. Fulfill listings, accept offers, create new orders, cross-chain purchases, and sweep multiple listings. Requires wallet signing; for read-only queries use opensea-api instead.","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fopensea\u002Fopensea-marketplace\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7AVS4AJ0S0NWX95DREYTW6Q","opensea-api","Query OpenSea marketplace data via the official CLI, MCP server, or shell scripts. Get floor prices, collection stats, NFT details, token data, trending collections, drops, events, and search across Ethereum, Base, Arbitrum, Polygon, and more. Read-only operations; for trading use opensea-marketplace, for token swaps use opensea-swaps.","https:\u002F\u002Fgithub.com\u002FCrawlrrAI\u002Fskills\u002Fblob\u002Fmain\u002Fopensea\u002Fopensea-api\u002FSKILL.md",[],[]]