agentforge-ship

Automate end-to-end packaging and release management for AI agents.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Kingxiao/agentforge --skill agentforge-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentforge-ship
Source: https://github.com/Kingxiao/agentforge/tree/main/agentforge-ship
Command: npx skills add https://github.com/Kingxiao/agentforge --skill agentforge-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AgentForge Phase 8 addresses the gap between a built agent and a usable deliverable by orchestrating packaging, distribution, version management, and CI/CD workflows to produce production-ready artifacts.

Core Features & Use Cases

  • End-to-end packaging orchestration across multiple languages and forms (CLI, SDK, Web, API)
  • Versioning, release form selection, and automated CI/CD integration for reliable deployments
  • Use Case: teams can release new agent iterations with standardized packaging, verified builds, and traceable release notes

Quick Start

Package and release AgentForge Phase 8 by selecting a release form, applying per-language packaging recipes, and enabling CI/CD before deployment.

Frequently Asked Questions about agentforge-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate AI agent packaging and release management for CI/CD workflows?

Automate AI agent packaging by orchestrating release form selection, applying language-specific recipes, and enabling CI/CD workflows to deliver production-ready artifacts with traceable release notes.

What is release governance for AI agents and why do I need SBOM generation?

Release governance enforces versioning, SBOM generation, and cross-platform builds to ensure traceable deployments. SBOM generation tracks component dependencies, providing accountability and security for production-ready agent artifacts.

Can I use automated versioning and cross-platform builds for both CLI and SDK agent release forms?

Automated versioning and cross-platform builds support multiple release forms including CLI, SDK, Web, and API. Language-specific packaging recipes coordinate builds to ensure standardized distribution across diverse platforms.

What's the best way to coordinate per-language packaging recipes for agent distribution?

Coordinate per-language packaging recipes by selecting a release form, applying the corresponding recipe, and enabling CI/CD integration. This end-to-end orchestration ensures verified builds and standardized packaging.

Does automated release management work without manual versioning enforcement?

Automated release management enforces versioning automatically during CI/CD integration. The orchestration process natively handles version tracking and SBOM generation, eliminating the need for manual versioning enforcement.

When should I not use automated end-to-end packaging orchestration for my agents?

Avoid automated end-to-end packaging orchestration if your project requires highly customized, non-standard release forms or lacks CI/CD infrastructure, as the process enforces standardized recipes and strict release governance.