Skillhub Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Skillhub Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<p align="center"> <img src="./assets/logo.png" alt="Skillhub MCP logo" width="160" /> </p>
mcp-name: io.github.214140846/skillhub-mcp
You already have Claude-style skills (SKILL.md), but in practice you often hit a wall:
Skillhub MCP bridges that gap: it turns Claude-style skills into MCP tools, so any MCP client can call the same skills.
⚠️ Experimental. Skills may contain scripts/resources. Treat them as untrusted and run with sandboxes/containers when possible.
This project is an MCP server.
.zip and .skill archivesfetch_resource tool for clients without native MCP resource supportstdio (default), http, sseDefault skills root: ~/.skillhub-mcp
{
"skillhub-mcp": {
"command": "uvx",
"args": ["skillhub-mcp@latest"]
}
}Use a custom skills root:
{
"skillhub-mcp": {
"command": "uvx",
"args": ["skillhub-mcp@latest", "/path/to/skills"]
}
}Below are minimal working examples for mainstream “vibe coding” editors.
Cursor supports configuring MCP servers via mcp.json. Add the following to your global ~/.cursor/mcp.json or project .cursor/mcp.json, then restart Cursor.
{
"mcpServers": {
"skillhub-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["skillhub-mcp@latest", "/path/to/skills"]
}
}
}Option A: configure via Claude Code CLI (recommended for quick setup):
claude mcp add --transport stdio skillhub-mcp -- uvx skillhub-mcp@latest /path/to/skillsOption B: project-scoped configuration via .mcp.json at your project root. You may need to explicitly allow project MCP servers in .claude/settings.json.
./.mcp.json
{
"mcpServers": {
"skillhub-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["skillhub-mcp@latest", "/path/to/skills"]
}
}
}./.claude/settings.json (approve only this server)
{
"enabledMcpjsonServers": ["skillhub-mcp"]
}Option A: use the Codex CLI to add a stdio MCP server:
codex mcp add skillhub-mcp -- uvx skillhub-mcp@latest /path/to/skillsOption B: edit ~/.codex/config.toml:
[mcp_servers.skillhub-mcp]
command = "uvx"
args = ["skillhub-mcp@latest", "/path/to/skills"]Skillhub MCP discovers skills under the root directory (default ~/.skillhub-mcp). Each skill can be:
SKILL.md.zip or .skill archive containing SKILL.md (at the archive root orinside a single top-level folder)
All other files become downloadable MCP resources for your agent to read. Note: Skillhub MCP does not execute scripts; the client decides whether/how to run them.
Example layout:
~/.skillhub-mcp/
├── summarize-docs/
│ ├── SKILL.md
│ ├── summarize.py
│ └── prompts/example.txt
├── translate.zip
├── analyzer.skill
└── web-search/
└── SKILL.mdArchive rules:
translate.zip
├── SKILL.md
└── helpers/
└── translate.jsdata-cleaner.zip
└── data-cleaner/
├── SKILL.md
└── clean.pyClaude Code expects a flat skills directory (each immediate subdirectory is one skill). Skillhub MCP is more permissive:
.zip / .skill packaged skills are supportedIf you need Claude Code compatibility, keep the flat layout.
skillhub-mcp [skills_root] [options]
| Flag / Option | Description |
|---|---|
positional skills_root | Optional skills directory (defaults to ~/.skillhub-mcp). |
--transport {stdio,http,sse} | Transport (default stdio). |
--host HOST | Bind address for HTTP/SSE transports. |
--port PORT | Port for HTTP/SSE transports. |
--path PATH | URL path for HTTP transport. |
--list-skills | List discovered skills and exit. |
--verbose | Emit debug logging. |
--log | Mirror verbose logs to /tmp/skillhub-mcp.log. |
README.mdREADME.zh-CN.mdI focus on AI SaaS going global, covering the full journey from idea validation and vibe coding to product development, infrastructure, SEO, backlinks, and growth experiments.
Everything shared here comes from real projects, real traffic, and real revenue attempts.
Thor’s AI Going-Global Content Planning
A structured knowledge base documenting hands-on experience in AI product overseas expansion, including demand discovery, execution strategies, and common pitfalls.
Long-form notes and case studies on building, launching, and iterating AI products in public.
Smart Campus System
Sharing real-time thoughts on indie hacking, AI tools, and product growth.
An online platform for AI-powered video generation, focused on practical use cases and real user workflows.
Model pages:
A curated collection of AI video and image generation tools, experiments, and capability tracking.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.