skr

The skr CLI is a robust utility designed to streamline the lifecycle of Agent Skills, acting as a bridge between standard Git repositories and OCI-compliant registry infrastructure. It provides a standardized framework for developers to package, distribute, and consume AI agent capabilities. By leveraging OCI (Open Container Initiative) artifacts, skr ensures that skills remain versioned, immutable, and performant, allowing developers to treat complex agentic workflows with the same reliability as containerized software.

Developers, AI engineers, and DevOps practitioners can use skr to maintain professional-grade agent ecosystems. It effectively solves the challenge of distributing modular agent logic across different environments, from local development to CI/CD pipelines in production. Whether building a single skill for a personal project or managing a complex monorepo of agentic tools, skr provides the necessary orchestration to ensure consistent behavior across various registry providers like GitHub Packages or Docker Hub.

• Build local skill directories into portable, OCI-compliant artifacts using simple command-line triggers.

• Install skills directly from diverse sources including Git repositories, local file paths, or remote OCI registries using a unified URI syntax.

• Batch publish capabilities enable automated deployment of multiple skills simultaneously, ideal for large-scale monorepo architectures.

• Manage local artifact stores, allowing for efficient inspection, listing, and pruning of installed skill dependencies.

• Registry authentication management through native login/logout commands ensures secure access to private OCI repositories.

• Native support for CI/CD integration, specifically with GitHub Actions, allowing for automated validation and deployment cycles.

• Input: Source paths or git URLs containing an Agent Skill structure and .skr.yaml configuration.

• Output: Validated OCI artifacts pushed to a registry or installed locally in the user workspace.

• Ensure a valid .skr.yaml file exists in the root directory to define the skill context and dependency graph.

• Use the validate command to check skill structure and syntax before pushing to production environments.

• Registry authentication (skr registry login) is mandatory before attempting to push or pull private artifacts.

• Maintain reproducibility by utilizing the generated .skr.lock file, which stores immutable tag hashes for all dependencies.