Skip to main content
New in version 3.0.0 Agent skills are directories containing instructions and supporting files that teach an AI assistant how to perform specific tasks. Tools like Claude Code, Cursor, and VS Code Copilot each have their own skills directories where users can add custom capabilities. The Skills Provider exposes these skill directories as MCP resources, making skills discoverable and shareable across different AI tools and clients.

Why Skills as Resources

Skills live in platform-specific directories (~/.claude/skills/, ~/.cursor/skills/, etc.) and typically contain a main instruction file plus supporting reference materials. When you want to share skills between tools or access them from a custom client, you need a way to discover and retrieve these files programmatically. The Skills Provider solves this by exposing each skill as a set of MCP resources. A client can list available skills, read the main instruction file, check the manifest to see what supporting files exist, and fetch any file it needs. This transforms local skill directories into a standardized API that works with any MCP client.

Quick Start

Create a provider pointing to your skills directory, then add it to your server.
Each subdirectory containing a SKILL.md file becomes a discoverable skill. Clients can then list resources to see available skills and read them as needed.

Skill Structure

A skill is a directory containing a main instruction file (default: SKILL.md) and optionally supporting files. The directory name becomes the skill’s identifier.
The main file can include YAML frontmatter to provide metadata. If no frontmatter exists, the provider extracts a description from the first meaningful line of content.

Resource URIs

Each skill exposes three types of resources, all using the skill:// URI scheme. The main instruction file contains the primary skill content. This is the resource clients read to understand what a skill does and how to use it.
The manifest is a synthetic JSON resource listing all files in the skill directory with their sizes and SHA256 hashes. Clients use this to discover supporting files and verify content integrity.
Reading the manifest returns structured file information.
Supporting files are any additional files in the skill directory. These might be reference documentation, code examples, or binary assets.

Provider Architecture

The Skills Provider uses a two-layer architecture to handle both single skills and skill directories.

SkillProvider

SkillProvider handles a single skill directory. It loads the main file, parses any frontmatter, scans for supporting files, and creates the appropriate resources.
Use SkillProvider when you want to expose exactly one skill, or when you need fine-grained control over individual skill configuration.

SkillsDirectoryProvider

SkillsDirectoryProvider scans one or more root directories and creates a SkillProvider for each valid skill folder it finds. A folder is considered a valid skill if it contains the main file (default: SKILL.md).
When scanning multiple root directories, provide them as a list. The first directory takes precedence if the same skill name appears in multiple roots.

Vendor Providers

FastMCP includes pre-configured providers for popular AI coding tools. Each vendor provider extends SkillsDirectoryProvider with the appropriate default directory for that platform. Vendor providers accept the same configuration options as SkillsDirectoryProvider (except for roots, which is locked to the platform default).
CodexSkillsProvider scans both system-level (/etc/codex/skills/) and user-level (~/.codex/skills/) directories, with system skills taking precedence.

Supporting Files Disclosure

The supporting_files parameter controls how supporting files (everything except the main file and manifest) appear to clients.

Template Mode (Default)

With supporting_files="template", supporting files are accessed through a ResourceTemplate rather than being listed as individual resources. Clients see only the main file and manifest in list_resources(), then discover supporting files by reading the manifest.
This keeps the resource list compact when skills contain many files. Clients that need supporting files read the manifest first, then request specific files by URI.

Resources Mode

With supporting_files="resources", every file in every skill appears as an individual resource in list_resources(). Clients get full enumeration upfront without needing to read manifests.
Use this mode when clients need to discover all available files without additional round trips, or when integrating with tools that expect flat resource lists.

Reload Mode

Enable reload mode to re-scan the skills directory on every request. Changes to skills take effect immediately without restarting the server.
With reload=True, the provider re-discovers skills on each list_resources() or read_resource() call. New skills appear, removed skills disappear, and modified content reflects current file state.
Reload mode adds overhead to every request. Use it during development when you’re actively editing skills, but disable it in production.

Client Utilities

FastMCP provides utilities for downloading skills from any MCP server that exposes them. These are standalone functions in fastmcp.utilities.skills.

Discovering Skills

Use list_skills() to see what skills are available on a server.

Downloading Skills

Use download_skill() to download a single skill, or sync_skills() to download all available skills.
Both functions accept an overwrite parameter. When False (default), existing skills are skipped. When True, existing files are replaced.

Inspecting Manifests

Use get_skill_manifest() to see what files a skill contains before downloading.