Skills Dev - Workspace de Desenvolvimento de Skills Claude Code
mtschoen/skills-dev
Workspace centralizado para desenvolver e distribuir skills Claude Code
Ver no GitHubRepositório umbrella que centraliza o desenvolvimento de múltiplos skills para Claude Code como submodelos Git. Fornece ferramentas de instalação e sincronização para gerenciar skills em múltiplos ambientes (Claude Code, Codex, Antigravity) de forma automatizada e sem duplicação.
Instalação
npx convez-ai mtschoen/skills-dev1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Desenvolvimento coordenado de múltiplos skills com submodelos Git
- Instalação automatizada de skills em ~/.agents/skills, ~/.claude/skills e ~/.gemini/skills
- Sincronização recursiva de submodelos entre máquinas e ambientes
Veredito

Infraestrutura robusta para desenvolvedores que mantêm múltiplos skills Claude Code. Requer familiaridade com Git submodelos e bash/batch, mas automatiza completamente a distribuição entre agentes diferentes.
README
A tradução para o português deste README ainda está na fila.
skills-dev
A workspace for developing Claude Code skills. Each top-level directory is a git submodule pointing at that skill's own repository; this repo is the umbrella that ties them together and provides install + sync tooling.
Cloning
The skills live in submodules, so a plain git clone will leave you with empty directories. Use one of:
# clone with submodules in one step
git clone --recursive <url>
# or, if you've already cloned without --recursive:
git submodule update --init --recursive
After cloning, opt this clone into recursive submodule updates so a later git pull keeps submodule checkouts in lockstep with the pointers the umbrella records — otherwise the umbrella drifts into a "submodule behind recorded pointer" dirty state (M <submodule> (new commits)):
git config submodule.recurse true
This lives in .git/config and cannot be committed, so run it once per clone — including on every machine you work from. It does not cover git clone itself (hence --recurse-submodules above). Trade-off: git pull then checks submodules out at the recorded commit (detached HEAD); scripts/pull-all.sh re-attaches them to main.
Installing skills
install-skills.sh (bash) and install-skills.bat (Windows) copy each skill into agent skill directories. The canonical source of truth is ~/.agents/skills/, which Codex (docs) and opencode (docs) both read natively as a global skills path. Two harnesses can't read it and so are kept as mirrors:
- Claude Code is hardcoded to
~/.claude/skills/with no setting to redirect it (anthropics/claude-code#22902, #33957). - Antigravity loads global skills from
~/.gemini/skills/; its.agents/skillsis workspace-only.
So the default install writes to all three — ~/.agents/skills/ plus mirrors at ~/.claude/skills/ and ~/.gemini/skills/ — rather than relying on symlinks. Pass agent flags to narrow the targets.
./install-skills.sh # default: ~/.agents/skills + ~/.claude/skills + ~/.gemini/skills
./install-skills.sh -y # overwrite without prompting
./install-skills.sh -n # dry run; show what would change
./install-skills.sh --agents # only the canonical ~/.agents/skills
./install-skills.sh --claude smoke-test pushback # limit destinations and skills
Supported destination flags:
| Flag | Destination |
|---|---|
--agents | ~/.agents/skills (canonical; read natively by Codex and opencode) |
--claude | ~/.claude/skills (Claude Code's mirror) |
--gemini | ~/.gemini/skills (Antigravity's global skills dir) |
--all | all of the above |
Each skill repo has SKILL.md at its root. The installer ships only git-tracked files, filtered to a top-level allowlist: SKILL.md + scripts/ + references/ + assets/, plus any extra top-level entries a skill declares in an optional .skillpack manifest at its repo root. Dev-only content (evals/, tests/, workspace/, README.md, LICENSE, etc.) is excluded by omission, and generated junk can never leak because untracked files are never shipped.
Working across all submodules
scripts/push-all.{sh,bat} and scripts/pull-all.{sh,bat} iterate every active submodule plus the umbrella repo. push-all pushes to both origin (Gitea) and github (GitHub) by default; pull-all fetches + fast-forwards from origin only. Either accepts --remote <name> to add another remote where it exists. Each push is pre-flighted (fetch + classify local vs remote as up-to-date / fast-forward / behind / diverged), and non-fast-forward states are reported and skipped. Errors print inline and don't halt the run, but the script exits non-zero with a summary.
./scripts/pull-all.sh
./scripts/push-all.sh
./scripts/pull-all.sh --remote github
./scripts/push-all.sh --remote github
Layout
skills-dev/
├── <skill-name>/ # submodule -> skills-<skill-name>.git
│ ├── SKILL.md # the skill itself
│ ├── evals/ # eval harness (dev-only, not installed)
│ └── ...
├── install-skills.sh # install -> ~/.agents/skills/ (+ Claude & Antigravity mirrors)
├── install-skills.bat
└── scripts/
├── push-all.sh
└── pull-all.sh
Submodule URLs in .gitmodules are relative (../skills-<name>.git), so the same .gitmodules works whether you cloned from Gitea or GitHub.
License
MIT — see LICENSE.