---
title: "Search Clawhub Skills"
method: GET
path: "/api/agents/{agent_id}/skills/search"
tags: ["agents"]
---

# Search Clawhub Skills

`GET /api/agents/{agent_id}/skills/search`

## Request

- Base URL: `https://api.maritime.sh` (the document declares no server; this is the origin it was published from)
- URL: `https://api.maritime.sh/api/agents/{agent_id}/skills/search`
- Auth: HTTP bearer

Search the framework's community registry server-side: ClawHub
(clawhub.ai) for openclaw-family agents, skills.sh for hermes-family.

Why direct-to-registry instead of the in-container CLI search: the
registries are public, so going through the agent just adds a
runtime command round trip per query (and hermes's CLI
has no JSON output at all). The agent ownership check is still done
to authorize the caller.

Response: `{results: [{slug, displayName, summary, score, owner: {...},
updatedAt, stats: {stars, downloads, ...} | null}]}`. For ClawHub,
`slug` is the namespaced install ref (`owner/name`) — pass it verbatim
to the install endpoint.

## Path parameters

- `agent_id` string, required

## Query parameters

- `q` string: ClawHub search query (empty returns nothing)
- `limit` integer

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/maritime/apis/maritime-api.md) - [All operations](https://skmtc.dev/maritime/apis/maritime-api/llms.txt) - [OpenAPI document](https://skmtc.dev/maritime/apis/maritime-api/revisions/acd712090ad6?raw)