Skip to content

AI-Neighbors/skillsOS

Repository files navigation

skillsOS

English | Русский | Español | 中文

Public directory of reusable operator skills and playbooks.

skillsOS hero

One repo. One public directory. Reusable packs across isolated runtimes.
Manual copy-paste breaks fast once you run Claude Code, Codex, OpenCode, OpenClaw, and Pi across several machines.

Claude Code Codex OpenCode Node.js License MIT
EN RU ES CN


skillsOS sync hero skillsOS sync loop preview

One public pack · one sync CLI · one contribution surface

Star Repository Fork Repository Send PR

What Is This

skillsOS is a public-safe directory of reusable operator skills and playbooks built from real work.

The current public-facing direction is the directory surface itself: clear categories and shipped entries.

It exists to solve one operator problem:

keeping reusable workflow assets in sync across several machines and isolated runtimes without endless manual copy-paste.

This repo is intentionally narrow and stays focused on one public pack, one sync CLI, and one clear contribution surface.

It is not trying to be a giant framework or a universal secret playbook.

It is a public working slice built around:

  • one runnable sync CLI
  • one public pack
  • one clear contribution surface

Who This Helps

  • people who need reusable workflow assets across several machines
  • operators who want one clear public pack instead of scattered notes
  • contributors who need a readable install-and-PR path

Why This Exists

When the same pack needs to live across vps1, vps2, vps3, local machines, and isolated runtimes, drift starts fast:

  • one runtime gets the new pack
  • another keeps the old copy
  • one host has a local tweak nobody remembers
  • examples leak private hostnames unless you clean them up on purpose

skillsOS exists to keep that boring operator problem explicit and reproducible.

It is not auth, SSO, or product-platform work.

Quick Start

git clone https://github.com/AI-Neighbors/skillsOS.git
cd skillsOS
npm install
npm run sync:plan -- \
  --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json \
  --all-hosts
npm run sync:apply -- \
  --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json \
  --all-hosts
npm run sync:verify -- \
  --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json \
  --all-hosts

Usage

Need Command
See what will change npm run sync:plan -- --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json --all-hosts
Install the public pack npm run sync:apply -- --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json --all-hosts
Verify targets after sync npm run sync:verify -- --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.example.json --all-hosts
Preview remote alias fan-out npm run sync:plan -- --manifest skillsos-ops-multi-machine-sync/references/skillsos-sync.remote-aliases.example.json --all-hosts

How It Works

one repo
   |
   +-- one public pack
   |      |
   |      +-- README
   |      +-- references
   |      +-- example manifests
   |
   +-- one sync CLI
          |
          +-- local runtimes
          |     +-- ~/.codex/packs-public
          |     +-- ~/.claude/packs-public
          |     +-- ~/.agents/packs-public
          |
          +-- remote aliases
                +-- vps1
                +-- vps2
                +-- vps3

The model is simple:

  • keep the pack as the source
  • keep installation repeatable
  • keep public examples anonymous and safe

Project Structure

skillsOS/
├── README.md
├── README.ru.md
├── README.es.md
├── README.cn.md
├── package.json
├── bin/
│   └── skillsos-sync.mjs
├── docs/
│   └── media/
└── skillsos-ops-multi-machine-sync/
    ├── README.md
    └── references/
        ├── architecture.md
        ├── roadmap.md
        ├── ssh-config.example
        ├── skillsos-sync.example.json
        └── skillsos-sync.remote-aliases.example.json

Current Pack

Browse the Directory

This public directory currently has one shipped entry and one first category:

First Entry

If you are here to understand the current public slice, start with:

That pack is the current bounded delivery base for the public directory rail.

Disclaimer

This repo shows a current working pattern, not the final answer.

If you have a cleaner setup, a stronger install model, or a better structure:

  • star it
  • fork it
  • open a PR
  • show a better way

Star History

Star History Chart

License

This project is released under the MIT License.

Let's Connect

X LinkedIn Website Email

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors