auto-skill-loader
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@auto-skill-loaderload my active skills"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
auto-skill-loader
Give your AI agent a persistent skill library it auto-loads at session start.
OpenCode image note: OpenCode doesn't yet expose real file paths when you paste images — the agent sees a filename instead. Workaround: give the agent an actual file path instead of pasting. Skills auto-load at session start as expected.
mcp-name: io.github.divitkashyap/auto-skill-loader
How it works
You configure which skills to auto-load in
~/.config/auto-skill-loader/config.yamlThe MCP server reads skill files from your skills directory and exposes them via
skills://activeAt session start your agent reads
skills://activeand gets all approved skills auto-injectedNo explicit triggers needed — the agent already knows your skills
Related MCP server: hermes-mcp-server
Why
The main problem: In OpenCode, skills don't auto-load — the agent has to explicitly invoke them or rely on unreliable fuzzy matching. auto-skill-loader solves this by exposing your skill library as an MCP resource that gets read at session start. Deterministic, no guessing.
Bonus: Our proxy tools also work around OpenCode's broken MCP stdio transport for the MiniMax vision and web search tools.
Installation
Option 1: uvx (recommended — no install needed)
uvx auto-skill-loaderOption 2: pip
pip install auto-skill-loader
auto-skill-loaderOption 3: Build from source
git clone https://github.com/divitkashyap/auto-skill-loader.git
cd auto-skill-loader
pip install -e .
auto-skill-loaderConfiguration
OpenCode
Add to ~/.config/opencode/opencode.json:
{
"mcp": {
"auto-skill-loader": {
"type": "local",
"command": ["uvx", "auto-skill-loader"],
"enabled": true
}
}
}Claude Code
Note: Claude Code requires a specific JSON format via add-json:
claude mcp add-json -s user auto-skill-loader '{"type":"stdio","command":"/FULL/PATH/TO/python","args":["-m","server"],"env":{"MINIMAX_TOKEN_PLAN_KEY":"sk-cp-YOUR-KEY-HERE"}}'Replace /FULL/PATH/TO/python with the path to your Python (e.g. /Users/YOU/auto-skill-loader/.venv/bin/python).
Or for uvx (requires network on first run):
claude mcp add -s user --transport stdio -e MINIMAX_TOKEN_PLAN_KEY=sk-cp-YOUR-KEY auto-skill-loader -- uvx auto-skill-loaderTested On
Host | Skill Auto-Load | Vision Proxy | Image Paste | Notes |
Claude Code (macOS) | ✅ | ❌ Not needed | ✅ | Use |
OpenCode (macOS) | ✅ | ✅ Works | ❌ Broken | Give file paths instead of pasting |
Skill auto-loading confirmed working on both hosts. The vision proxy bypasses OpenCode's broken stdio transport, but image paste-to-path is a separate rendering issue in OpenCode that requires using file paths.
Other MCP-compatible hosts (Cursor, Zed, etc.) should work with the same configuration — contributions welcome.
Platform Differences & Known Issues
Image Input: OpenCode vs Claude Code
Both hosts work with auto-skill-loader vision tools, but image input behaves differently:
Host | How images are passed | Recommended workflow |
Claude Code | Images uploaded to URL automatically → tool receives URL | Paste image directly ✅ works |
OpenCode | Inline images render visually but may not give tools a real path | Give a file path instead of pasting |
OpenCode note: When you paste an image in OpenCode, it may render inline but the agent sees it as a filename string (e.g. logo.png) rather than a real filesystem path. This is a known OpenCode rendering behavior.
Workaround for OpenCode: Instead of pasting, give the agent the actual file path:
analyze this image: /path/to/your/image.pngThe agent can access local files directly in OpenCode. If the image is only in your clipboard, the agent can extract it to /tmp/ first.
What We're Monitoring
We actively track the following OpenCode issues:
Inline image rendering (images pasted don't expose real paths to tools)
MCP stdio transport for local servers (our proxy tools work around this)
Session persistence of skills across restarts
If OpenCode releases a fix for inline image paths, this documentation and the vision-analysis skill will be updated to support direct paste workflow. We monitor OpenCode's changelog and release notes — check this repo for updates.
Other Known Issues
Issue | Severity | Workaround |
OpenCode inline images show as filename, not path | Medium — affects paste workflow | Use file paths instead |
Claude Code auth conflict (ANTHROPIC_AUTH_TOKEN vs managed key) | Low — cosmetic warning | Harmless, can be ignored |
First vision call may take 3-5s (uvx download) | Low — one-time | Subsequent calls are ~200ms |
Setup
Create skills directory (symlink to your existing skills):
mkdir -p ~/.config/auto-skill-loader
ln -sf ~/.config/opencode/skills ~/.config/auto-skill-loader/skillsEdit
~/.config/auto-skill-loader/config.yaml:
active_skills:
- vision-analysis
- context-maintainer
- markdown-mcp
skills_dir: ~/.config/auto-skill-loader/skillsRestart your agent. It will now auto-load all listed skills at session start.
Tools
Tool | What it does |
| List all available skills in skills_dir with descriptions |
| Add a skill to your approved list (persists to config.yaml) |
| Remove a skill from your approved list |
| Get details about a specific skill |
| List currently active skill names |
| If no skills are active, suggests common ones to get started |
| Validate a skill's dependencies (MCP tools, API keys, env vars) |
Bonus: MiniMax Vision & Web Search Proxy
auto-skill-loader also exposes two tools that proxy to minimax-coding-plan-mcp with a working stdio transport:
Tool | What it does |
| Analyze images (JPEG, PNG, GIF, WebP up to 20MB) |
| Web search using MiniMax |
Note: For vision specifically, mmx-cli is now the recommended approach — it's a direct REST call to MiniMax VLM, no MCP transport issues, and handles URLs natively. These proxy tools are useful if you want a unified MCP interface for both skill loading and vision.
The OpenCode MCP Bug
When OpenCode's built-in minimax-coding-plan-mcp MCP integration (minimax-token-plan) is configured, the understand_image tool fails with:
API Error: login fail: Please carry the API secret key in the 'Authorization' fieldThis happens even when:
✅
MINIMAX_API_KEY/MINIMAX_TOKEN_PLAN_KEYis set correctly✅ API key is valid (same key works via direct API calls)
✅ Token Plan has available vision quota
Root cause: OpenCode's stdio transport for local MCP servers sends messages in a way that breaks the MCP protocol — likely batched writes without proper flush between JSON-RPC messages. Direct subprocess tests with sequential writes + flush() work fine.
The fix: Our proxy tools in auto-skill-loader use proper sequential stdio communication, bypassing OpenCode's broken transport layer.
Setup
Set your MiniMax Token Plan key in
~/.config/opencode/.env:
MINIMAX_TOKEN_PLAN_KEY=sk-cp-your-key-hereAdd auto-skill-loader to
~/.config/opencode/opencode.json:
{
"mcp": {
"auto-skill-loader": {
"type": "local",
"command": ["/path/to/venv/bin/python", "-m", "server"],
"enabled": true
}
}
}Critical: If you have
minimax-coding-plan-mcpconfigured directly in opencode.json (theminimax-token-planentry), remove or disable it — its broken stdio transport will cause "login fail" errors. The proxy tools in auto-skill-loader replace it entirely.Restart OpenCode and verify:
/ask Do you have auto-skill-loader_minimax_understand_image available?
Diagnosis
If you see "login fail" errors after setup:
Disable the broken minimax MCP — ensure
"minimax-token-plan": { "enabled": false }or remove it entirelyRestart OpenCode completely — MCP servers are re-spawned on each session
Check with:
/ask Call minimax_understand_image with image_source="/any/real/image.png" and prompt="test"
Resources
Resource | What it does |
| All approved skill contents concatenated — read by host at session init |
| Your current config.yaml content |
Security
User-controlled — only skills in
config.yamlare loadedNo network fetches — everything is local
No prompt injection — skills come from your own configured directory
Repo Structure
auto-skill-loader/
├── src/
│ └── server.py # MCP server (Python stdlib + mcp package)
├── pyproject.toml # Package config
├── README.md # This file
├── SKILL.md # For agent onboarding
└── LICENSE # MITRequirements
Python 3.9+
mcppackage (pip install mcp)pyyamlpackage (pip install pyyaml)
Or just use uvx auto-skill-loader which fetches dependencies automatically.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables file system operations, web scraping, and AI-powered search through MCP tools for use by LLM agents.1
- AlicenseNot gradedqualityBmaintenanceBridges MCP-compatible AI clients to over 100 Hermes Agent skills for web browsing, file management, code execution, GitHub operations, and more.1MIT
- AlicenseAqualityBmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseNot gradedqualityBmaintenanceProvides 20 essential tools including HTTP requests, web search, file I/O, shell commands, and persistent memory for any MCP client, with zero configuration required.MIT
Related MCP Connectors
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Stealth web browser for agents: search, fetch, click and type through persistent sessions over MCP.
Shared long-term memory vault for AI agents with 20 MCP tools.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/divitkashyap/auto-skill-loader'
If you have feedback or need assistance with the MCP directory API, please join our Discord server