Publish a Context Pack

Publishing makes a context pack available through the registry and CLI.

Publish lifecycle

Draft → In Review → Approved → Published

Step 1: Save draft

In the context pack editor:

1. Add or edit files.
2. Save changes.
3. Confirm the status remains Draft.

Step 2: Submit for review

Use review before publishing organization-level guidance.

Reviewers should check:

• Is the domain vocabulary correct?
• Are business rules clear?
• Are instructions specific enough?
• Are there conflicting rules?
• Are file paths safe for CLI output?
• Does SKILL.md include useful frontmatter?

Step 3: Approve

Approve the pack once the content is stable enough for developers to consume.

Step 4: Publish

Publishing should:

• Persist latest files
• Set status to Published
• Set publish visibility
• Generate a CLI payload
• Expose install command

Example:

ai-skill install rb-testcontext

Published visibility

Recommended visibility types:

• Public: visible in public registry.
• Workspace: visible to workspace members.
• Private: only owner or selected users.
• Project: scoped to project usage.

Published output

The registry response should contain:

• name
• title
• description
• version
• registryKey
• installName
• files
• generated or authored SKILL.md

Important rule

Developers should install published context, not unreviewed draft context.