nandi/oripublic Fork 0
main
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

🛟 Updated. f5c963a · on main · k33g · 18h ago
0016-publish-the-kit.yaml · 33 lines · 1.2 KBYAML Blame HistoryRaw
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
id: 16
title: Publish the kit
state: open
author:
  name: k33g
  email: ph.charriere@gmail.com
createdAt: 2026-09-18T00:00:00.000Z
updatedAt: 2026-09-18T00:00:00.000Z
labels: []
body: |
  Publish the ori kit so it can be used via `sbx create claude --kit ori` instead of requiring
  a local path `--kit ./kits/ori`.

  According to the sbx source exploration (2026-09-17, follow-up 5b in history.md), kits can be
  distributed using:
  - `sbx kit validate` — validate kit spec
  - `sbx kit pack` — package the kit
  - `sbx kit push` — push to a kit registry

  Requirements:
  - Validate `kits/ori/spec.yaml` passes `sbx kit validate`
  - Package the kit using `sbx kit pack`
  - Publish to a registry accessible by `sbx create --kit ori`
  - Update documentation (quickstart.md, kits/ori/README.md, docs/*/how-to/run-in-a-sandbox.md)
    to reflect the simplified usage

  Open questions:
  - What registry should be used for publication?
  - Does the kit need to be namespaced (e.g., `k33g/ori` or `bots-garden/ori`)?
  - Authentication/permissions for pushing to the registry?
tasks: []
comments: []