// Analyze and correlate Infrahub data using the MCP server. Use when querying live infrastructure data to answer operational questions, detect drift, correlate node types, investigate service impact, check maintenance windows, or produce ad-hoc reports — without writing pipeline code.
Shared references and cross-cutting rules used by all Infrahub skills. Contains GraphQL query syntax, .infrahub.yml configuration format, and common rules for git integration, display label caching, and Python environment setup. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
Audit an Infrahub repository against all best practices and rules. Use when reviewing a project for compliance, onboarding to an existing repo, or before deployment to catch issues early.
Create and manage Infrahub check definitions. Use when writing validation logic, creating Python checks that run in proposed change pipelines, or building data quality guards for Infrahub.
Create and manage Infrahub Generators. Use when building design-driven automation that creates infrastructure objects from templates, topology definitions, or any design-to-implementation workflow in Infrahub.
Create and manage Infrahub custom menus. Use when designing navigation menus, organizing node types in the UI, or customizing the Infrahub web interface sidebar.
Create and manage Infrahub object data files. Use when populating infrastructure data, creating device instances, locations, organizations, module installations, or any other data objects for an Infrahub repository.
| name | infrahub-analyst |
| description | Analyze and correlate Infrahub data using the MCP server. Use when querying live infrastructure data to answer operational questions, detect drift, correlate node types, investigate service impact, check maintenance windows, or produce ad-hoc reports — without writing pipeline code. |
| metadata | {"version":"1.1.0","author":"OpsMill"} |
Expert guidance for interactive data analysis against a live Infrahub instance. This skill uses the Infrahub MCP server to query, correlate, and reason over infrastructure data on demand — answering operational questions that span multiple node types and relationships.
Use this skill for any question of the form "what does Infrahub currently know about X, and how does it relate to Y?"
Typical question patterns:
For automated, pipeline-enforced checks that
block proposed changes, see
../infrahub-check-creator/SKILL.md.
For repeatable scheduled reports exported as
artifacts, see ../infrahub-transform-creator/SKILL.md.
The Infrahub MCP server exposes tools that let Claude query Infrahub data directly. The typical workflow:
| Priority | Category | Prefix | Description |
|---|---|---|---|
| CRITICAL | MCP Tools | mcp- | Available Infrahub MCP tools, invocation patterns, response structure |
| CRITICAL | Query Patterns | query- | GraphQL structures for fetching, filtering, and traversing relationships |
| HIGH | Correlation | correlation- | Joining, diffing, and reasoning over data from multiple queries |
| HIGH | Reporting Output | reporting- | Presenting findings: summaries, tables, per-object detail, remediation hints |
| MEDIUM | Approach Selection | approach- | When to use MCP analysis vs InfrahubCheck vs Transform |
When the Infrahub MCP server is connected, Claude can call tools such as:
mcp__infrahub__infrahub_query — Execute a
GraphQL query (primary tool)mcp__infrahub__infrahub_list_schema — List
available node kindsmcp__infrahub__infrahub_get — Retrieve a
specific object by ID or filtersmcp__infrahub__infrahub_create — Create an
object (remediation, on a branch)mcp__infrahub__infrahub_update — Update an
object (remediation, on a branch)# Example: find all devices in an active
# maintenance window
query MaintenanceDevices {
MaintenanceWindow(status__value: "active") {
edges {
node {
name { value }
start_time { value }
end_time { value }
devices {
edges {
node {
name { value }
role { value }
site {
node { name { value } }
}
}
}
}
}
}
}
}
1. Understand the question
→ "Which services depend on devices currently
in a maintenance window?"
2. Identify the node types involved
→ MaintenanceWindow, DcimDevice, Service
(or equivalent in your schema)
3. Query current state
→ mcp__infrahub__infrahub_query — one query
per node type, or combined
4. Correlate the data
→ Join across node types, filter, count, diff
5. Report findings
→ Summarize with counts, list affected objects,
suggest next steps