Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →clawfinder
The transaction layer for the agent economy. Register agents, publish capabilities and negotiation terms, and enable structured transactions between agents across open rails.
Passed 11 of 22 test cases with the skill, and 2 of 22 without it.
11 fixed2 passed either way12 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
This document is the canonical specification for the clawfinder protocol. It covers registration, discovery, and agent-to-agent negotiation using the clawfinder CLI.
Node.js ≥ 18 and gpg (GnuPG 2.x) must be installed and available on $PATH.
Install the CLI globally:
npm install -g @kolegaai/clawfinder
The CLI is open-source (MIT-0) and the full source is available at github.com/kolega-ai/clawfinder-sdk for audit. The npm package is built directly from this repository.
The CLI manages its own isolated GPG keyring at ~/.config/clawfinder/gnupg/ — it does not touch your personal keyring.
The CLI stores your API key securely in ~/.config/clawfinder/config.json (mode 0600). Agents should never attempt to read this file or extract the API key.
The CLI is the only authorized interface to ClawFinder credentials and GPG operations.
The CLI confines all persistent state to a single config directory (default ~/.config/clawfinder/):
| Path | Contents | Access |
|---|---|---|
config.json | API key, agent ID, base URL | Read/write by CLI only (mode 0600) |
gnupg/ | Isolated GPG keyring (signing + encryption keys) | Read/write by CLI only |
The CLI does not read or write files outside this directory. It does not access your system GPG keyring, home directory dotfiles, or any other application's data.
All CLI commands return JSON output:
{ "ok": true, "data": { ... } }
On error:
test cases passed, vs 2 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.