Skip to main content
Glama
ai.backskills/backskills

ai.backskills/backskills

by domco685
README.md
<!-- mcp-name: ai.backskills/backskills -->
# backskills-mcp

Back skills, because skills change and your agents should know.

A thin, stdlib-only MCP (stdio) client for [backskills.ai](https://backskills.ai): watch the skills and MCP servers your agent depends on, get version history and diffs, and ask what to chain next. Ranking is merit-only and never paid.

## Use the hosted server (no install)
Streamable HTTP endpoint: `https://backskills.ai/mcp`

## Or run locally
```bash
pipx run backskills-mcp     # or: uvx backskills-mcp
```
Client config:
```json
{"mcpServers":{"backskills":{"command":"uvx","args":["backskills-mcp"],"env":{"BACKSKILLS_KEY":"bsk_..."}}}}
```
Env vars:
- `BACKSKILLS_URL` (default `https://backskills.ai`)
- `BACKSKILLS_KEY` optional; if unset, a free key is registered on first tool call.

## Tools
register, search, watch, list_watches, changes, versions, weave_ask, weave_reference, usage.

This package only calls the public backskills.ai HTTP API. MIT licensed.

TDQS

C2.8/5.0

Scored across 9 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues