agent-deploy

To publish a generated agent to a private GitHub repository, the skill automates remote repository creation via the gh CLI and enforces required files like CLAUDE.md and README.md. It returns a ready-to-use repository URL while coordinating preflight checks and deployment QC.

Deploying an agent as a private repo requires specific files including CLAUDE.md and README.md. The process enforces these readiness checks alongside .cursor/skills validation to ensure your domain-specific agent passes preflight QC before remote GitHub publication.

Yes, you can use the gh CLI to automate private repo creation for AI agents. This skill leverages the gh CLI to create the remote repository directly, eliminating manual setup and streamlining the deployment workflow for generated domain-specific agents.

Multi-platform synchronization for deployed agents works by aligning master artifacts across CLAUDE, AGENTS, and related surfaces. The skill uses the update_agent_master script to enforce consistency and coordinate synchronization throughout the private repository deployment workflow.

The best way to automate the GitHub deployment workflow for a domain-specific agent is to use a skill that handles preflight checks, QC, and gh CLI repository creation. This ensures required files are validated and multi-platform synchronization is executed automatically.

Limitations when publishing agents as private GitHub repos include strict dependencies on required files like CLAUDE.md and README.md. Failing these preflight checks or lacking proper gh CLI authentication will halt the deployment workflow and prevent repository creation.