Skip to main content
Glama
ai.backskills/backskills

ai.backskills/backskills

by domco685

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BACKSKILLS_KEYNoOptional API key. If unset, a free key is registered on first tool call.
BACKSKILLS_URLNoThe 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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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