Main
- Treat your skills folder as a repo: review changes, pin versions, and add CI checks before syncing to every target.
- Use
.skillignoreand 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.