How do I install the Skill Vendor skill?

Run npx skillmds@latest add davesnx/skill-vendor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skill Vendor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skill Vendor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skill Vendor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skill Vendor?

davesnx (@davesnx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skill Vendor by davesnx — Agent Skill

Name: Skill Vendor
Author: davesnx

Skill Vendor

Keep the skills this repository publishes for other people, such as the mlx skills in ocaml-mlx/skills, in step with their upstream repository through the skill-vendor command. Use when the user says "vendor skills", "skill-vendor", "pull the mlx skills", "push the mlx skills upstream", or asks whether agents/skills/VENDOR is in sync. Not for moving skills between the Mac and nspawn; that is sync-skills.

davesnx 4447156 2 files · 7.7 KB Updated Sep 17, 2026

File contents

Skill vendor

agents/skills/VENDOR lists each upstream repository, its branch, the directory that holds the skills there, the pinned commit, and the skills copied from it. The copies under agents/skills/ are the working copies. skill-vendor moves changes in either direction, only when asked.

Steps

Run skill-vendor check and read every line. Each skill is up to date, upstream ahead, local ahead, new local, new upstream, diverged, or pending. Exit 1 means at least one skill needs a pull or push.
Pick the direction from those states and the user's request:
- Upstream moved and the user wants it: skill-vendor pull. It replaces the local copies and records the new commit in VENDOR.
- Local edits go upstream: skill-vendor push -m "<message>" commits on the upstream branch. For a pull request, add --branch <name>; the pin stays unchanged until that branch merges.
- diverged: stop and report. Both sides changed, and the user merges by hand.
Run skill-vendor check again. Every listed skill reads up to date, or local ahead for a branch push that is still open.
Commit agents/skills/VENDOR together with the skill copies it describes, only when the user asks for a commit.

Rules

pull refuses while a skill is local ahead, new local, or diverged. pull --force discards those local edits; use it only when the user says so.
push refuses while upstream is ahead. Pull first.
A new skill also needs whatever the upstream repository asks for, such as a README row or a plugin manifest entry. Push it on a branch and finish those by hand in the pull request.
Clones live under ~/.cache/skill-vendor. A failed clone or fetch means the machine lacks SSH access to the upstream. Report it; do not switch remotes.

Command details live in terminal/bin/README.md. After changing the command, run bash agents/skills/skill-vendor/tests/skill-vendor.sh.

---name: skill-vendordescription: Keep the skills this repository publishes for other people, such as the mlx skills in ocaml-mlx/skills, in step with their upstream repository through the skill-vendor command. Use when the user says "vendor skills", "skill-vendor", "pull the mlx skills", "push the mlx skills upstream", or asks whether agents/skills/VENDOR is in sync. Not for moving skills between the Mac and nspawn; that is sync-skills.---# Skill vendor`agents/skills/VENDOR` lists each upstream repository, its branch, thedirectory that holds the skills there, the pinned commit, and the skills copiedfrom it. The copies under `agents/skills/` are the working copies.`skill-vendor` moves changes in either direction, only when asked.## Steps1. Run `skill-vendor check` and read every line. Each skill is `up to date`, `upstream ahead`, `local ahead`, `new local`, `new upstream`, `diverged`, or `pending`. Exit 1 means at least one skill needs a pull or push.2. Pick the direction from those states and the user's request: - Upstream moved and the user wants it: `skill-vendor pull`. It replaces the local copies and records the new commit in `VENDOR`. - Local edits go upstream: `skill-vendor push -m "<message>"` commits on the upstream branch. For a pull request, add `--branch <name>`; the pin stays unchanged until that branch merges. - `diverged`: stop and report. Both sides changed, and the user merges by hand.3. Run `skill-vendor check` again. Every listed skill reads `up to date`, or `local ahead` for a branch push that is still open.4. Commit `agents/skills/VENDOR` together with the skill copies it describes, only when the user asks for a commit.## Rules- `pull` refuses while a skill is `local ahead`, `new local`, or `diverged`. `pull --force` discards those local edits; use it only when the user says so.- `push` refuses while upstream is ahead. Pull first.- A new skill also needs whatever the upstream repository asks for, such as a README row or a plugin manifest entry. Push it on a branch and finish those by hand in the pull request.- Clones live under `~/.cache/skill-vendor`. A failed clone or fetch means the machine lacks SSH access to the upstream. Report it; do not switch remotes.Command details live in[`terminal/bin/README.md`](../../../terminal/bin/README.md#vendor-published-skills).After changing the command, run `bash agents/skills/skill-vendor/tests/skill-vendor.sh`.

Frequently asked questions