kinic-skill-registry

Files (1)

• SKILL.md

SKILL.md (first lines)

# Kinic Skill Registry

Use this skill when the user wants to:

- manage skill packages stored under `/Skills`
- use `kinic-vfs-cli skill ...` commands
- find or inspect skills by task context
- record run evidence, promote, deprecate, or rollback snapshots
- create a lockfile-only install record

Do not use this skill for:

- ordinary knowledge query, ingestion, or lint work
- browser UI implementation
- local agent runtime placement
- permission enforcement beyond database roles

Core rules:

- Treat [`../../docs/SKILL_REGISTRY.md`](../../docs/SKILL_REGISTRY.md) as the source of truth.
- Keep `kinic-vfs-cli` as the only public binary; do not introduce `skill-cli` or `wiki-cli`.
- Use `kinic-vfs-cli skill ...` for package lifecycle commands.
- Authenticated CLI commands default to Internet Identity through `icp identity default`; use `--allow-non-ii-identity` only for explicit operator workflows that require PEM or another non-II identity.
- `skill upsert` and `skill import github` write package files through the `write_nodes` batch API; use generic `write-nodes` only for non-package VFS batch writes.
- Use `database link` or `--database-id` for DB selection; access control remains database-level.
- Treat packages as normal VFS nodes, not as canister schema.
- Keep `skill install` lockfile-only; do not copy package files into an agent runtime.
- Prefer `promoted` or `reviewed` skills and ignore `deprecated` skills unless auditing.
- Record usage evidence after a skill materially affects a task outcome.
- `skill upsert` and `skill rollback` snapshot the replaced current version before changing it.

Before substantive registry work:

1. Read `docs/SKILL_REGISTRY.md`.
2. Confirm the target database is selected.
3. Use the smallest relevant command set:
   - package write: `skill upsert` or `skill import github`
   - discovery: `skill find`
   - inspection: `skill inspect`
   - evidence: `skill record-run`
   - lifecycle: `skill set-status`, `skill rollback`, `skill history`
   - downstream pinning: `skill install --lockfile`

From ICME-Lab/kinic-wiki, MIT.

More from ICME-Lab/kinic-wiki