aicp-model-mgmt

Manage base model lifecycle via aicp CLI models surfaces with YAML config persistence.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill aicp-model-mgmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aicp-model-mgmt
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/aicp-model-mgmt
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill aicp-model-mgmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AICP operators need a cohesive, maintainable workflow to install, monitor, swap, and delete base models, unify lifecycle tooling, and avoid deprecated MCP commands, reducing manual overhead and misconfigurations.

Core Features & Use Cases

  • Manage base model lifecycle through the aicp --models and aicp --model-cmd surfaces (install/download, unload, delete, status, update).
  • Ensure single-active-backend behavior with proper VRAM management and catalog synchronization.
  • Pre-deployment and audit workflows for selecting and validating models, including YAML config updates and activation.

Quick Start

Install, monitor, and manage base models with the aicp CLI using the models surface to download, activate, unload, and delete models.

Frequently Asked Questions about aicp-model-mgmt

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

FAQPage Schema
How do I manage base model lifecycles in AICP using the CLI?

Manage base model lifecycles in AICP through the aicp CLI using the --models and --model-cmd surfaces to install, activate, unload, and delete models with YAML-based config persistence.

How does VRAM management work for single-active-backend deployments?

VRAM management for single-active-backend deployments enforces proper memory allocation and catalog synchronization when swapping base models, ensuring only one active backend consumes GPU resources at any given time.

Can I perform catalog audits and pre-deployment model selection with YAML config?

Yes, pre-deployment and audit workflows support selecting and validating models through YAML config updates and activation, allowing operators to verify catalog entries before deployment.

What safety rules apply to destructive operations like deleting base models?

Safety rules around destructive operations enforce validation checks before deleting or unloading base models, preventing accidental data loss and ensuring proper catalog synchronization during removal.

Why should I use the aicp CLI instead of MCP tools for model management?

The aicp CLI replaces deprecated MCP commands with unified --models and --model-cmd surfaces, providing a cohesive workflow that reduces manual overhead and avoids misconfigurations from fragmented tooling.