How it works
Get from scattered local skills to a governed, securely connected library in four steps — then connect any MCP client.
- 1
Connect a Git source
Point the hub at a GitHub repo of skills. The hub syncs them and you choose which ones to publish.
- 2
Control access
Grant each skill org-wide, per team, or per person — least privilege, no scattered local copies.
- 3
Connect your AI client
Add the OAuth 2.1 connector in claude.ai / Claude Desktop, or use a scoped personal access token in Claude Code / Codex.
- 4
Your agents use the skills
Agents discover and run exactly the skills you granted — favorites preloaded into context.
Connect via the OAuth 2.1 connector (claude.ai & Claude Desktop)
In claude.ai or Claude Desktop, add a custom connector and point it at the hub’s MCP endpoint. You’ll sign in and authorize access — no static secrets to paste.
Connector type: Custom (MCP)
MCP server URL: https://www.skillsmanager.uk/mcp
Auth: OAuth 2.1 (you'll be prompted to sign in)Connect via a personal access token (Claude Code & Codex)
For CLI clients, generate a personal access token in the hub and scope it to the skills that client should have. Then add the server to your MCP client config:
{
"mcpServers": {
"makeitfuture-skills": {
"url": "https://www.skillsmanager.uk/mcp",
"headers": {
"Authorization": "Bearer <YOUR_PERSONAL_ACCESS_TOKEN>"
}
}
}
}You generate and scope tokens, and copy the exact connector URL, from the in-app Configure MCP page after you sign in.