You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add skills library, install flow, and management UI (#143)
* Add skills library and management workflows
- Expose bundled skill catalog and install/import APIs
- Add skills page, create dialog, and composer shortcuts
- Wire slash commands to browse, create, install, and uninstall skills
* Switch global skills to ~/.okcode with legacy fallback
- Update skill creation and system docs to use ~/.okcode/skills
- Preserve read compatibility with existing ~/.claude/skills installs
- Add tests for skill precedence and bundled skill installation
Copy file name to clipboardExpand all lines: .plans/skills-system.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Problem
4
4
5
-
Skills (slash commands backed by markdown definitions) currently exist as an external convention: markdown files placed in `~/.claude/skills/<name>/SKILL.md` that Claude discovers and surfaces as `/slash-commands`. There is no first-class support in OK Code for:
5
+
Skills (slash commands backed by markdown definitions) currently exist as an external convention: markdown files placed in `~/.okcode/skills/<name>/SKILL.md` that Claude discovers and surfaces as `/slash-commands`, with legacy `~/.claude/skills/<name>/SKILL.md` still readable during migration. There is no first-class support in OK Code for:
6
6
7
7
1. Creating new skills (scaffolding, validation, editing)
8
8
2. Storing skills at workspace vs global scope
@@ -40,15 +40,15 @@ Body follows a loose convention:
40
40
41
41
| Scope | Path | Purpose |
42
42
|-------|------|---------|
43
-
| User/global |`~/.claude/skills/<name>/SKILL.md`| Available in all projects |
43
+
| User/global |`~/.okcode/skills/<name>/SKILL.md`| Available in all projects |
44
44
| Shared agent |`~/.agents/skills/<name>/SKILL.md`| Shared across agent tools |
Global skills can symlink to shared agent skills for deduplication.
48
48
49
49
### Current discovery
50
50
51
-
Claude Code discovers skills at startup by scanning `~/.claude/skills/`and presents them in the system prompt as available slash commands. There is no project-level discovery, no registry, no search.
51
+
OK Code should treat `~/.okcode/skills/`as the canonical global skill directory while preserving read compatibility with legacy `~/.claude/skills/` installs. There is no project-level discovery, no registry, no search.
52
52
53
53
### Current invocation
54
54
@@ -58,7 +58,7 @@ Skills are invoked via the `Skill` tool, which takes `skill: "<name>"` and optio
58
58
59
59
## Design goals
60
60
61
-
1.**Two-tier scoping**: skills live at global (`~/.claude/skills/`) or project (`.claude/skills/`) scope, with clear precedence rules.
61
+
1.**Two-tier scoping**: skills live at global (`~/.okcode/skills/`, with legacy fallback from `~/.claude/skills/`) or project (`.claude/skills/`) scope, with clear precedence rules.
62
62
2.**Scaffold-first authoring**: `okcode skill create` (or UI equivalent) generates valid skill structure with frontmatter, required sections, and optional supplementary files.
63
63
3.**Discoverability**: skills can be browsed, searched, and imported from a registry (local directory, git repo, or future remote registry).
64
64
4.**Zero-config invocation**: existing `/skill-name` slash command convention continues to work; new skills are immediately available after creation.
@@ -117,7 +117,8 @@ Skills are resolved with project scope taking precedence over global scope:
2. ~/.okcode/skills/<name>/SKILL.md (canonical global scope)
121
+
3. ~/.claude/skills/<name>/SKILL.md (legacy global fallback)
121
122
```
122
123
123
124
If the same skill name exists in both scopes, the project-scoped version wins. This allows projects to override or customize global skills.
@@ -423,7 +424,7 @@ Recommended phasing:
423
424
2. Skill versioning or dependency resolution between skills.
424
425
3. Skill permissions or access control (all installed skills are available).
425
426
4. Skill marketplace or monetization.
426
-
5. Breaking backwards compatibility with existing `~/.claude/skills/` layout.
427
+
5. Breaking backwards compatibility with existing `~/.claude/skills/` layout; legacy installs should remain readable while `.okcode` becomes the canonical write target.
0 commit comments