ipam-allocation
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Allocate IP address space (aggregates/prefixes/subnets and individual IP addresses) on a supported IPAM platform — currently NetBox (REST), Infoblox NIOS (WAPI), SolarWinds IPAM (SOAP/SWIS verb invocation, not REST), Nautobot (REST), Micetro (REST), and phpIPAM (REST). Use when an agent needs to reserve network space or assign an IP address, distinct from creating DNS records for that address (see dns-record-management for that). Assumes an authenticated client for the target platform's API is already available; this skill does not provision or authenticate it. Not every platform uses the same call mechanism — check references/INDEX.md before assuming REST.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Not for creating the DNS record that points at an allocated address — see dns-record-management for that (a separate concept from …
- Very specific: line 59
Does not cover DHCP scope/lease configuration (see dhcp-scope-management), network discovery, or DNS record creation on any platform — …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
IPAM Allocation
Allocates network/subnet space and individual IP addresses on whichever IPAM platform the caller is targeting, following that platform's own documented procedure and call mechanism exactly.
When to use this skill
- Reserving a new subnet/prefix from an existing address pool, or assigning an available IP address, on a supported IPAM platform.
- Not for creating the DNS record that points at an allocated address — see
dns-record-managementfor that (a separate concept from address-space allocation, even on platforms like Infoblox that offer both).
Universal concepts (shared IPAM vocabulary, not a wire standard)
There is no RFC grounding IPAM allocation the way RFC 1035 grounds DNS — every platform's allocation model is its own product design. What is genuinely shared:
- Address space is hierarchical: a parent block is carved into child blocks, which are carved into individual addresses. Every platform in this skill models this, even though the exact terms differ (NetBox: aggregate → prefix → IP; Infoblox: network container → network → IP; SolarWinds: subnet → IP node; Nautobot: prefix → child prefix → IP; Micetro: range → sub-range → IP; phpIPAM: section → subnet, optionally nested → address).
- "Available" is often computed, not a stored fact. Several platforms calculate what's free on the fly rather than maintaining a persistent free-list — don't assume a "list available" response is a set of real, reservable records; confirm what the specific platform actually guarantees.
- Allocation and reservation are not always the same operation. Some platforms allocate immediately and permanently on one call; others (SolarWinds, and Micetro's optional temporary claim) have a distinct, time-boxed hold before a final commit. Check the target platform's procedure file before assuming either shape.
- Not every platform's call mechanism is REST. SolarWinds IPAM is SOAP/verb-invocation
(
Invoke-SwisVerb), not HTTP methods — confirm the mechanism inreferences/INDEX.mdbefore assuming GET/POST semantics apply.
See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
Procedure
- Identify the target platform — from the caller's request or the
platformargument. Checkreferences/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet. - Open
references/<platform>/procedure.mdand follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist. - Report the outcome using that platform procedure's own status vocabulary — don't normalize it away, and don't conflate a reservation with a final allocation on a platform that distinguishes them.
Known limitations
- Currently covers NetBox, Infoblox NIOS (allocation only, not DNS records — see
dns-record-managementfor those), SolarWinds IPAM, Nautobot, Micetro (address space only), and phpIPAM. A platform not listed inreferences/INDEX.mdneeds a new reference file before this skill can be used for it. - Does not cover DHCP scope/lease configuration (see
dhcp-scope-management), network discovery, or DNS record creation on any platform — those are adjacent capabilities, not address-space allocation.
Contributing to this skill
SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated client and call mechanism (REST, WAPI, or SOAP/SWIS verb
invocation) — see references/INDEX.md for which, and that platform's procedure.md for the specific
operations.
Verification checklist
- Target platform confirmed against
references/INDEX.mdbefore proceeding, including its call mechanism (REST vs. non-REST) - That platform's own
procedure.mdwas followed, including its own confirmation/reservation semantics — not a generic/improvised sequence - Outcome reported using the platform procedure's own status vocabulary
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

