
Auto Skill Loader
io.github.divitkashyapPublished by GitHub account divitkashyapv1.0.1Updated Nov 3, 2026
Auto-loads skills into agent sessions. MiniMax vision and search proxy.
Overview
Local MCP server that auto-loads a configured skill library into agent sessions and adds MiniMax image analysis and web search proxy tools.
- What you can do
- List, inspect and check prerequisites of skills in your skills directory
- Activate or deactivate skills, persisting the approved list to config.yaml
- Read the active skill set and current config as MCP resources at session start
- Analyze images (JPEG, PNG, GIF, WebP up to 20MB) through a MiniMax proxy
- Run web searches through a MiniMax proxy
- When to use it
- Useful when your host does not auto-load skills and you want a deterministic, user-curated skill library injected at session start, or when you want MiniMax vision and search behind a working stdio transport in OpenCode.
- Requirements
- Local Python process (Python 3.9+, mcp and pyyaml packages, or run via uvx, which needs network on first run). A skills directory and a config.yaml listing active skills. The secret MINIMAX_TOKEN_PLAN_KEY is required for the MiniMax proxy tools.
Installation
In SourceWeft
- Open Auto Skill Loader in the dashboard and add it to a workspace.
- 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
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.yaml - The MCP server reads skill files from your skills directory and exposes them via
skills://active - At session start your agent reads
skills://activeand gets all approved skills auto-injected - No explicit triggers needed — the agent already knows your skills
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)
Option 2: pip
Option 3: Build from source
Configuration
OpenCode
Add to ~/.config/opencode/opencode.json:
Claude Code
Note: Claude Code requires a specific JSON format via add-json:
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):
Tested On
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:
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:
The 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
Setup
- Create skills directory (symlink to your existing skills):
- Edit
~/.config/auto-skill-loader/config.yaml:
- Restart your agent. It will now auto-load all listed skills at session start.
Tools
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:
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:
This 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:
- Add auto-skill-loader to
~/.config/opencode/opencode.json:
-
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 entirely - Restart 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
Security
- User-controlled — only skills in
config.yamlare loaded - No network fetches — everything is local
- No prompt injection — skills come from your own configured directory
Repo Structure
Requirements
- Python 3.9+
mcppackage (pip install mcp)pyyamlpackage (pip install pyyaml)
Or just use uvx auto-skill-loader which fetches dependencies automatically.
Source: README.md at commit cf24477
Tools
0Version history
1- v1.0.1LatestSep 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
