Agent Package Spec — Testing skill for Claude Code

Agent Package Specification

This repository proposes a standard way to package and distribute **agent skills and agent plugins as OCI artifacts**. The aim is to give publishers, registries, marketplaces, and agent hosts a common distribution format that works with existing OCI tooling for versioning, signing, verification, and promotion.

The [draft specification](spec/agent-package.md) preserves the native Skill or Plugin files and adds an OCI manifest, package metadata, and a verifiable file inventory around them. A Skill or Plugin package is an OCI artifact; it does not need to be a container image that runs an application.

**This is a proposal for community review, not an adopted standard.** Feedback and implementation experience are welcome. Media types, namespace ownership, and other design details remain provisional.


The payload remains governed by its native specification, such as the [Agent Skills specification](https://agentskills.io/specification) or the [Agent Plugins specification](https://agent-plugins.org/specification). The OCI manifest and package config add typed discovery, inventory, verification, and distribution metadata around those unchanged files.

Why package Skills and Plugins?

Build one verifiable release artifact

A Skill or Plugin is normally authored as a directory containing instructions, metadata, scripts, references, assets, hooks, or other related files. Source control is the right place to develop those files, but a repository branch or directory can change. Publishers and consumers need to identify exactly which files belong to a particular release.

An explicit build step creates one immutable, versioned distribution unit. A marketplace, scanner, installer, and user can then operate on the same output. The artifact can be validated, signed, approved