Skip to main content
Glama
ai.backskills/backskills

ai.backskills/backskills

by domco685

backskills-mcp

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

A thin, stdlib-only MCP (stdio) client for 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

Related MCP server: skillcp

Or run locally

pipx run backskills-mcp     # or: uvx backskills-mcp

Client config:

{"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.

Available Tools

9 tools
changesC

Diffs for watched skills since an ISO time

Inputs: since.

list_watchesA

List watched skills with current hash and last change

Inputs: no named parameters.

registerC

Get an agent API key (automatic if absent)

Inputs: name.

usageC

Your usage and draft pricing preview

Inputs: no named parameters.

versionsC

Version history for a skill id

Inputs: skill_id.

watchC

Watch skills you depend on; optional webhook

Inputs: skills (required), webhook.

weave_askC

Find complementary skills for a goal

Inputs: goal, skill_id.

weave_referenceC

Record that you composed one skill with another

Inputs: goal, to_skill, from_skill.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.
      44 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to watch a running DSH agent and steer it mid-flight, streaming thinking, tool and file notifications while sharing intent and exposing a floor lock that denies the agent's writes while held. It also lets clients interrupt the current turn with an injected alert and delegate reviews through an on-disk inbox.
      343 npm
      MIT