nandi/oripublic Fork 0
3d1f70c3b1e0d8c9a0b27adcc1bd1a9f053c050e
Commits
Clone
git clone https://git.rickub.com/nandi/ori.git
git clone ssh://git@rickub.com/nandi/ori.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

forked from bots-garden/ori

0016-publish-the-kit.yaml · 33 lines · 1.2 KBYAML Blame HistoryRaw
🛟 Updated. f5c963a k33g yesterday1# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2id: 16
3title: Publish the kit
4state: open
5author:
6 name: k33g
7 email: ph.charriere@gmail.com
8createdAt: 2026-09-18T00:00:00.000Z
9updatedAt: 2026-09-18T00:00:00.000Z
10labels: []
11body: |
12 Publish the ori kit so it can be used via `sbx create claude --kit ori` instead of requiring
13 a local path `--kit ./kits/ori`.
14
15 According to the sbx source exploration (2026-09-17, follow-up 5b in history.md), kits can be
16 distributed using:
17 - `sbx kit validate` — validate kit spec
18 - `sbx kit pack` — package the kit
19 - `sbx kit push` — push to a kit registry
20
21 Requirements:
22 - Validate `kits/ori/spec.yaml` passes `sbx kit validate`
23 - Package the kit using `sbx kit pack`
24 - Publish to a registry accessible by `sbx create --kit ori`
25 - Update documentation (quickstart.md, kits/ori/README.md, docs/*/how-to/run-in-a-sandbox.md)
26 to reflect the simplified usage
27
28 Open questions:
29 - What registry should be used for publication?
30 - Does the kit need to be namespaced (e.g., `k33g/ori` or `bots-garden/ori`)?
31 - Authentication/permissions for pushing to the registry?
32tasks: []
33comments: []