Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search the skill-builder registry and auto-install skills for Claude Code, Cursor, and Codex.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SKILL_API_URL, SKILL_TOKEN, SKILL_PROJECT_DIR, SKILL_TARGETValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"skill-builder": {
"command": "npx",
"args": [
"-y",
"@dmzagent/skill-builder-mcp"
],
"env": {
"SKILL_API_URL": "your-value",
"SKILL_TOKEN": "your-value",
"SKILL_PROJECT_DIR": "your-value",
"SKILL_TARGET": "your-value"
}
}
}
}Run this in your terminal
claude mcp add skill-builder --env SKILL_API_URL=your-value --env SKILL_TOKEN=your-value --env SKILL_PROJECT_DIR=your-value --env SKILL_TARGET=your-value -- npx -y @dmzagent/skill-builder-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"skill-builder": {
"command": "npx",
"args": [
"-y",
"@dmzagent/skill-builder-mcp"
],
"env": {
"SKILL_API_URL": "your-value",
"SKILL_TOKEN": "your-value",
"SKILL_PROJECT_DIR": "your-value",
"SKILL_TARGET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"skill-builder": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dmzagent/skill-builder-mcp"
],
"env": {
"SKILL_API_URL": "your-value",
"SKILL_TOKEN": "your-value",
"SKILL_PROJECT_DIR": "your-value",
"SKILL_TARGET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SKILL_API_URL envSKILL_PROJECT_DIR envSKILL_TARGET envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The publisher (dmzagent.com) is not the repo owner (praeceptor-thesis); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SKILL_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Publish and install AI skill prompts from the command line — or author them in the web editor with help from an AI drafting assistant.
npx @dmzagent/skill-builder install @author/skill-id
Results print as a dense table right in your terminal:
npx @dmzagent/skill-builder list
Filter by category, author, type, tag, and sort order:
npx @dmzagent/skill-builder list --category "Developer Tools"
npx @dmzagent/skill-builder list --type meta # only meta skills npx @dmzagent/skill-builder list --author skillauthor npx @dmzagent/skill-builder list --sort downloads npx @dmzagent/skill-builder list --json # machine-readable npx @dmzagent/skill-builder list --web # open the browser registry instead
npx @dmzagent/skill-builder search "data pipeline" # ranked by relevance
npx @dmzagent/skill-builder info @skillauthor/dialogue-flow npx @dmzagent/skill-builder suggest dial # autocomplete: skills, tags, authors
Wire up shell completion (skills, tags, and authors complete as you type):
npx @dmzagent/skill-builder completion >> ~/.bashrc
npx @dmzagent/skill-builder install dialogue-flow
npx @dmzagent/skill-builder install @skillauthor/dialogue-flow
Downloads dialogue-flow.md and dialogue-flow.json to the current directory. Use --output ./my-skills to change where files land.
Meta skills install their dependencies automatically. Installing a meta skill resolves its full dependency tree (deduped, cycle-safe) and installs every required skill alongside it. Use --no-deps to install just the meta skill.
npx @dmzagent/skill-builder install @skillauthor/my-bundle
npx @dmzagent/skill-builder register myhandle "My Name" me@email.com
You'll be prompted for a password. Or set SKILL_PASSWORD to skip the prompt:
SKILL_PASSWORD=hunter2 npx @dmzagent/skill-builder register myhandle "My Name" me@email.com
npx @dmzagent/skill-builder login me@email.com
Your auth token is printed on success. Set it as SKILL_TOKEN so subsequent commands can use it:
export SKILL_TOKEN=<token-from-login>
(Or pass --token $SKILL_TOKEN to each command.)
From a markdown file:
npx @dmzagent/skill-builder publish ./my-skill.md
The CLI reads the filename as the skill id and the first heading as the name. You can also use a JSON manifest:
npx @dmzagent/skill-builder publish ./my-skill.json
A skill can declare what a model must be able to do to invoke it. The declaration lives on the spec, so it travels with the skill through the registry, the CLI, and MCP — an agent can tell whether it is able to run a skill before it spends a turn on it.
{
"capabilities": [ { "id": "vision", "level": "required", "note": "reads chart images" }, { "id": "long-context", "level": "preferred" } ] }
required capabilities gate execution: the registry refuses to run a skill on a runtime that cannot provide one, unless the caller explicitly forces a degraded run. preferred capabilities only weaken the result. Catalog ids:
vision · audio-input · file-input · structured-output · streaming
extended-reasoning · long-context · multilingual tool-use · parallel-tool-calls · code-execution · web-search · file-system computer-use · mcp-client persistent-memory · citations
Custom ids are accepted for anything the catalog does not model yet. info and list show the contract, and install rolls it up across a meta skill's whole dependency tree — a meta skill only runs where every skill it installs can run.
npx @dmzagent/skill-builder info @skillauthor/chart-reader
npx @dmzagent/skill-builder fork @skillauthor/dialogue-flow --name my-dialogue
Creates a copy under your account that you can republish.
scripts/backfill-dependencies.mjs finds existing skills that implicitly orchestrate other skills and proposes explicit dependencies + type: "meta" for them. It reads every skill, detects references to other *real* registry skills (by full id, install directives, or distinctive names), scores a confidence level, and merges a curated set of known-correct mappings.
It is dry-run by default — it prints a report and writes nothing:
node scripts/backfill-dependencies.mjs # report only
node scripts/backfill-dependencies.mjs --json # machine-readable
To apply, pass --apply with a token. Only skills owned by the token's account are updated (others are listed and skipped), so run it once per publishing account:
SKILL_TOKEN=<token> node scripts/backfill-dependencies.mjs --apply
node scripts/backfill-dependencies.mjs --apply --include-medium # also apply medium-confidence
Confidence tiers: curated and high (explicit id / install / distinctive-name references) apply by default; medium (fuzzy name match) only with --include-medium; meta-no-deps (orchestration language but no concrete dependency) is reported for manual review and never auto-applied.
Applying requires the registry to run the worker build that understands
type/dependencies(it derivestypeand regenerates markdown on save).
The dry-run report works against any deployed version.
Coding agents — Claude Code, Cursor, Codex, and other MCP clients — can search the registry and auto-install skills (resolving meta-skill dependency trees) via the @dmzagent/skill-builder-mcp MCP server.
// e.g. .mcp.json (Claude Code) or .cursor/mcp.json (Cursor)
{ "mcpServers": { "skill-builder": { "command": "npx", "args": ["-y", "@dmzagent/skill-builder-mcp"] } } }
Tools: skill_search, skill_info, skill_suggest, skill_taxonomy, and skill_install (writes skill files for the detected tool). See packages/mcp/README.md for per-client setup.
Visit the skill studio at https://skills.dmzagent.com. The workspace is three collapsible panes plus a settings drawer:
{{variables}} highlighted, examples and tests, and a publish-readiness checklist that links into the field behind each gap.npm install
npm run dev --workspace packages/web
MIT