scientific-skills-hub
Related Servers
Alternatives to scientific-skills-hub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that serves agent skills (SKILL.md bundles) to any MCP client, exposing them via tools and resources for tool-oriented and resource-aware clients.313 npmISC
- AlicenseNot gradedqualityBmaintenanceDiscovers and manages portable agent capabilities (skills and MCP servers) from configurable collections, providing search, inspection, and local installation via CLI and MCP tools.1MIT
- AlicenseBqualityCmaintenanceMCP (Model Context Protocol) Server for skill4agent - Search, view, and install AI skills in AI conversations.310 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, install, and manage SKILL.md skills from a Git-backed registry via MCP tools for search, install, and list operations.4 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable agents to search, inspect, lint, and safely install Agent Skills from the skillmd registry mid-conversation.01MIT
TDQS
Scored across 8 tools
Each tool targets a clearly distinct operation: search, card metadata, file content, bundle fetch, compatibility, diff, diagnostics, and issue reporting. The three get_skill_* tools have similar prefixes but their descriptions clearly separate card metadata, directory file content, and packaged bundle downloads.
Tool names mostly follow a consistent verb_noun snake_case pattern such as search_skills, check_compatibility, and report_skill_issue. The one-word command 'doctor' deviates slightly, but it is a recognizable conventional diagnostic command and does not create confusion.
Eight tools is well within the ideal 3-15 range and each tool fills a distinct role in the scientific-skills hub workflow: discovery, inspection, retrieval, compatibility, version comparison, health checking, and issue feedback. No tool feels redundant or extraneous.
The set covers the main consumption workflow: search, view card, read content, fetch bundle, check compatibility, diff versions, diagnose issues, and report problems. Minor gaps exist around explicit listing or publishing new skills, but those appear outside the hub's stated consumption-focused scope.