Agent Skill Loader

io.github.back1plyPublished by GitHub account back1plyv1.2.1Updated Oct 25, 2026

Dynamically load Claude Code skills into AI agents without copying files.

Overview

AI-generated overview

A local MCP server that exposes your Claude Code skill folders to AI agents as prompts and tools, so skills load without copying files.

What you can do
Discover skills in configured directories, with an optional name or description filter, and read a skill's markdown instructions on demand, or inject them as slash-command prompts in clients that support MCP Prompts. Copy a skill permanently into the project's .agent/skills folder. Add, remove or list skill search paths at runtime, writing them to a project config file. Run diagnostics on scanned paths, readability and warnings. Notify the client when skills are added or removed via a file watcher.
When to use it
Use it when you keep a library of Claude Code skills and want Claude Desktop, Cursor or another MCP client to see them live, either as slash commands or as tools the agent calls on its own.
Requirements
Local process; Node.js 18 or newer, installed globally from npm or built from source. Skill directories are auto-detected from the default Claude plugins cache and a project-level skill-paths.json; optional environment variables MCP_SKILL_PATHS, MCP_WORKSPACE_ROOT and MCP_NO_WATCH adjust paths and disable the watcher. No authentication declared.
Before you install
install_skill copies skill folders into the workspace, and manage_search_paths writes to skill-paths.json, so both change files on disk; target paths are restricted to the current workspace. The server reads and scans whatever directories are configured, so point it only at folders you trust. The file watcher can be disabled in CI with MCP_NO_WATCH.

Installation

In SourceWeft

  1. Open Agent Skill Loader in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Agent Skill Loader 🧠

[npm version] [MCP Registry] [License: MIT] [Node.js Version] [TypeScript] [MCP]

Agent Skill Loader is a Model Context Protocol (MCP) server that acts as a bridge between your static Claude Code Skills library and dynamic AI agents (like Claude Desktop, Cursor, or any MCP client).

It exposes skills both as MCP Prompts (slash commands, zero tool calls needed) and as MCP Tools (for programmatic use). Skills are auto-discovered from configured directories and stay live — add a new SKILL.md and the client is notified automatically.

🚀 Features

  • MCP Prompts: Skills appear as slash commands in clients. No tool call needed to inject them.
  • Live updates: listChanged notification fires when skills are added or removed (via file watcher).
  • Discovery: list_skills — scans configured skill directories, with optional search filter.
  • Dynamic Learning: read_skill — fetches the SKILL.md content.
  • Persistence: install_skill — copies a skill permanently to your project.
  • Configuration: manage_search_paths — add/remove skill directories at runtime.
  • Troubleshooting: debug_info — diagnose configuration and path issues.

🛠️ Setup

Prerequisites

  • Node.js >= 18

Option A: Install from npm (Recommended)

bash
npm install -g agent-skill-loader

Then register in .mcp.json:

json
"agent-skill-loader": {  "command": "agent-skill-loader"}

Option B: Build from Source

bash
git clone https://github.com/back1ply/agent-skill-loader.gitcd agent-skill-loadernpm installnpm run build

Then register in .mcp.json:

json
"agent-skill-loader": {  "command": "node",  "args": ["<path-to-repo>/build/index.js"]}

📂 Configuration

The server automatically detects its workspace and aggregates skill paths from:

  1. Default: %USERPROFILE%\.claude\plugins\cache (Standard location)
  2. Dynamic Config: skill-paths.json (Located in the project root)

Environment Variables

VariableDescription
MCP_SKILL_PATHSJSON array or semicolon/comma-separated list of additional skill paths
MCP_WORKSPACE_ROOTOverride auto-detected workspace root
MCP_NO_WATCHSet to 1 to disable the file watcher (useful in CI)

Dynamic Path Management

You do not need to manually edit config files. Use the tool to manage paths at runtime:

  • Add: manage_search_paths(operation="add", path="F:\\My\\Deep\\Skills")
  • Remove: manage_search_paths(operation="remove", path="...")
  • List: manage_search_paths(operation="list") creates/updates skill-paths.json.

🤖 Usage

MCP Prompts (Slash Commands)

If your client supports MCP Prompts (Claude Desktop, Cursor, etc.), skills appear automatically as slash commands. Select a skill from the slash command menu to inject its content directly — no tool calls needed.

Tools

The agent has access to five tools:

  • list_skills(query?): Returns a JSON list of available skills. Optional query filters by name/description substring (case-insensitive).
  • read_skill(skill_name): Returns the markdown instructions for a skill.
  • install_skill(skill_name, target_path?): Copies the skill folder to .agent/skills/<name>. For security, target_path must be within the current workspace.
  • manage_search_paths(operation, path?): Add, remove, or list skill search paths.
  • debug_info(): Returns diagnostic information (paths, status, warnings).

Example Agent Prompt

"I need to write a DAX measure but I'm not sure about the best practices."

The agent will automatically call list_skills, find writing-dax-measures, call read_skill, and answer with expert knowledge. Or the user can invoke the skill directly as a slash command.

🔧 Troubleshooting

If skills aren't being discovered, use debug_info() to see:

  • search_paths: Which directories are being scanned
  • path_status: Whether each path exists and is readable
  • warnings: Any errors encountered during scanning (permission denied, empty files, etc.)

Example output:

json
{  "workspace_root": "C:/projects/agent-skill-loader",  "search_paths": {    "base": ["C:/Users/pc/.claude/plugins/cache"],    "dynamic": ["F:/My/Skills"],    "effective": ["C:/Users/pc/.claude/plugins/cache", "F:/My/Skills"]  },  "path_status": [    { "path": "C:/Users/pc/.claude/plugins/cache", "exists": true, "readable": true },    { "path": "F:/My/Skills", "exists": false, "readable": false }  ],  "skills_found": 12,  "warnings": [    { "path": "F:/My/Skills", "reason": "Directory does not exist" }  ]}

📦 Project Structure

  • src/index.ts: Main server logic (tools + prompts + watcher).
  • src/utils.ts: Skill scanning, description extraction, prompt helpers, debounce.
  • build/: Compiled JavaScript output.
  • package.json: Dependencies (@modelcontextprotocol/sdk, chokidar, zod).

🤝 Contributing

To add new skills, add a folder with a SKILL.md file to one of the watched directories. The server picks them up automatically and sends a listChanged notification — no restart required.

Source: README.md at commit 8e19c6b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.2.1LatestOct 15, 2026
  2. v1.0.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts