ai.backskills/backskills
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKSKILLS_KEY | No | Optional API key. If unset, a free key is registered on first tool call. | |
| BACKSKILLS_URL | No | The base URL of the backskills server. | https://backskills.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| registerC | Get an agent API key (automatic if absent) |
| searchC | Search skills and MCP servers |
| watchC | Watch skills you depend on; optional webhook |
| list_watchesA | List watched skills with current hash and last change |
| changesC | Diffs for watched skills since an ISO time |
| versionsC | Version history for a skill id |
| weave_askC | Find complementary skills for a goal |
| weave_referenceC | Record that you composed one skill with another |
| usageC | Your usage and draft pricing preview |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly different operations: watch/list_watches/changes form a monitoring trio with distinct meanings, and versions vs changes are separable (history vs diffs). The main soft spot is search vs weave_ask, which both return skills but with different intents (query vs goal-driven complement discovery), and the two weave_ tools require reading descriptions to keep apart.
Mixed conventions: some tools are bare lowercase verbs (register, search, watch), some are bare nouns (changes, versions, usage), and two use a namespace_prefix pattern (weave_ask, weave_reference) alongside an unrelated snake_case list_watches. The names are readable but there is no single predictable pattern.
Nine tools is well within the ideal range and each maps to a concrete need: auth, discovery, monitoring, versioning, composition, and billing. Nothing feels padded or redundant in count.
The lifecycle is largely covered — register, search, watch, list_watches, changes, versions, composition discovery/recording, and usage. The notable gap is no unwatch/stop-watching operation and no way to enumerate recorded weaves, leaving agents unable to reverse actions they can take.