Personal Code Skills MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_PATH | No | Subdirectory containing skill files (default: root) | |
| GITHUB_TOKEN | No | GitHub personal access token (required for private repos) | |
| SKILLS_REPO_NAME | Yes | GitHub repository name | |
| SKILLS_REPO_OWNER | Yes | GitHub repository owner (username or organization) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsB | Returns a list of all available best practice skills |
| get_skillC | Returns the content of a specific best practice 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 2 tools
The two tools have clearly distinct purposes: get_skill retrieves detailed content for a specific skill, while list_skills provides an overview of all available skills. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern (get_skill and list_skills), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.
With only 2 tools, the server feels thin for a 'Personal Code Skills' domain that implies management of skills. While basic read operations are covered, the lack of create, update, or delete tools suggests an incomplete surface for skill management, making the count too low for the apparent scope.
The server only provides read operations (get and list), with no ability to create, update, or delete skills. This is a significant gap for a skills management domain, as agents cannot modify or add new skills, leading to potential dead ends in workflows that require full lifecycle management.