Esta página se muestra en inglés. Una traducción al español está en curso.
SkillsMay 14, 2026·2 min de lectura

skillshare — Sync Skills Across AI CLIs

Sync skills, agents, rules, and prompts across Codex, Claude Code, Cursor, and 60+ targets with a single offline-friendly CLI.

Listo para agents

Staging seguro para este activo

Este activo primero queda en staging. El prompt copiado pide inspeccionar los archivos staged antes de activar scripts, config MCP o config global.

Stage only · 17/100Política: staging
Superficie agent
Cualquier agent MCP/CLI
Tipo
CLI Tool
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando de staging seguro
npx -y tokrepo@latest install 56ec8f81-07c8-5fd1-a014-dbf7356df5b4 --target codex

Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.

Introducción

Use skillshare to keep one source of skills in sync across multiple AI CLIs and teammates without manual copying.

Sync skills, agents, rules, and prompts across Codex, Claude Code, Cursor, and 60+ targets with a single offline-friendly CLI.

Best for: teams maintaining shared skills/rules across multiple AI tools (Codex, Claude Code, Cursor) and machines

Works with: macOS/Linux/Windows, Homebrew or releases, local folders and Git repos as sources

Setup time: ~5–10 minutes (install + first init/sync)

Key facts (verified)

  • GitHub: 1,805 stars · 109 forks · pushed 2026-05-14.
  • License: MIT · owner avatar + repo URL verified via GitHub API.
  • Entrypoint (README-backed): brew install skillshare.

Main

  • Treat your skills folder as a repo: review changes, pin versions, and add CI checks before syncing to every target.
  • Use .skillignore and per-target include/exclude rules to prevent sensitive files from being copied to local agents.
  • When onboarding a team, standardize one canonical source directory and keep all targets read-only from the sync side.

README excerpt (source)

<p align="center" style="margin-bottom: 0;">
  <img src=".github/assets/logo.png" alt="skillshare" width="280">
</p>

<h1 align="center" style="margin-top: 0.5rem; margin-bottom: 0.5rem;">skillshare</h1>

<p align="center">
  <a href="https://skillshare.runkids.cc"><img src="https://img.shields.io/badge/Website-skillshare.runkids.cc-blue?logo=docusaurus" alt="Website"></a>
  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a>
  <a href="https://github.com/runkids/skillshare/releases"><img src="https://img.shields.io/github/v/release/runkids/skillshare" alt="Release"></a>
  <img src="https://img.shields.io/badge/platform-macOS%20%7C%20Linux%20%7C%20Windows-blue" alt="Platform">
  <a href="https://goreportcard.com/report/github.com/runkids/skillshare"><img src="https://goreportcard.com/badge/github.com/runkids/skillshare" alt="Go Report Card"></a>
  <a href="https://deepwiki.com/runkids/skillshare"><img src="https://deepwiki.com/badge.svg" alt="Ask DeepWiki"></a>
</p>

<p align="center">

FAQ

Q: Is it offline-friendly? A: The CLI is a single binary and can sync local sources; remote Git sources depend on your network.

Q: What should I sync first? A: Start with a small curated set of skills/rules, then expand once you have review + filtering in place.

Q: How do I avoid leaking secrets? A: Add .skillignore and avoid placing secrets in skill repos; review what each target receives.

🙏

Fuente y agradecimientos

Source: https://github.com/runkids/skillshare > License: MIT > GitHub: 1,805 stars · 109 forks · pushed 2026-05-14

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados