ClawHub skills

01

The skills

Every path below is under https://api.superagnt.com.

Calls under /v1/data spend credits from your organization's balance, and each response carries its price in meta.costCents: see Data sources and, for the agnt endpoints, People and companies. A connection skill needs the vendor connected in the workspace first. Its calls run on that account and cost no superagnt_ credits (Connections), and it tells the agent to confirm with you before it deletes, overwrites or sends anything.

Each data skill also names its scoped MCP endpoint, https://mcp.superagnt.com/mcp/<facet>, and each connection skill the root endpoint, for an agent that can connect over MCP instead: see Scoped entry points.

02

Install

openclaw skills install @superagnt/social-data

clawhub install superagnt/social-data

Always include the owner: several of these slugs, such as social-data, youtube-data and email-finder, also name other publishers' skills on ClawHub.

openclaw skills install puts the skill in the skills folder of the active agent workspace, or in the shared ~/.openclaw/skills with --global. The ClawHub CLI installs into the skills folder of its working directory, which defaults to the agent workspace in your OpenClaw config, or the current directory; pass --workdir to choose it. Start a new OpenClaw session if the agent does not list the skill.

03

Give it the API key

Every skill reads the key from SUPERAGNT_API_KEY, and declares that variable and curl as requirements, so OpenClaw only offers the skill to the agent once both are there. Create an API key in the superagnt app (see Managing API keys), then either set SUPERAGNT_API_KEY in the gateway's environment (for example in ~/.openclaw/.env), or give the key to the skill in openclaw.json:

{
  "skills": {
    "entries": {
      "social-data": {
        "apiKey": "agnt_live_..."
      }
    }
  }
}

The entry is keyed by the skill's name, which is its slug without the owner. OpenClaw passes apiKey to the skill as SUPERAGNT_API_KEY when the agent runs on the host. A sandboxed run does not get it, so give the sandbox the variable as well.

openclaw skills check lists any installed skill that is missing a requirement. To test the key itself, run the same first call every skill tells the agent to make:

curl -s https://api.superagnt.com/v1/credits \
  -H "Authorization: Bearer $SUPERAGNT_API_KEY"

A body with success: true and your balances means the key works. A 401 means it is missing, revoked or mistyped.

04

Update and remove

openclaw skills update @superagnt/social-data

openclaw skills update --all updates every ClawHub skill in the workspace, and clawhub update --all does the same for skills the ClawHub CLI installed. An update keeps your local edits to a skill unless you add --force, or, with clawhub update, answer yes when it asks to overwrite them. To remove a skill, run clawhub uninstall @superagnt/social-data, with --workdir pointing at the folder that holds its skills folder: the agent workspace, or ~/.openclaw for a --global install.

05

Troubleshooting