Back to Directory/Developer Tools

io.github.back1ply/agent-skill-loader

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

Developer ToolsTypeScriptv1.0.2

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)

npm install -g agent-skill-loader

Then register in .mcp.json:

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

Option B: Build from Source

git clone https://github.com/back1ply/agent-skill-loader.git
cd agent-skill-loader
npm install
npm run build

Then register in .mcp.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:

{
  "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.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y agent-skill-loader

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-back1ply-agent-skill-loader": {
      "command": "npx",
      "args": [
        "-y",
        "agent-skill-loader"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

agent-skill-loadernpm

Compatible MCP Clients

io.github.back1ply/agent-skill-loader works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More