admin-devops

Manage multi-provider server inventory with unified device profiles.

1|Updated Dec 19, 2025

Search Tags:#automation #devops #cloud #SSH #inventory #provisioning

Ready to run

npx skills add https://github.com/evolv3-ai/vibe-skills --skill admin-devops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: admin-devops
Source: https://github.com/evolv3-ai/vibe-skills/tree/main/skills/admin-devops
Command: npx skills add https://github.com/evolv3-ai/vibe-skills --skill admin-devops

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Inventory-driven DevOps for multi-provider infrastructures using device profiles as the single source of truth.

Core Features & Use Cases

Server inventory in profile.servers with deployment references via profile.deployments.
Provisioning workflows across admin-infra-* providers and app-* skills.
SSH access to managed servers and integrated deployment workflows.

Quick Start

Load the profile, list servers, and navigate to provisioning workflows via routed skills.

Frequently Asked Questions about admin-devops

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

FAQPage Schema

How do I manage servers across multiple cloud providers in a single inventory?▼

Multi-provider server inventory uses unified device profiles as the single source of truth. Load your profile with servers listed in profile.servers, then filter and access them through a centralized interface that routes to each provider's infrastructure.

Can I automate provisioning workflows across different cloud providers?▼

Provisioning automation across multiple providers works through profile-driven routing. Define servers in your device profile using PROVIDER_* keys, then execute provisioning workflows via admin-infra-* providers and app-* skills that handle multi-provider deployment.

How do I set up SSH access to managed servers in a DevOps inventory?▼

SSH access to managed servers is integrated into the inventory system. Load your server profile, list available servers with filtering options, then use the unified interface to establish SSH connections—no separate authentication setup required per provider.

What inventory format does a profile-first DevOps system require?▼

Profile-first inventory uses a structured device profile format with AGENT_DEVOPS_*, PROVIDER_*, and SERVER_* keys. This format enables unified listing, filtering, and deployment references across your infrastructure while maintaining a single source of truth.

Does inventory-driven DevOps integrate with deployment workflows?▼

Yes. Deployment integration works through profile.deployments references linked to profile.servers. Route deployment tasks to provisioning skills, which read the inventory profile and execute workflows across your multi-provider infrastructure automatically.

What happens to server history in multi-provider inventory systems?▼

History retention tracks server changes and operations across all providers. The unified inventory maintains deployment and operational history, enabling audit trails and historical analysis of your infrastructure changes over time.