How do I install the Sync Skills skill?

Run npx skillmds@latest add noppu-labs/sync-skills 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.

What does the Sync Skills skill do?

Use when checking vendored skills for upstream updates, pulling or merging upstream changes into this repo, or re-baselining skills-lock.json after editing a vendored skill. It is listed under Coding & Dev Tools on SkillMD.

Is Sync Skills 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 Sync Skills?

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 Sync Skills free to use?

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

Who published Sync Skills?

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

Sync Skills by noppu-labs — Agent Skill

Name: Sync Skills
Author: noppu-labs

File contents

Sync vendored skills with upstream

Prerequisites: gh CLI authenticated. Run everything from the repo root.

Workflow

Run npm run sync -- status. States and what to do:
- up-to-date — nothing to do.
- local — our own skill, no upstream; nothing to sync.
- upstream-updated — safe fast-forward: npm run sync -- pull <plugin>/<skill>.
- locally-modified — we edited since the last baseline. If the edits are intentional, npm run sync -- accept <plugin>/<skill>.
- diverged — both sides changed: merge manually (section below).
- fetch-error (...) — upstream unreachable or moved; check source/skillPath in the plugin's skills-lock.json against the upstream repo.
After all changes: npm run sync -- verify, then commit with a message that lists which skills were pulled or merged and from which upstream commits.

Manual merge for diverged skills

Never blind-overwrite a diverged skill — pull --force discards our customizations.

npm run sync -- diff <plugin>/<skill> — full diff, vendored → upstream.
Identify which differences are OUR deliberate customizations (git log -p -- <plugin>/skills/<skill> shows how the vendored copy evolved) versus genuine upstream improvements.
Edit the vendored files to incorporate the upstream improvements while preserving every local customization. Read both versions fully before editing.
Re-baseline BOTH sides: npm run sync -- seed <plugin>/<skill> (accept only re-baselines the vendored hash and would leave the skill permanently flagged as upstream-updated).

Frequently asked questions

Sync Skills