SkillGild
OfficialRelated Servers
Alternatives to SkillGild
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and IDEs to discover, install, and execute skills over Model Context Protocol via stdio or SSE, with semantic search and framework bridges.Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceProvides access to 224 battle-tested skills plus multi-agent orchestration, exposed as tools for Claude or Codex.-
- AlicenseAqualityDmaintenanceSearch, install, and manage AI agent skills (SKILL.md files) from GitHub repositories. Features workspace analysis for personalized recommendations and supports 140+ pre-indexed skills.940 npm12Creative Commons Attribution Non Commercial Share Alike 4.0 International
- AlicenseBqualityBmaintenanceConnects AI coding agents to a library of procedural AI skills, verified code snippets, and executable shell commands. It enables searching, retrieving, saving, and injecting these resources into agent context.7626 npmMIT
- AlicenseAqualityDmaintenanceEnables discovering, fetching, validating, and converting Claude skills from the skills.sh marketplace and GitHub repositories.825 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to search, score, review, and submit tools from the SkillsIndex directory of 11,000+ AI agent tools.971 npmMIT
TDQS
Scored across 5 tools
Each tool has a distinct role: search, prompt-pipeline execution, hybrid-session lifecycle (start/call/end). The main possible confusion is between skillgild_run_skill and skillgild_start_session, but the descriptions explicitly route prompt_pipeline vs hybrid_tools skills, so boundaries remain clear.
All tools use a consistent skillgild_ prefix followed by a snake_case verb_noun pattern (search_skills, run_skill, start_session, call_tool, end_session). No mixed conventions or vague naming.
Five tools is well-scoped for this server: one discovery tool, two execution modes, and two session lifecycle controls. Each tool earns its place without redundancy.
The surface covers discovery, both execution modes, and session cleanup, which are the core workflows. Minor gaps exist, such as a dedicated get-skill-detail tool or entitlement inspection, but search and runtime responses provide enough metadata to work around them.