auto-skill-connector
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_skillA | Search the auto-skill database (~200k scraped Claude skills, MCP servers, and plugins) for the one that best matches a task, and return its full SKILL.md content so it can be read and followed immediately. Call this whenever the user's request might already be covered by an existing packaged skill/MCP server, before building something from scratch. Pass a short, keyword-rich description of the task. |
| install_skillA | Download a skill's SKILL.md (by url, as returned from recommend_skill) and install it into ~/.claude/skills//SKILL.md so Claude Code can invoke it as a normal /skill from now on, in any project. |
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 2 tools
The two tools have clearly distinct purposes: one searches and returns skill content, the other installs a skill from a URL. No overlap in functionality.
Both tools follow a consistent verb_noun pattern: 'install_skill' and 'recommend_skill', making them predictable and easy to distinguish.
With only two tools, the server feels minimal for a skill management system. While it covers the core workflow of finding and installing skills, it lacks tools for listing, updating, or removing skills, which limits its utility.
The server covers the basic find-and-install flow but is missing lifecycle operations like listing installed skills, updating, or removing them. Users may need additional tools to manage their skill set effectively.