get_default_skillsLABSCO SUMMARY
A switchboard for what the agent knows.
The three tools are deliberately few; the product is the UI in front of them, where you group skills and flip them on or off so an agent only carries what a task needs. The always-loaded versus dynamic split is the point — some knowledge should be present every session, some should be fetched by name only when relevant. One non-obvious step: the tools alone are not enough, the README wants MCP_instructions.md pasted into the agent's system prompt.
What it is
A self-hosted web application plus MCP server for managing AI skills, workflows and contexts. You organise skills into groups in a local web UI and toggle them on or off; the MCP server then loads what is enabled into an agent, either automatically or on demand.
What you get
- Every skill marked
always_loadedpulled into context at once —get_default_skills - All enabled skills listed with their descriptions and modes —
list_available_skills - A specific
dynamicskill loaded on demand by name —load_full_skill_context - A web UI to create, edit, organise and search skills and workflows, with per-group enable/disable toggles and drag-and-drop
- Two loading modes per skill — always-loaded, or dynamic on-demand
- Import from a local folder, a GitHub repository, or the Skills.sh registry, plus token counting to track context size
- Isolated workspaces (hubs), with the server aware of the active one
Requirements
Node and Python. Install is a clone plus chmod +x setup.sh and ./setup.sh, which generates mcp_settings.json with the correct paths; the web app runs with npm start on http://localhost:3000. The generated MCP entry launches mcp_server.py through the project's .venv Python. The package.json names the web app context-manager-web at 1.0.0. The README stresses one setup step beyond the tools: the contents of MCP_instructions.md must be copied into the agent's system prompt or rules, or the three tools have no usage guidance. A starter library of skills and workflows is copied into your hub on first setup.
Setup effort
Build from source — git clone https://github.com/One-Man-Company/Skills-ContextManager.git
USE CASES
01
Loading only the skills a task needs
Toggle groups on in the web UI, then let the agent pull the enabled always-loaded set at session start.
02
Fetching a specialised skill on demand
Have the agent list what is available and load one dynamic skill by name only when the work calls for it.
03
Bringing existing skills in from elsewhere
Import from a local folder, a GitHub repository or the Skills.sh registry rather than recreating them.
04
Keeping separate skill sets for separate projects
Use isolated hubs so each workspace exposes its own skills, with the server tracking the active one.
3 tools
Listed in project docs. Your client may show a different list.
list_available_skillsload_full_skill_contextBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/One-Man-Company/Skills-ContextManager.git
cd Skills-ContextManager
chmod +x setup.sh
./setup.sh
cd Skill-ContextManager && npm startAdd the entry from mcp_settings.json to your agent's MCP settings, and copy the contents of MCP_instructions.md into the agent's system prompt or rules
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"Skills-ContextManager": {
"command": "<YOUR_ABSOLUTE_PATH>/Skills-MCP/.venv/bin/python3",
"args": [
"-u",
"<YOUR_ABSOLUTE_PATH>/Skills-MCP/mcp_server.py"
],
"env": {}
}
}
}
