ginuim/skill-base

94 stars · Last commit 2026-06-05

Private Skill distribution platform for AI coding agents: publish, install, update, and rollback team skills across Cursor, Claude Code, Codex, and OpenClaw with a minimal server + skb CLI.

README preview

# Skill Base

**English** | [中文](docs/zh/README.md)

[![npm version](https://img.shields.io/npm/v/skill-base.svg)](https://www.npmjs.com/package/skill-base)
[![Node version](https://img.shields.io/badge/node-%3E%3D%2018.0.0-brightgreen)](https://nodejs.org/)
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

> Private distribution for Agent Skills. Publish once; install, update, and roll back across Cursor, Claude Code, Codex, OpenClaw, and similar assistants — one small server, one CLI (`skb`).

<p align="center">
  <img src="https://github.com/ginuim/skill-base/raw/main/docs/images/demo.gif" alt="Skill Base demo" />
</p>

## Why

Many teams already have dozens or hundreds of Skills, but they are not team assets yet — just Markdown scattered across chat logs, personal machines, and project folders. People download from group chats, copy a colleague's old copy, or edit their local file directly. Over time, no one can say which copy is current, who changed what, or which projects still run an old version.

Some teams move Skills into Git, which helps: you get commits and a single repo. But Git answers "where do files live?", not "how does the team use them?" It does not fix fragmented Skill paths across Cursor, Claude Code, Qoder, and other agents. The real pain is distribution, install, updates, and access:

View full repository on GitHub →