ai.backskills/backskills
Related Servers
Alternatives to ai.backskills/backskills
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables assistants to search for MCP servers, agent skills and plugins, then inspect their packages, publishers, repositories, domains, documentation, security review signals and recorded history before use. Watch passes keep collecting and comparing dependency and publisher changes over time with sources and dates.MIT No Attribution
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to audit and manage installed skills and MCP servers across harnesses, profile startup token overhead, inspect bundled assets, safely remove unused skills, and check for updates via native tools and a local dashboard.MIT
- AlicenseNot gradedqualityCmaintenanceCatalogues skills and agents into a queryable graph, exposing MCP tools for reference counting, usage scanning, and overlay notes with a built-in visual viewer.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to observe a remote Hermes deployment's agents, sessions, crons, skills, and tools, and to run one-shot remote agent chats via a chat tool.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
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.