dhcp-scope-management
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, read, update, and delete a DHCP scope/subnet and its lease reservations — currently Infoblox NIOS (WAPI range/fixedaddress objects), ISC Kea (Control Agent subnet_cmds/host_cmds hook commands), and Microsoft Windows Server DHCP Server (DhcpServer PowerShell module). Distinct from ipam-allocation, which reserves address space and IPs as inventory records; this skill manages the DHCP service configuration that actually leases addresses to clients from that space. Assumes an authenticated/permitted client for the target platform (WAPI session, Control Agent HTTP access, or a PowerShell session with the DhcpServer module) 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
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- 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
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Not for reserving IP address space or an individual IP as an inventory record — see ipam-allocation for that.
- Very specific: line 73
Does not cover IP address space allocation as an inventory record — see ipam-allocation for that.
- Very specific: line 74
Does not cover DHCPv6, DHCP failover-partner relationship setup, or lease-level management independent of scope/reservation configuration — …
≈ “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
DHCP Scope Management
Manages DHCP scope/subnet configuration and lease reservations on whichever DHCP platform the caller is targeting, following that platform's own documented procedure exactly.
When to use this skill
- Creating, reading, updating, or deleting a DHCP scope/subnet, or creating/deleting a lease reservation for a specific client, on a supported platform.
- Not for reserving IP address space or an individual IP as an inventory record — see
ipam-allocationfor that. A platform like Infoblox may expose both concerns through related objects, but allocating the address as inventory and configuring DHCP to actually lease it are different operations; this skill is only the latter.
Universal concepts (shared DHCP vocabulary, not a wire standard)
There is no wire standard grounding management-API shape here the way RFC 1035/2136/1123 ground
DNS — RFC 2131 defines the DHCP protocol itself (what a client and server exchange on the wire), not
how a vendor's own API/CLI should represent scope or reservation configuration. Every platform below
designed that management surface independently. What is verified true across all three platforms
currently covered (Infoblox NIOS, ISC Kea, Microsoft DHCP Server — see references/INDEX.md):
- A scope/subnet's address-space definition and its DHCP-service configuration are handled as
distinct concerns from address-space allocation as inventory, even on a platform that also does
IPAM. Infoblox's
rangeobject is separate from itsnetworkobject; Kea'ssubnet_cmdsoperate on service configuration, not an inventory record; Windows's scope cmdlets have no IPAM-inventory counterpart at all in this module. This is the basis for this skill's own boundary withipam-allocation— see "When to use this skill" above. - A lease reservation ties a specific client identifier (most commonly a MAC address, though every
platform here also supports at least one alternate identifier type) to a specific address, and is a
distinct object from the scope/subnet it lives in. Infoblox's
fixedaddress, Kea's host reservations, and Windows'sDhcpServerv4Reservationare all separate create/read/update/delete operations from their platform's own scope object, not a field on the scope itself. - Updating a scope/subnet's core configuration is not a full-replace operation by default on every
platform — this is NOT a safe generalization, it's flagged here specifically because it does NOT
hold universally. Kea's plain
subnet4-updatefully overwrites the subnet (anything omitted is removed); Infoblox's range/fixedaddress updates and Microsoft'sSet-DhcpServerv4Scopeboth change only the fields explicitly supplied. Confirm the target platform's own update semantics in itsprocedure.mdbefore assuming either behavior. - Deleting a scope/subnet does not, by itself, guarantee cleanup of the leases or reservations
issued under it on at least one platform (Kea's
subnet4-delexplicitly does not remove associated leases/reservations, per its own documentation) — this is unverified for Infoblox and Microsoft, so treat "does deletion clean up dependents" as a per-platform question to check, not an assumed yes/no, before relying on it in an automated flow. - Deleting a scope/subnet or a reservation that may be actively in use is treated as a confirmation-gated action in every platform's own procedure file here — not because of a shared vendor guarantee, but because each procedure gates it regardless of what the vendor's API itself enforces.
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.
Known limitations
- Currently covers Infoblox NIOS, ISC Kea, and Microsoft DHCP Server — see
references/INDEX.md. A platform not listed there needs a new reference file before this skill can be used for it. - Does not cover IP address space allocation as an inventory record — see
ipam-allocationfor that. - Does not cover DHCPv6, DHCP failover-partner relationship setup, or lease-level management
independent of scope/reservation configuration — see each platform's own
procedure.mdfor the specifics of what its file does and doesn't address.
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/permitted client and call mechanism (WAPI, a JSON
command/response envelope over HTTP, or PowerShell/CIM cmdlets — not all of them REST) — 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-like WAPI, JSON command envelope, or PowerShell/CIM — not all are REST) - That platform's own
procedure.mdwas followed, including its own confirmation gates on destructive changes (scope deletion, which affects every active lease under it) - 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.

