overskill 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +32 -239
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,261 +1,54 @@
1
1
  # Overskill
2
2
 
3
- A CLI for managing skills across repositories.
3
+ [Overskill](https://overskill.jacobchaselubitz.com/)
4
4
 
5
- ## Why Overskill over AI Agent Plugins?
5
+ Overskill is a skills manager for AI coding agents. It gives you a single place to write, version, and share the instruction files that guide tools like Claude Code, Cursor, Codex, and Windsurf — then apply them to any repository with one command.
6
6
 
7
- Tools like Claude Code offer built-in plugin systems for distributing skills. Overskill takes a different approach — skills live in your repo as plain files — and this comes with meaningful advantages:
7
+ **Why Overskill?**
8
8
 
9
- - **Agent-agnostic**: Overskill skills work with Claude Code, Cursor, Codex, Windsurf, and any agent that can read markdown. Plugins lock you into a single tool.
10
- - **Transparent and auditable**: Skills are visible files in your project. You can read, diff, and review them like any other code. Plugin skills are buried in global cache directories.
11
- - **Version-locked per repo**: `.skills.lock` pins exact versions and hashes to each commit, giving you reproducible builds. Plugins are installed globally or per-user with no per-repo lockfile.
12
- - **Team-friendly**: `skill sync` works like `npm install` clone the repo, run one command, and everyone has the same skills at the same versions. Plugins require each developer to install them separately.
13
- - **Full control over activation**: You decide how and when skills are loaded via `CLAUDE.md`, `.cursor/rules`, or `AGENTS.md`. Plugin activation is controlled by the agent vendor.
14
- - **Works offline**: Once synced, skills are local files with no runtime dependency on external services.
15
- - **No vendor dependency**: Your skills aren't tied to a plugin API that could change or be deprecated. They're markdown files — the most durable format there is.
9
+ - **Write once, use everywhere.** Create a skill once and add it to as many repositories as you need. When you improve it, update every project in seconds.
10
+ - **Agent-agnostic.** Skills are plain markdown files. They work with any agent that can read markdown no plugin API, no vendor lock-in.
11
+ - **Version-locked per repo.** `.skills.lock` pins exact versions and content hashes, so every collaborator and CI run gets the same skills.
12
+ - **Transparent and auditable.** Skills live in your project as visible files you can read, diff, and review like any other code.
13
+ - **Works offline.** Once synced, skills are local files with no runtime dependency on external services.
16
14
 
17
- ## Requirements
15
+ ## How it works
18
16
 
19
- - Node.js >= 18
17
+ Overskill maintains a **global registry** on your machine (in `~/.overskill/registry/`). When you create or import a skill, it's saved there. When you run `skill add` and `skill sync` in a repository, Overskill copies the right version into the project's `.skills/` directory and generates an index file so AI agents discover them automatically.
20
18
 
21
- ## Setup
19
+ ## Documentation
22
20
 
23
- ### CLI
21
+ 1. **[Getting Started](./docs/getting-started.md)** — Install Overskill and add it to your first project
22
+ 2. **[Configuration](./docs/configuration.md)** — View and change global settings like your default editor
23
+ 3. **[Managing Skills in a Repository](./docs/managing-skills.md)** — Initialize a repo, import existing skills, create new ones, add and remove skills
24
+ 4. **[Syncing and Updating](./docs/syncing-and-updating.md)** — Check installed versions, sync skills, and update to the latest
25
+ 5. **[Editing Skills](./docs/editing-skills.md)** — Edit a skill, publish a new version, and apply changes to a project
26
+ 6. **[Command Reference](./docs/command-reference.md)** — Full list of commands and flags
24
27
 
25
- 1. Install dependencies and build:
28
+ ## Quick start
26
29
 
27
30
  ```bash
28
- cd cli
29
- npm install
30
- npm run build
31
- ```
32
-
33
- 2. Run the CLI:
34
-
35
-
36
- ```bash
37
- node dist/index.js --help
38
- ```
39
-
40
- Optional: link the CLI for a global `skill` command:
41
-
42
- ```bash
43
- npm link
44
- skill --help
45
- ```
46
-
47
- ## CLI Quick Start
48
-
49
- ### Local-Only Workflow (No Cloud)
50
-
51
- 1. Initialize a local-only project:
31
+ # Install
32
+ npm install -g overskill
52
33
 
53
- ```bash
34
+ # Or install with Homebrew
35
+ brew tap jchaselubitz/tap
36
+ brew install overskill
37
+
38
+ # Initialize in a project
39
+ cd your-project
54
40
  skill init
55
- ```
56
-
57
- 2. Create a new skill:
58
-
59
- ```bash
60
- skill new my-skill
61
- ```
62
-
63
- 3. Add skills from local cache:
64
-
65
- ```bash
66
- skill add my-skill
67
- ```
68
41
 
69
- 4. Import skills from other tools (Claude, Cursor, Codex):
70
-
71
- ```bash
42
+ # Import skills you've already written for Claude, Cursor, or Codex
72
43
  skill import
73
- ```
74
-
75
- ### Cloud Workflow (Coming Soon)
76
-
77
- 1. Configure the API URL:
78
-
79
- ```bash
80
- skill config api_url https://your-domain.example/api
81
- ```
82
-
83
- 2. Initialize with cloud registry:
84
-
85
- ```bash
86
- skill init --cloud --registry your-registry
87
- ```
88
44
 
89
- 3. Log in:
90
-
91
- ```bash
92
- skill login
93
- ```
94
-
95
- 4. Add and sync skills:
45
+ # Or create a new skill from scratch
46
+ skill new my-skill
96
47
 
97
- ```bash
48
+ # Add skills to the project
98
49
  skill add my-skill
99
- skill sync
100
- ```
101
-
102
- ## Commands
103
-
104
- ### Configuration
105
-
106
- - `skill config <key> [value]` - Get or set config (`api_url`, `editor`, `install_path`)
107
- - `skill config show` - Show all config
108
- - `skill config logout` - Clear authentication tokens
109
-
110
- ### Project Setup
111
-
112
- - `skill init [options]` - Initialize `.skills.yaml` in current directory. Also configures AI agent integration files (see [AI Agent Integration](#ai-agent-integration)).
113
- - `--cloud` - Include a cloud registry source
114
- - `-u, --url <url>` - API URL for cloud registry (requires `--cloud`)
115
- - `-r, --registry <slug>` - Cloud registry slug (requires `--cloud`)
116
- - `-p, --path <path>` - Custom install path (default: `.skills`)
117
-
118
- ### Authentication
119
-
120
- - `skill login [--manual]` - Authenticate with cloud registry (browser flow or manual code entry)
121
-
122
- ### Skill Creation & Management
123
-
124
- - `skill new <slug> [options]` - Create a new skill in local registry
125
- - `-n, --name <name>` - Display name
126
- - `-d, --description <desc>` - Description
127
- - `-t, --tags <tags>` - Comma-separated tags
128
- - `-c, --compat <compat>` - Compatibility list (e.g., `claude,gpt4`)
129
- - `-v, --version <version>` - Initial version (default: `1.0.0`)
130
- - `-m, --metadata <key=value>` - Custom frontmatter metadata (repeatable)
131
- - `--content <file>` - Read content from file instead of editor
132
- - `--blank` - Open editor with blank content (frontmatter only)
133
- - `--no-editor` - Skip editor, create with template
134
- - `--no-add` - Skip adding to current project
135
- - `--no-sync` - Skip automatic sync
136
-
137
- - `skill publish <slug> [options]` - Publish a new version of existing skill
138
- - `-v, --version <version>` - Explicit version number
139
- - `--patch` - Bump patch version (1.0.0 → 1.0.1)
140
- - `--minor` - Bump minor version (1.0.0 → 1.1.0)
141
- - `--major` - Bump major version (1.0.0 → 2.0.0)
142
- - `-m, --message <message>` - Changelog message
143
- - `--content <file>` - Read content from file
144
- - `--no-editor` - Skip editor, use current content
145
-
146
- - `skill import [path] [options]` - Import skills from other AI tools
147
- - `[path]` - Custom path to scan (optional)
148
- - `-f, --force` - Overwrite existing skills
149
- - `--add` - Add imported skills to `.skills.yaml`
150
- - `--sync` - Run sync after importing (requires `--add`)
151
- - `--dry-run` - Preview without making changes
152
- - `-y, --yes` - Import all without prompting
153
-
154
- ### Project Operations
155
-
156
- - `skill add [slugs...] [options]` - Add skills to project
157
- - Interactive mode if no slugs provided (checkbox selection)
158
- - `-v, --version <constraint>` - Version constraint (e.g., `>=1.0.0`, `^2.0.0`)
159
- - `--no-sync` - Skip automatic sync after adding
160
-
161
- - `skill remove <slugs...>` - Remove skills from project
162
-
163
- - `skill sync [options]` - Sync configured skills to install directory. Also updates AI agent integration files (see [AI Agent Integration](#ai-agent-integration)).
164
- - `-f, --force` - Force re-install even if unchanged
165
-
166
- - `skill update [slug] [--check]` - Update to latest versions
167
-
168
- ### Discovery & Information
169
-
170
- - `skill list [options]` - List available skills
171
- - `--installed` - Show only installed skills in current project
172
- - `--local` - Show only local registry skills
173
-
174
- - `skill search <query> [options]` - Search for skills
175
- - `-t, --tags <tags>` - Filter by tags
176
- - `-c, --compat <compat>` - Filter by compatibility
177
-
178
- - `skill info <slug> [options]` - Show detailed skill information
179
- - `-v, --version <version>` - Show info for specific version
180
-
181
- ### Editing & Validation
182
-
183
- - `skill edit <slug>` - Edit a local skill using configured editor
184
-
185
- - `skill diff <slug>` - Show differences between local and registry versions
186
-
187
- - `skill validate [slug]` - Validate skill files (validates all if no slug provided)
188
-
189
- ## Project Files
190
-
191
- - `.skills.yaml` - Project config (sources, install path, skills list)
192
- - `.skills.lock` - Version lock file (like package-lock.json)
193
- - `.skills/` - Installed skills directory (default, configurable)
194
- - `SKILLS_INDEX.md` - Generated index of installed skills for AI discovery
195
-
196
- ## AI Agent Integration
197
-
198
- When you run `skill init` or `skill sync`, Overskill automatically configures your project so that AI coding agents discover and use your installed skills. It updates the following files:
199
-
200
- - **`CLAUDE.md`** — Claude Code reads this file automatically. Overskill adds a managed section that points Claude to `SKILLS_INDEX.md`.
201
- - **`AGENTS.md`** — Read by Codex and other agents. Same managed section as `CLAUDE.md`.
202
- - **`.cursor/rules/overskill.mdc`** — Cursor rule with `alwaysApply: true` that tells Cursor to read the skills index.
203
-
204
- The `CLAUDE.md` and `AGENTS.md` sections are wrapped in `<!-- overskill-start -->` / `<!-- overskill-end -->` comment markers so they can be updated idempotently without affecting the rest of the file. The Cursor rule is a standalone file that gets overwritten on each sync.
205
-
206
-
207
- ## Local Registry
208
-
209
- Skills are cached locally in `~/.local/share/overskill/cache/` (Linux/macOS) or equivalent on Windows. The local registry supports:
210
-
211
- - Creating skills with `skill new`
212
- - Publishing versions with `skill publish`
213
- - Importing from other tools with `skill import`
214
- - Version resolution with semver constraints
215
-
216
- # Coming for Cloud
217
-
218
- ### Commands for Cloud
219
-
220
- - `skill login [--manual]` - Authenticate with cloud registry (browser flow or manual code entry)
221
-
222
- - `skill config api_url <url>` - Set the API URL for the cloud registry
223
-
224
- - `skill config registry <slug>` - Set the registry slug for the cloud registry
225
-
226
- - `skill config install_path <path>` - Set the install path for the cloud registry
227
-
228
- ### Publishing & Sharing
229
-
230
- - `skill push [slug] [--create ...]` - Publish changes to cloud registry
231
-
232
- - `skill bundle [slugs...] [options]` - Bundle skills into single markdown file
233
- - `[slugs...]` - Specific skills to bundle (bundles all if omitted)
234
- - `-o, --output <path>` - Output file path (default: `skills-bundle.md`)
235
-
236
- - `skill delete <skill>` - Delete skill from registry
237
- - Local: `skill delete <slug>`
238
- - Remote: `skill delete <registry>/<slug>`
239
-
240
- ### Registry Management
241
-
242
- - `skill registry <subcommand>` - Manage registries and invitations
243
- - See `skill registry --help` for subcommands
244
-
245
-
246
-
247
- ## Development
248
-
249
- - CLI dev mode:
250
-
251
- ```bash
252
- cd cli
253
- npm run dev
254
50
  ```
255
51
 
256
- - Typecheck:
52
+ ## License
257
53
 
258
- ```bash
259
- cd cli
260
- npm run typecheck
261
- ```
54
+ MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "overskill",
3
- "version": "1.0.0",
3
+ "version": "1.0.2",
4
4
  "description": "Overskill CLI - manage skills across repositories",
5
5
  "main": "./dist/index.js",
6
6
  "bin": {