SkillForge MCP
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., "@SkillForge MCPlist all available 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.
SkillForge MCP
Universal Skills MCP server — load Markdown skills from arbitrary folders, lazy-by-design, cross-tool.
v1.0.0 — 5 MCP tools, 370 tests, 10 sample skills, modular architecture (all source files ≤ 400 lines).
What it is
A standalone Model Context Protocol server that exposes Markdown-defined skills (prompts, templates, scripts) to any MCP-capable LLM tool — Claude Code, OpenAI Codex CLI, Cursor, or custom clients via @modelcontextprotocol/sdk.
One skill folder. One config file. Any tool can ask for any skill on demand.
Why it exists
Pain | Today | With SkillForge |
Auto-loading 122+ skills per session burns ~4880 tokens on init | Every Claude Code session pays the toll, most skills are never used | Lazy MCP discovery — pay only for |
Hardcoded paths ( | One folder, one tool, hardcoded | Multi-folder, per-project, priority-ordered, env override |
No cross-tool format | Each tool ships its own skill layout | Universal frontmatter parser auto-detects Claude / Codex / persona / custom dialects |
Skill execution = "just inline body in prompt" | No scripts, no caching, no timeouts, no composition | Strategy pattern (prompt / script / hybrid) + decorator chain (logging → timeout → cache) + composite skills with cycle detection |
Quick Start
Option 1 — Claude Code marketplace (recommended)
/plugin marketplace add lyupro/llm-plugins-marketplace
/plugin install skillforge-mcp@lyupro-llm-pluginsRestart your Claude Code session. The five tools (skills__list, skills__get, skills__invoke, skills__configure, skills__reload) appear in the tool list.
Option 2 — npm
claude mcp add skillforge -- npx -y @lyupro/skillforge-mcpWorks for any MCP host that can spawn a stdio command (Claude Code, Codex CLI, Cursor).
Option 3 — local build
See Contributing.
After install, point SkillForge at your skill folder:
> use skills__configure with action="add_folder", folder="/abs/path/to/your/skills"
> use skills__listSee docs/INSTALL.md for Codex CLI, Cursor, and manual MCP-client setups.
Verify Installation
After the install step, run these three checks from inside any wired LLM tool session:
skills__list— returns an array of skill summaries (possibly empty if no skills folders are configured yet).skills__configurewithaction: "list_folders"— shows the resolved folder list with priorities andenabledflags.skills__reload— forces a fresh scan, returns{loaded, added, removed, errors}diff.
If any call fails with [skillforge] fatal: on stderr, the most likely cause is a corrupt config file or a missing folder path — the error message points at the offending file. Delete or fix ~/.lyupro/.skillforge/config.json and retry.
MCP tool surface
Tool | Purpose |
| Enumerate available skills (metadata only). Filters: |
| Fetch full SKILL.md body + metadata for one skill. |
| Execute a skill via its assigned strategy, wrapped in the decorator chain (Logging → Timeout → Cache). Composite skills ( |
| Manage configured folders + manual blacklist. Actions: |
| Force a full rescan of all configured folders. Returns |
Configure which folders to scan
By default SkillForge scans ~/.claude/plugins/cache/claude-code-skills/. Override via environment:
# Windows (PowerShell)
$env:SKILLFORGE_FOLDERS = "C:\path\to\skills;C:\other\folder"
# macOS / Linux
export SKILLFORGE_FOLDERS=/home/me/skills:/home/me/team-skillsPath separator is platform-native (; on Windows, : elsewhere). Or use skills__configure to manage the persisted list — see docs/CONFIGURATION.md.
For shared content across multiple tools, the convention is ~/.lyupro/skills/ (Lyu Pro brand shared content folder).
Persisted config + hot reload
Config file:
~/.lyupro/.skillforge/config.json(resolved cross-platform viaos.homedir()). Schema-validated via Zod; missing → schema defaults; corrupt JSON / schema → loud error with the file path.Merge order for folders:
SKILLFORGE_FOLDERSenv (when set) > persistedfolders[]withenabled: truesorted byprioritydesc > built-in default.Auto-audit:
security.autoAudit: true(default) scans skill bodies on load againstsecurity.auditPatterns(default:shell=True,eval(,exec(,base64.b64decode). Matched skills are excluded and logged to stderr.Manual blacklist:
blacklist: string[]excludes skills by exact name (case-sensitive). Short-circuits before the audit step.Hot reload: chokidar watches all configured folders for
.mdadd/change/unlink events. Debounced batches invalidate the metadata cache so the nextskills__listre-scans. Folders mutated viaskills__configureauto-re-watch via the same diff path.
Skill format
Any .md file with a YAML frontmatter block defining at least name::
---
name: apple-hig-check
description: Audit code against Apple Human Interface Guidelines.
tags: [ios, design]
---
You are an Apple HIG expert. When asked to review code...Optional camelCase fields validated by SkillMetadata: strategy (prompt / script / hybrid), allowScripts, allowNetwork, skills (composite — string[] of nested skill names invoked sequentially), timeoutMs, cacheable, cacheTtlMs, scripts (string[], single-entry — main.py / entry.sh / app.mjs). Anything else passes through to extra.
FormatDetector recognizes Claude (SKILL.md), Codex (AGENTS.md), persona-style (frontmatter has persona:), and generic-custom dialects automatically.
Full spec: docs/SKILL_FORMAT.md.
Architecture (one-liner)
MCP request → Tool handler → Registry lookup → DecoratorChain.wrap(strategy).invoke(skill, ctx) → Logging → Timeout → Cache → Strategy (Prompt / Script / Hybrid / Composite-resolver) → InvocationResult
Patterns used: Registry, Strategy, Factory, Adapter, Decorator (chain composition), Composite (sequential nested invocation), Observer (chokidar), Singleton.
Full design: docs/ARCHITECTURE.md.
Limitations
Read this before enabling scripts.
ScriptStrategy runs user-provided scripts in a SandboxRunner subprocess. The sandbox is best-effort env/cwd isolation, not an OS-grade jail. Node child_process cannot guarantee network isolation, filesystem confinement outside cwd, or CPU/memory limits — those require Docker/firecracker/gVisor (future enhancement).
Property | Enforced? | How |
| Yes | Subprocess receives only |
Temp | Yes | Fresh |
Abort signal | Yes |
|
stdout/stderr cap | Yes | Tail-truncate at 1 MB each. |
Network egress | No | Subprocess inherits host network stack. |
Filesystem reads outside | No | Subprocess has full OS user permissions. |
Filesystem writes outside | No | Same. |
CPU / memory limits | No | Only the timeout decorator wall-clock-kills runaways. |
Defence in depth layered on top:
Global gate —
config.security.allowScripts: falseby default.Per-skill opt-in —
metadata.allowScripts: truerequired per skill.Audit pattern scanner —
PatternScannerdetectsshell=True,eval(,exec(, base64 decode patterns in skill bodies before load.Manual blacklist — explicit skill names in
config.security.blacklist.
For production use with untrusted skill authors, run SkillForge inside Docker or another OS-level sandbox. Full threat model: docs/SECURITY.md.
Updating
# Marketplace install
/plugin update skillforge-mcp@lyupro-llm-plugins
# npm install
claude mcp remove skillforge
claude mcp add skillforge -- npx -y @lyupro/skillforge-mcp@latest
# Local-build install
cd skillforge-mcp
git pull
pnpm install
pnpm buildThe wiring in Claude Code / Codex / Cursor points at the same binary path — restarting the host session picks up the new build. Your persisted config at ~/.lyupro/.skillforge/config.json survives the upgrade.
Documentation
Doc | Audience |
First-time setup for Claude Code, Codex CLI, Cursor, manual MCP clients | |
Skill authors — full frontmatter spec, dialect detection, examples | |
Power users — folder management, blacklist, sandbox config, env overrides | |
Contributors — design patterns, module responsibilities, extension points | |
Security-conscious operators — threat model, audit checklist, sandbox limits, disclosure policy | |
Per-tool wiring guides (claude-code / codex / cursor / custom-llm-tools) | |
10 ready-to-use sample skills (prompt / script / hybrid examples) | |
Sample |
Contributing
Local build (for development or pre-publish testing):
git clone https://github.com/lyupro/skillforge-mcp.git
cd skillforge-mcp
pnpm install
pnpm build
# Wire into Claude Code using the absolute path
claude mcp add skillforge -- node /absolute/path/to/skillforge-mcp/dist/server.jsDevelopment commands:
pnpm install
pnpm dev # tsx watch src/server.ts
pnpm test # vitest run
pnpm test:coverage # coverage report
pnpm lint # tsc --noEmit
pnpm check:size # file-size gate (≤400 lines per file)
pnpm build # emit dist/
pnpm smoke # post-build subprocess smoke testLicense
MIT — see LICENSE.
Author
lyupro — independent dev. Part of the Lyu Pro tooling portfolio.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
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/lyupro/skillforge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server