MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill.
$ npx skills add BuilderIO/skills --skill adding-a-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/skills adding-a-skill --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-a-skill .claude/skills/adding-a-skill && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .claude/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuilderIO/skills --skill adding-a-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/skills adding-a-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-a-skill .agents/skills/adding-a-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .agents/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill adding-a-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/skills adding-a-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-a-skill .cursor/skills/adding-a-skill && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .cursor/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuilderIO/skills.git --path .agents/skills/adding-a-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuilderIO/skills --skill adding-a-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/skills adding-a-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-a-skill .gemini/skills/adding-a-skill && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .gemini/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuilderIO/skills adding-a-skillInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuilderIO/skills --skill adding-a-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-a-skill .github/skills/adding-a-skill && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .github/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill adding-a-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuilderIO/skills adding-a-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-a-skill .opencode/skills/adding-a-skill && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adding-a-skill" agent skill from https://github.com/BuilderIO/skills/tree/main/.agents/skills/adding-a-skill into .opencode/skills/adding-a-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-skill", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
adding-a-skillUse in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill.
Adding A Skill is an agent skill from BuilderIO/skills. Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill. Covers the repo-local skill files, root catalog docs, plugin metadata, @agent-native/skills dynamic install path, optional managed AGENTS/CLAUDE instruction blocks in ../agent-native/framework, and generated/synced Plan skill gotchas.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Agent Workflows. It works with Model Context Protocol. The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 530d9ee. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxpython3nodepnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, npx and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Adding A Skill loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 616 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from BuilderIO/skills at commit 530d9ee, republished under its MIT licence (© BuilderIO). 616 words, ~1,562 tokens.
.claude/skills/adding-a-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use this for public skill work in this repo. Keep ordinary skill changes in
skills/<skill-name>/; keep repo-only guidance under .agents/skills/.
skills/<name>/ with
SKILL.md. This is the common case. @agent-native/skills discovers these
dynamically from BuilderIO/skills@main, so there is no framework registry to
edit just to make npx @agent-native/skills@latest add --skill <name> work.AGENTS.md / CLAUDE.md line when users pass
--update-instructions. These need one extra framework change; see
"Managed Instruction Blocks" below.../agent-native/framework/packages/core/src/cli/skills.ts and
../agent-native/framework/packages/skills/src/built-in-apps.ts.visual-plan and visual-recap have generated/synced copies
between this repo and ../agent-native/framework. Do not treat them like a
standalone prose folder.SKILL.md is generated from Agent Native because
the instructions and local Screen Memory tools share one privacy contract.
Keep the human README here; use npm run sync:agent-native-skills for the
generated skill instead of editing it by hand.Create or update skills/<skill-name>/SKILL.md.
Add skills/<skill-name>/README.md when the skill should appear in the
public catalog. This repo intentionally uses READMEs for public skill pages.
If the collection positioning changes, update root README.md,
.codex-plugin/plugin.json, .claude-plugin/plugin.json, and package.json
descriptions.
Keep the skill concise. Put only essential agent instructions in SKILL.md;
avoid extra docs unless they directly support the skill.
Validate with:
python3 /Users/steve/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/<skill-name>Smoke-test install discovery locally before claiming the CLI path works:
node ../agent-native/framework/packages/skills/dist/cli.js add --copy . --skill <skill-name> --client codex --scope project --dry-run --jsonRun npm run check. If it fails on visual-plan / visual-recap sync while
the change is unrelated, report that specifically instead of rewriting those
skills casually.
For a plain public skill, the install path is dynamic:
../agent-native/framework/packages/skills/src/index.ts sets
DEFAULT_SKILLS_SOURCE = "BuilderIO/skills".
It materializes that repo, reads plugin manifests via resolveSkillsRoot, and
discovers every skills/*/SKILL.md through discoverSkills.
Therefore a new folder under skills/<name>/ is enough for:
npx @agent-native/skills@latest add --skill <name>No @agent-native/core built-in registry change is needed unless the skill is
app-backed or needs custom install behavior.
If the skill should affect AGENTS.md / CLAUDE.md through
--update-instructions, update the framework wrapper:
Add a concise line in
../agent-native/framework/packages/skills/src/index.ts inside
instructionContentForSkill(skillName).
Add or update tests in
../agent-native/framework/packages/skills/src/index.spec.ts.
Run:
pnpm --filter @agent-native/skills test -- src/index.spec.ts --runInBandUse this for durable behavior rules like quick-recap, efficient-fable,
stay-within-limits, and likely docs-first behavior such as
read-the-damn-docs.
If a skill needs hosted tools, auth, MCP registration, local-files mode, or special install flags, inspect the framework before editing:
../agent-native/framework/packages/core/src/cli/skills.ts../agent-native/framework/packages/skills/src/built-in-apps.ts../agent-native/framework/packages/skills/src/sync-with-core.spec.tsKeep the core and standalone @agent-native/skills MCP descriptors in sync.
visual-plan, visual-recap, and rewind are special:
npm run check compares those copies and can fail for drift
unrelated to a new plain skill.sync-plan-marketplace, sync-workspace-skills, and skills.sync.spec.ts.SKILL.md is generated from
packages/core/src/cli/skills-content/rewind-skill.ts. Its public README is
preserved as an overlay. The plain-copy installer cannot configure Rewind's
local MCP connection; public setup docs must use @agent-native/skills or
@agent-native/core.skills/ directory must carry an
always-on setup directive: invoking Rewind with Clips absent asks permission
before opening the official install flow, never installs or enables capture
silently, and keeps Rewind unavailable until Core configures the local MCP
connection and screen_memory_status succeeds.When finishing a skill change, tell the user:
@agent-native/skills dynamic install discovery is enough.© BuilderIO, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .agents/skills/adding-a-skill of BuilderIO/skills.
Open the folder on GitHubat commit 530d9ee
Adding A Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Adding A Skill this skillBuilderIO/skills | 4.5k | — | ~1.6k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 37k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
BuilderIO/skills
A skill your agent uses when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log…
BuilderIO/skills
A skill your agent uses when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed…
BuilderIO/skills
A skill your agent uses when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done"…
BuilderIO/skills
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…
BuilderIO/skills
A skill your agent uses when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window…
BuilderIO/skills
A skill your agent uses when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy…
Works with
Categories
Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill. Adding A Skill is an agent skill from BuilderIO/skills. Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill.
Adding A Skill fits situations like: agent Workflows work in your project.
Run `npx skills add BuilderIO/skills --skill adding-a-skill -a claude-code`. Or copy the skill folder (.agents/skills/adding-a-skill in BuilderIO/skills) into .claude/skills/adding-a-skill in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BuilderIO/skills --skill adding-a-skill -a codex`. Or copy the skill folder (.agents/skills/adding-a-skill in BuilderIO/skills) into .agents/skills/adding-a-skill in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuilderIO/skills --skill adding-a-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-a-skill, .gemini/skills/adding-a-skill, .github/skills/adding-a-skill and .opencode/skills/adding-a-skill in your project.
Going by SKILL.md and its folder, Adding A Skill needs the command-line tools its instructions call (npm, npx, python3, node and pnpm). Our summary lists: Python 3; Node.js.
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Adding A Skill is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Adding A Skill: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 37k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BuilderIO (a GitHub organization) maintains it in BuilderIO/skills, which has 4,528 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 7, 2026.
Source: BuilderIO/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.