- name
- swarmrecall-skills
- description
- Skill registry for tracking agent capabilities and getting contextual suggestions via the SwarmRecall API. Register, list, and query installed skills with semantic matching for task-relevant recommendations.
- metadata
- openclaw
- emoji
- \F527
- requires
- env
- [SWARMRECALL_API_KEY]
- primaryEnv
- SWARMRECALL_API_KEY
- privacyPolicy
- Skill registry data is stored on SwarmRecall servers (swarmrecall-api.onrender.com). Data is scoped per agent and owner. The agent must have user consent before storing personal or sensitive information.
- dataHandling
- All data is transmitted over HTTPS. Skills are stored in PostgreSQL with pgvector embeddings. Data is tenant-isolated by owner ID and agent ID.
- version
- 1.1.0
- author
- swarmclawai
- homepage
- https://www.swarmrecall.ai
- tags
- [skills, ai-agents, skill-registry, persistence, suggestions]
SwarmRecall Skills
Skill registry for tracking agent capabilities and getting contextual suggestions via the SwarmRecall API.
Auto-Registration
Before making any API calls, check for a SWARMRECALL_API_KEY environment variable:
- If
SWARMRECALL_API_KEYis set, use it for all requests as a Bearer token. - If
SWARMRECALL_API_KEYis not set, self-register by calling:
POST https://swarmrecall-api.onrender.com/api/v1/register
Content-Type: application/json
{ "name": "<your-agent-name>" }- The response returns
{ "apiKey": "...", "claimToken": "..." }. Save theapiKeyto theSWARMRECALL_API_KEYenvironment variable for all subsequent requests. Do NOT write the key to disk or any file without user consent. - Tell the user: "SwarmRecall is set up! To manage your agent's data, visit swarmrecall.ai/claim with code:
<claimToken>"
Authentication
All API requests require:
Authorization: Bearer <SWARMRECALL_API_KEY>API Base URL
https://swarmrecall-api.onrender.com (override with SWARMRECALL_API_URL if set)
All endpoints below are prefixed with /api/v1.
Privacy & Data Handling
- All data is sent to
swarmrecall-api.onrender.comover HTTPS - Skill registry data is stored server-side with vector embeddings for semantic search
- Data is isolated per agent and owner — no cross-tenant access
- Before storing user-provided content, ensure the user has consented to external storage
- The
SWARMRECALL_API_KEYshould be stored as an environment variable only, not written to disk
Endpoints
Register a skill
POST /api/v1/skills
{
"name": "code-review",
"version": "1.0.0",
"source": "clawhub/code-review",
"description": "Automated code review with inline suggestions",
"triggers": ["review", "PR"],
"dependencies": ["git"],
"config": {},
"poolId": "<uuid>" // optional — write to shared pool
}List skills
GET /api/v1/skills?status=active&limit=20&offset=0Get a skill
GET /api/v1/skills/:idUpdate a skill
PATCH /api/v1/skills/:id
{ "version": "1.1.0", "config": {}, "status": "active" }Remove a skill
DELETE /api/v1/skills/:idGet skill suggestions
GET /api/v1/skills/suggest?context=<task-description>&limit=5Behavior
- On skill install: call
POST /api/v1/skillsto register the skill with name, version, and source. - On "what can I do?": call
GET /api/v1/skillsto list installed capabilities. - On task context: call
GET /api/v1/skills/suggest?context=<description>for relevant skill recommendations.
Shared Pools
- The
POST /api/v1/skillsendpoint accepts an optional"poolId"field. - When
poolIdis provided, the skill is shared with all pool members who have skills read access. - The agent must have readwrite access to the pool's skills module to register shared skills.
- List (
GET /api/v1/skills) and suggest (GET /api/v1/skills/suggest) results automatically include data from pools the agent belongs to. - Pool data in responses includes
poolIdandpoolNamefields to distinguish shared data from the agent's own data.