Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SKILL_DEBUGNoSet to '1' or 'true' to log registry selection and diagnostics to stderr.
GITHUB_TOKENNoOptional GitHub token; sent as Authorization on api.github.com calls to raise API rate limits.
SKILL_REGISTRYNoRegistry selection mode: auto (token present → skills.sh, else GitHub), skills-sh, or github.auto
SKILLS_SH_TOKENNoOptional. Enables the skills.sh API mode with richer data (install counts, leaderboard views). Obtainable from a Vercel project via OIDC.
SKILL_MAX_BYTESNoRegistry-level byte cap applied to loaded skill content.200000
SKILL_GITHUB_SOURCESNoComma-separated owner/repo list for GitHub mode.vercel-labs/skills, anthropics/skills, obra/superpowers, mattpocock/skills, microsoft/azure-skills, supabase/agent-skills, prisma/skills

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_skillsA

List available agent skills from the registry (skills.sh / GitHub). Returns compact metadata only (id, name, source, installs) - NO descriptions or content, so it is cheap on context. Use this to browse what is available before searching.

search_skillsA

Search for agent skills by keyword (name or description). Returns compact results: id, name, source, installs, and a short description preview (<=300 chars) when include_description is true. Use this to find a skill for a task. Query must be at least 2 characters.

load_skillA

Load the FULL content of one skill by id (e.g. "vercel-labs/skills/find-skills" or "anthropics/skills/document-skills"). Returns the complete SKILL.md plus optional supporting files. Use ONLY when you have decided to use a specific skill and need its full instructions - this is the expensive (context-heavy) call; prefer list_skills/search_skills first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct role: list for browsing, search for finding by keyword, load for retrieving full content. There is no overlap in functionality or purpose.

Naming Consistency4/5

Tools follow a verb_noun pattern, but 'list_skills' and 'search_skills' use plural while 'load_skill' uses singular. This minor inconsistency is predictable and does not cause confusion.

Tool Count5/5

With 3 tools, the server is well-scoped for a skill registry: browse, search, and retrieve full content. Each tool serves a necessary function without unnecessary bloat.

Completeness5/5

The tool surface covers the full workflow for discovering and using skills: listing available skills, searching them, and loading the full content when needed. No obvious gaps exist for the stated purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues