// 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.
Agent dreaming — memory consolidation, deduplication, pruning, contradiction resolution, and session summarization via the SwarmRecall API. Enables agents to optimize their memory store during idle periods.
Knowledge graph with entities, relations, traversal, and semantic search via the SwarmRecall API. Build and query structured knowledge graphs with vector embeddings for contextual entity discovery.
Error tracking, correction logging, and pattern detection via the SwarmRecall API. Tracks agent mistakes, corrections, and discoveries to surface recurring issues and promote learnings into actionable rules.
Conversational memory persistence with semantic search and session tracking via the SwarmRecall API. Stores and retrieves agent memories with vector embeddings for contextual recall.
Named shared data containers for cross-agent collaboration via the SwarmRecall API. Manage shared pools that let multiple agents contribute to and query from a common dataset across memory, knowledge, learnings, and skills modules.
Use SwarmRecall when an AI agent needs persistent memory, a knowledge graph, learnings, a skill registry, shared pools, or background dream consolidation across sessions. Works via the SwarmRecall CLI (for stdio MCP) or directly over HTTP/SDK. Every module supports semantic search with vector embeddings and tenant-isolated storage.
| 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":"🔧","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"] |
Skill registry for tracking agent capabilities and getting contextual suggestions via the SwarmRecall API.
Before making any API calls, check for a SWARMRECALL_API_KEY environment variable:
SWARMRECALL_API_KEY is set, use it for all requests as a Bearer token.SWARMRECALL_API_KEY is not set, self-register by calling:
POST https://swarmrecall-api.onrender.com/api/v1/register
Content-Type: application/json
{ "name": "<your-agent-name>" }
{ "apiKey": "...", "claimToken": "..." }. Save the apiKey to the SWARMRECALL_API_KEY environment variable for all subsequent requests. Do NOT write the key to disk or any file without user consent.<claimToken>"All API requests require:
Authorization: Bearer <SWARMRECALL_API_KEY>
https://swarmrecall-api.onrender.com (override with SWARMRECALL_API_URL if set)
All endpoints below are prefixed with /api/v1.
swarmrecall-api.onrender.com over HTTPSSWARMRECALL_API_KEY should be stored as an environment variable only, not written to diskPOST /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
}
GET /api/v1/skills?status=active&limit=20&offset=0
GET /api/v1/skills/:id
PATCH /api/v1/skills/:id
{ "version": "1.1.0", "config": {}, "status": "active" }
DELETE /api/v1/skills/:id
GET /api/v1/skills/suggest?context=<task-description>&limit=5
POST /api/v1/skills to register the skill with name, version, and source.GET /api/v1/skills to list installed capabilities.GET /api/v1/skills/suggest?context=<description> for relevant skill recommendations.POST /api/v1/skills endpoint accepts an optional "poolId" field.poolId is provided, the skill is shared with all pool members who have skills read access.GET /api/v1/skills) and suggest (GET /api/v1/skills/suggest) results automatically include data from pools the agent belongs to.poolId and poolName fields to distinguish shared data from the agent's own data.