How do I install the Sync Skill Repo skill?

Run npx skillmds@latest add hu-wentao/sync-skill-repo 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 Sync Skill Repo 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 Skill Repo?

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 Skill Repo free to use?

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

Who published Sync Skill Repo?

Hu-Wentao (@hu-wentao) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sync Skill Repo by hu-wentao — Agent Skill

Name: Sync Skill Repo
Author: Hu-Wentao

Sync Skill Repo

Hidden compatibility backend for publishing explicitly selected shared skills. Invoke explicitly for legacy sync commands or deterministic batch validation, testing, exact-path commit and push, named Skills CLI updates, and installation/lock verification. Project-private skills are rejected.

Hu-Wentao Updated Sep 17, 2026

File contents

Sync Skill Repo Backend

Use skillcraft for ownership and revision decisions. This hidden skill preserves explicit compatibility and owns only deterministic publication mechanics.

Canonical batch command

uv run python <skill-root>/scripts/sync_skill_repo.py publish-batch \
  --repo <source-repository> \
  --skill <name> [--skill <name> ...] \
  [--include-path <explicit-path>] \
  [--project-root <consumer-project>] \
  [--expected-upstream-head <sha> --expected-source-head <sha>]

The runner validates budgets and references, runs each scripts/tests/run.py, stages only explicit paths, creates at most one commit, pushes once, runs pnpm dlx skills update <name> -y once per name from a neutral cwd, verifies matching installations and locks, and emits sync-skill-repo.publish-receipt.v2 JSON.

Existing ahead commits require both exact head arguments. Input under package/node_modules, project-private source, skills-config, ambiguous locks, unrelated dirty paths, non-GitHub upstreams, stale heads, or missing update locks fails closed. A push followed by update failure returns completed: false.

Compatibility commands

register <repo>: register a local shared source checkout.
publish <skill-dir>: one-skill compatibility publication.
sync <skill-dir>: copy a valid lock-managed skill to registered source.
refresh and install: explicit recovery/first-install compatibility operations.

Do not use compatibility commands to bypass skillcraft ownership classification.

Resource

scripts/sync_skill_repo.py: canonical publisher and compatibility backend.
scripts/tests/run.py: complete backend test entry point.

---name: sync-skill-repodescription: Hidden compatibility backend for publishing explicitly selected shared skills. Invoke explicitly for legacy sync commands or deterministic batch validation, testing, exact-path commit and push, named Skills CLI updates, and installation/lock verification. Project-private skills are rejected.---# Sync Skill Repo BackendUse `skillcraft` for ownership and revision decisions. This hidden skill preserves explicit compatibility and owns only deterministic publication mechanics.## Canonical batch command```bashuv run python <skill-root>/scripts/sync_skill_repo.py publish-batch \ --repo <source-repository> \ --skill <name> [--skill <name> ...] \ [--include-path <explicit-path>] \ [--project-root <consumer-project>] \ [--expected-upstream-head <sha> --expected-source-head <sha>]```The runner validates budgets and references, runs each `scripts/tests/run.py`, stages only explicit paths, creates at most one commit, pushes once, runs `pnpm dlx skills update <name> -y` once per name from a neutral cwd, verifies matching installations and locks, and emits `sync-skill-repo.publish-receipt.v2` JSON.Existing ahead commits require both exact head arguments. Input under `package/node_modules`, project-private source, `skills-config`, ambiguous locks, unrelated dirty paths, non-GitHub upstreams, stale heads, or missing update locks fails closed. A push followed by update failure returns `completed: false`.## Compatibility commands- `register <repo>`: register a local shared source checkout.- `publish <skill-dir>`: one-skill compatibility publication.- `sync <skill-dir>`: copy a valid lock-managed skill to registered source.- `refresh` and `install`: explicit recovery/first-install compatibility operations.Do not use compatibility commands to bypass `skillcraft` ownership classification.## Resource- `scripts/sync_skill_repo.py`: canonical publisher and compatibility backend.- `scripts/tests/run.py`: complete backend test entry point.

Frequently asked questions