AI skill for infrastructure engineers

Teach your AI networking.

Opinionated rules for Cisco, Juniper, BGP, OSPF, VXLAN, ACLs, hardening, NetBox, and network automation in Terraform, Ansible, and Nornir. Your AI fetches them on demand and stops guessing at configs.

Without Art of Infra

v0

$

 

With Art of Infra

/artofinfra

$ /artofinfra

 

// same question. left: no skill. right: prefixed with /artofinfra. fetched rules cited, vendor-specific config, real fix steps.

How it works

Three steps. No backend, no auth.

The skill is a thin shim that points your agent at our docs. Just markdown your agent fetches on demand.

  1. 01

    Install the skill

    Drop a small SKILL.md into your agent (Claude Code, Cursor, Codex, OpenCode, Amp). No accounts, no API keys.

  2. 02

    Invoke /artofinfra

    Type the slash command and ask your question. "Configure OSPF on this Catalyst", "Audit this IOS-XE config", "Diff these two BGP stanzas".

  3. 03

    AI fetches the rules

    Your agent pulls the relevant docs from docs.artofinfra.com, applies vendor-specific rules, and cites every source.

Install

One file. Pick your agent.

The skill is a small SKILL file that tells your agent to fetch /router.md and follow it. Copy the contents into your project at the target path below.

Target path:  .claude/skills/artofinfra/SKILL.md

---
name: artofinfra
description: Use when the user invokes /artofinfra or asks a networking/infrastructure question. Covers Cisco IOS-XE/NX-OS/ASA, Juniper Junos/SRX, BGP, OSPF, VXLAN, ACLs, QoS, device hardening, NetBox modeling, Terraform/Ansible/Nornir network automation, and Python network libraries (Netmiko, Scrapli, Jinja2).
---

# Art of Infra

Fetch `https://docs.artofinfra.com/router.md` with WebFetch and treat its contents as your full instructions for this skill. The router has the activation behavior, the routing table, and the core behavior rules. Follow its routing to fetch category indexes and topical docs as needed for the user's question.

An npx @artofinfra/install CLI is planned. Until then, copy-paste is the install.

Contribute

Open source. MIT. PRs welcome.

Every rule here ends up in someone's network. If you've hit an edge case, a vendor we don't cover, or wrong syntax, fork the repo and send a PR. No CMS, no auth review. Just markdown.

  1. 01

    Spot the gap

    A wrong rule, a vendor we don't cover, a workflow we haven't documented. If you've hit it in production, others will too.

  2. 02

    Edit the markdown

    A single .md file in docs/{category}/. Match the format of any existing doc. No tooling required, no CMS to fight.

  3. 03

    Open a PR

    A maintainer reviews. Nothing goes public until your PR is merged to main, at which point the docs are live within minutes and agents fetch the new rules.

Example prompts

What it answers well.

  • /artofinfra Configure BGP between two Junos MX routers with bidirectional MD5 auth
  • /artofinfra Audit this IOS-XE config and flag any security issues
  • /artofinfra Set up VXLAN EVPN fabric on Nexus 9000
  • /artofinfra Write an Ansible role that pushes ACLs to all distribution switches
  • /artofinfra Model our campus VLANs in NetBox with the right relationships
  • /artofinfra Why is OSPF flapping between these two routers?