arn-infra-discover

Inventory infrastructure tooling and verify authentication across cloud providers.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-infra-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-infra-discover
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-infra/skills/arn-infra-discover
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-infra-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proactively inventory installed infrastructure tools (MCPs, CLIs, Claude Code plugins) and verify authentication state, enabling teams to harmonize tooling with provider configurations and reduce configuration drift.

Core Features & Use Cases

  • Detects provider MCPs, CLIs, and Claude Code plugins and reports official status and capabilities.
  • Checks authentication state for each tool and flags unauthenticated or misconfigured setups.
  • Generates a tooling manifest and provides installation recommendations to streamline onboarding and governance.

Quick Start

Run /arn-infra-discover to begin inventorying your provider tooling and generate a tooling manifest.

Frequently Asked Questions about arn-infra-discover

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

FAQPage Schema
How do I inventory installed infrastructure tools like CLIs and MCPs across cloud providers?

To inventory infrastructure tooling across cloud providers, you can run an automated discovery process that detects installed CLIs, MCPs, and Claude Code plugins. This process identifies official tool statuses and reports their capabilities to harmonize provider configurations.

Why does configuration drift happen with cloud provider tooling and how can I detect it?

Configuration drift happens when local infrastructure tools become misaligned with provider setups. You can detect drift by verifying the authentication state of your CLIs and MCPs, which flags unauthenticated or misconfigured setups for remediation.

Can I check authentication state for MCPs and Claude Code plugins before deployment planning?

Yes, you can check authentication state for MCPs and Claude Code plugins during the discovery phase. This verification flags unauthenticated or misconfigured setups, ensuring your tooling manifest is accurate for deployment planning.

What is a tooling manifest and when do I need one for infrastructure governance?

A tooling manifest is a generated record of your inventoried infrastructure tools, their authentication states, and capabilities. You need one for infrastructure governance to streamline onboarding and reduce configuration drift across cloud providers.

How do I generate installation recommendations for missing infrastructure tooling?

You can generate installation recommendations by running an automated discovery process that inventories existing CLIs and MCPs. The resulting tooling manifest identifies gaps and provides actionable installation recommendations for missing components.

Does infrastructure tooling discovery work with multiple cloud providers?

Yes, infrastructure tooling discovery is provider-aware, meaning it works across multiple cloud providers. It detects provider-specific MCPs and CLIs, checks their authentication states, and harmonizes tooling with provider configurations.