opsmill/infrahub-skills

infrahub-managing-menus

Creates, modifies and debugs Infrahub custom navigation menus for the web UI sidebar, organizing node types into logical groups.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/opsmill/infrahub-skills --skill infrahub-managing-menus

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Infrahub Menu Creator

Overview

Expert guidance for creating Infrahub custom menus. Menus control the left-side navigation in the web interface, organizing schema node types into a custom hierarchy.

Project Context

Existing menu files: !find . -name "*.yml" -path "*/menus/*" 2>/dev/null | head -10

Schema files (to identify available node types): !find . -name "*.yml" -path "*/schemas/*" -o -name "*schema*" -name "*.yml" 2>/dev/null | head -10

When to Use

  • Designing navigation menus for the Infrahub web UI
  • Organizing node types into logical groups

and hierarchies

  • Adding icons and labels to menu items
  • Setting up group headers (non-clickable)

with nested children

  • Configuring schema nodes to use custom menus

instead of auto-generated ones

  • Reordering, renaming, or regrouping an existing

menu file

  • Debugging why a menu item does not appear, or

lands in the wrong group

Rule Categories

PriorityCategoryPrefixDescription
CRITICALFormatformat-apiVersion, kind, spec
CRITICALPropertiesitem-name, namespace, label, kind
HIGHHierarchyhierarchy-Nesting, group headers, data
HIGHIconsicons-MDI icon reference, choices
MEDIUMSchemaschema-includeinmenu, kind links
LOWPatternspatterns-Flat menu, comments, links

Schema Features This Skill Depends On

A custom menu doesn't replace the auto-menu — it augments it. Schemas need cooperating settings to avoid duplicates and stay UI-stable.

Duplicates come from two places, and only one of them is the schema's. Nodes the auto-menu also emits are settled below with include_in_menu: false; sections Infrahub itself ships are settled in the menu file with parent:, covered in rules/hierarchy-nesting.md.

If the menu item...The schema must...See
Links to a schema node's list view via kind:Define that node (or generic) so the URL resolves — and set include_in_menu: false on it to suppress the duplicate auto-menu entryrules/schema-integration.md
Shows all subtypes under one entry via a generic kindHave the generic defined, with all the relevant nodes inherit_from it../infrahub-managing-schemas/rules/hierarchy-setup.md
Should appear at a specific position when auto-menu is in playSet order_weight on the schema node (auto-menu uses it; custom menu ignores it)../infrahub-managing-schemas/rules/display-order-weight.md
Groups subtypes under a parent node entrySet menu_placement: <FullKind> on each subtype so the auto-menu side groups consistently with the custom menu../infrahub-managing-schemas/rules/display-menu-placement.md

Audit include_in_menu on every node you reference from the menu file — the sidebar duplicates that this prevents look to users like the custom menu is "broken", but the fix is on the schema side.

Menu File Basics

yaml
---
apiVersion: infrahub.app/v1
kind: Menu
spec:
  data:
    - namespace: Dcim
      name: DeviceMenu
      label: "Devices"
      icon: "mdi:server"
      kind: DcimDevice        # Links to schema node list view

apiVersion, kind: Menu, and spec.data are always required. Each menu item needs name and namespace.

Workflow

Follow these steps when creating a menu:

  1. Gather requirements — Ask what schema nodes

exist, how they should be grouped, and whether the user wants flat or hierarchical navigation.

  1. Read relevant rules — Read rules/format-structure.md

for the required YAML structure, rules/item-properties.md for item fields, and rules/icons-reference.md to pick appropriate MDI icons. Read rules/hierarchy-nesting.md before placing any item, flat menus included: Infrahub already ships IPAM, Object Management, Branches and others, and anything belonging in one of those attaches with parent: rather than being declared again.

  1. Generate the menu YAML — Start with the

$schema comment and apiVersion/kind/spec structure. Apply rules from step 2.

  1. Add registration and schema guidance — Every

menu file output must include:

  • A YAML comment block showing how to register

the file in .infrahub.yml under the menus: key (see rules/format-structure.md)

  • A YAML comment block advising to set

include_in_menu: false on every schema node that appears in the custom menu, to prevent duplicate sidebar entries (see rules/schema-integration.md)

Include these as comments at the top of the file, before the --- document separator. This ensures the user sees the guidance alongside the menu definition.

Supporting References

  • [examples.md](./examples.md) -- Four worked

menu hierarchies (flat, grouped, generic-linked, full multi-domain) ready to copy and adapt

  • [infrahub-yml-reference.md](../infrahub-common/infrahub-yml-reference.md)

-- .infrahub.yml project configuration

  • [common/rules/](../infrahub-common/rules/)

-- Shared rules (git integration, caching gotchas) that apply across all skills

  • [../infrahub-common/rules/workflow-information-priority.md](../infrahub-common/rules/workflow-information-priority.md)

-- Skill content first; how to consult docs.infrahub.app on a genuine gap (e.g. deleting nodes)

  • [managing-schemas](../infrahub-managing-schemas/SKILL.md)

-- Schema node kinds that menus link to

  • [rules/](./rules/)

-- Individual rules organized by category prefix

from this repository

More skills

All skills
opsmill
Community

infrahub-analyzing-diagnostics

Analyze an already-collected infrahub-collect diagnostic bundle — traceback and failure triage across service logs, incident correlation, and known-issue matching against opsmill/infrahub GitHub issues. TRIGGER when: the user says they collected a diagnostic bundle, gives you a bundle path, or pastes bundle contents — and asks what's wrong, wants the logs or tracebacks analyzed, asks "what does this bundle say", wants errors triaged/correlated, or asks whether a crash is a known issue. DO NOT TR

1h installs
2
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-analyzing-data

Analyzes and correlates live Infrahub data via the MCP server — answers operational questions, detects drift, and investigates impact. TRIGGER when: querying infrastructure data, checking compliance, investigating change impact, producing ad-hoc reports. DO NOT TRIGGER when: writing automated checks, building transforms, designing schemas, populating data files, planning an Infrahub version upgrade (use infrahub-planning-upgrades). ALWAYS pass the user's question verbatim as args — this skill ru

1h installs
3
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-auditing-repo

Audits an Infrahub repository against best practices and rules, producing a structured compliance report. TRIGGER when: reviewing repo for compliance, onboarding to existing project, pre-deployment validation, catching issues. DO NOT TRIGGER when: creating schemas, writing checks/generators, querying live data, populating objects, planning an Infrahub version upgrade (use infrahub-planning-upgrades).

1h installs
3
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-collecting-diagnostics

Collect a redacted local diagnostic bundle (logs, config, version, state) for an OpsMill expert hand-off. TRIGGER when: Infrahub is broken/failing/erroring, the user asks for help debugging, wants to collect logs/diagnostics, prepares a hand-off for OpsMill support, or reports a crash/timeout/connection issue (upgrade failure, stuck branch, container CrashLoopBackOff, 500s, OOM). DO NOT TRIGGER when: debugging a check, transform, generator, menu, or schema in the repository (use the infrahub-man

1h installs
3
GitHub stars
27
Updated
Nov 9