One complete delivery path
Git supplies content. Skiva validates fixed commits, stores immutable versions, and delivers complete snapshots through channels.
Git commit → Pipeline validation → Skill version → Release snapshot → Canary verification → Stable → Agent
A successful build does not publish content. Creating a snapshot does not change a channel. Clients following a channel discover a new version only after that channel is promoted.
Where to start
| Goal | Guide |
|---|---|
| Create a Git repository in Skiva | Hosted Git |
| Use the platform for the first time | Quickstart |
| Understand versions, snapshots, and channels | Core concepts |
| Publish, update, or roll back Skills | Releases |
| Configure scan directories and rules | Pipelines |
| Connect an Agent | Clients and Agents |
| Manage permissions and credentials | Security |
| Deploy, back up, or troubleshoot | Operations |
Supported scope
The console, static Git validation, immutable releases, Canary / Stable channels, Profile authorization, and Linux read-only FUSE mounts are implemented. Pipelines do not execute repository scripts. Native macOS / Windows mounts are not implemented.
This handbook describes the current implementation. Agent context caches and filesystem updates are separate: after files change, you may still need to reload Skills or start a new task.
Python SDK
Connect your own Agent with versioned discovery, pinned/dynamic views and Pydantic AI integration. Start with the Python SDK quickstart.