skillsh-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_skillsA | Search for skills on skills.sh by query term (e.g., "mapbox", "react", "gis") |
| get_skill_detailsA | Get detailed information about a specific skill by owner/repo/skillId |
| get_popular_skillsC | Get popular skills from the leaderboard |
| get_install_commandB | Get the npx install command for a skill |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: searching, fetching details, retrieving popular skills, and generating install commands. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (search_skills, get_skill_details, get_popular_skills, get_install_command). The verbs 'search' and 'get' are semantically appropriate and the pattern is uniform.
With only 4 tools, the server is well-scoped for a skills directory service. Each tool earns its place and covers the core actions without unnecessary clutter.
The tool surface covers the full discovery-to-installation workflow: searching, viewing details, browsing popular items, and getting the install command. No obvious missing operations for its read-only purpose.