cooagents-upgrade

Automate cooagents service upgrades with health validation and rollback guidance.

5|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vaxtomis/cooagents --skill cooagents-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cooagents-upgrade
Source: https://github.com/vaxtomis/cooagents/tree/main/skills/cooagents-upgrade
Command: npx skills add https://github.com/vaxtomis/cooagents --skill cooagents-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill guides administrators to upgrade the cooagents service by pulling the latest code, updating dependencies, rebuilding the dashboard, and restarting the service with health verification to ensure minimal downtime.

Core Features & Use Cases

  • End-to-end upgrade workflow: checks service health, pulls latest code, runs bootstrap to install deps and rebuild frontend, and restarts the server with validation.
  • Operational guardrails: warns about running tasks during upgrade, backs up state, and provides rollback guidance via troubleshooting references.
  • Use Case: An admin runs the upgrade to refresh a production deployment with minimal disruption and clear rollback options.

Quick Start

Run the cooagents-upgrade command to refresh the service on the local host.

Frequently Asked Questions about cooagents-upgrade

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

FAQPage Schema
How do I upgrade a production service with minimal downtime?

Upgrading a production service with minimal downtime involves pulling the latest code, updating dependencies, rebuilding the dashboard, and restarting the server. The automated workflow includes health validation and operational guardrails like state backups to ensure a safe refresh.

What is the safest way to pull latest code and restart a local server?

The safest way to pull latest code and restart a local server is using an automated upgrade workflow that checks service health first, runs bootstrap to install dependencies and rebuild the frontend, then restarts with post-restart validation to ensure the service is properly refreshed.

Do I need an API token and active health endpoint to run a service upgrade?

Yes, you need an active service health endpoint at http://127.0.0.1:8321/health and an AGENT_API_TOKEN before running the service upgrade. These prerequisites ensure the automated upgrade process can validate the deployment and manage the restart safely.

Can I rebuild the frontend dashboard without disrupting running tasks?

Rebuilding the frontend dashboard during an upgrade warns about running tasks to prevent disruption. The upgrade workflow includes operational guardrails that check for active tasks, back up state, and provide rollback guidance via troubleshooting references if conflicts occur.

What should I do if my service upgrade fails the health validation check?

If your service upgrade fails the health validation check, consult the troubleshooting references provided by the upgrade workflow. The system offers conflict guidance and rollback instructions to help administrators restore the production deployment to its previous stable state.