amcos-plugin-management

Orchestrate per-team Claude Code plugin installation, configuration, and validation.

1|Updated Feb 27, 2026

Search Tags:#validation #governance #claude-code #plugin-management #agent-lifecycle #amcos

Ready to run

npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-plugin-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amcos-plugin-management
Source: https://github.com/Emasoft/ai-maestro-chief-of-staff/tree/main/skills/amcos-plugin-management
Command: npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-plugin-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Amcos-plugin-management centralizes the installation, configuration, validation, and lifecycle management of Claude Code plugins for per-team Chief of Staff (COS) instances. It enables governance workflows, dual-manager approvals, and coordinated plugin operations across AMCOS, EOA (Orchestrator), EAA (Architect), and EIA (Integrator), ensuring team-specific plugin readiness and reliable recovery from failures.

Core Features & Use Cases

Lifecycle orchestration: install, configure, validate, enable/disable plugins for a team's COS.
Governance enforcement: dual-manager approvals before critical changes (spawn/terminate/replace).
Cross-role coordination: AMP-based messaging among AMCOS, EOA, EAA, and EIA to notify and coordinate operations.
Reliability and recovery: failure detection, classification, and recovery strategies; batch operations and rollback support.

Quick Start

Trigger a team-scoped plugin install, validation, or configuration and follow the governance workflow to complete the operation.

Frequently Asked Questions about amcos-plugin-management

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

FAQPage Schema

How do I manage Claude Code plugin installations for multiple teams?▼

You can manage Claude Code plugin installations by orchestrating per-team installation, configuration, and validation through AMCOS workflows. This coordinates plugin readiness across team Chief of Staff instances reliably.

What's the best way to enforce approval workflows before modifying Claude Code plugins?▼

Enforce plugin governance by requiring dual-manager approvals before critical changes like spawning, terminating, or replacing plugins. This ensures safe, auditable deployments managed by AMCOS.

How does cross-role coordination work for Claude Code plugin lifecycle management?▼

Cross-role coordination uses AMP-based messaging among AMCOS, EOA, EAA, and EIA agents to notify and coordinate plugin operations. This keeps all team roles synchronized during lifecycle changes.

Do I need Claude Code CLI access to validate team plugin configurations?▼

Yes, Claude Code CLI access is a prerequisite for plugin validation. You also need correct plugin manifests and robust restart procedures to ensure safe, auditable deployments after configuration changes.

Can I recover from failed Claude Code plugin deployments using batch operations?▼

Yes, plugin management supports failure detection, classification, and recovery strategies including batch operations and rollback support. This ensures reliable recovery from failed plugin deployments.