New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ipam DNS Audit

by LeoYeAI in LeoYeAI/openclaw-master-skills

IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health.

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Ipam DNS Audit

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill ipam-dns-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills ipam-dns-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ipam-dns-audit .claude/skills/ipam-dns-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ipam-dns-audit
GitHub stars
2.2k
Token cost
~4.4k tokens
SKILL.md length
1,750 words
Files
4 (incl. references)
Skills in repo
1,235
Repo updated
First seen
Licence
Apache-2.0

At a glance

IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health.

  • Works in 6 steps: IPAM Inventory Analysis → Live Subnet Discovery → DNS Record Audit → …
  • Tasks that involve Accounting and bookkeeping
  • SKILL.md covers When to Use, Prerequisites, Procedure and Threshold Tables, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ipam DNS Audit is an agent skill from LeoYeAI/openclaw-master-skills. IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health. Platform-agnostic with references to common IPAM implementations. Uses the reconciliation procedure shape — IPAM source extraction, live discovery, diff analysis, and remediation reporting.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `_meta.json`, `references/cli-reference.md` and `references/subnet-dns-reference.md`).

It sits in Business, Finance & HR, covering Accounting and bookkeeping. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Accounting and bookkeeping

Example prompts

  • “/ipam-dns-audit”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. IPAM Inventory Analysis
  2. Live Subnet Discovery
  3. DNS Record Audit
  4. Conflict Detection
  5. Utilization Reporting
  6. Reconciliation Report

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ipam DNS Audit loads about 4.4k tokens when it runs, and up to ~7.4k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 1,750 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its Apache-2.0 licence (© LeoYeAI). 1,750 words, ~4,390 tokens.

Download SKILL.mdSave it as .claude/skills/ipam-dns-audit/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
ipam-dns-audit
description
IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health. Platform-agnostic with references to common IPAM implementations. Uses the reconciliation procedure shape — IPAM source extraction, live discovery, diff analysis, and remediation reporting.
license
Apache-2.0
metadata.safety
read-only
metadata.author
network-security-skills-suite
metadata.version
1.0.0
metadata.openclaw
{"emoji":"📊","safetyTier":"read-only","requires":{"bins":[],"env":[]},"tags":["ipam","dns","ip-conflict"],"mcpDependencies":[],"egressEndpoints":[]}

IPAM/DNS Reconciliation Audit

IP Address Management (IPAM) and DNS record reconciliation audit for assessing the accuracy and health of IP address allocations, subnet utilization, and DNS records. This skill provides a systematic methodology for comparing IPAM-recorded state against live subnet activity and DNS resolution results — identifying conflicts, orphaned records, exhaustion risks, and stale entries that degrade network reliability.

IPAM systems maintain the authoritative record of how IP address space should be allocated: prefix hierarchies, subnet assignments, VLAN mappings, static reservations, and DHCP scopes. DNS servers maintain the mapping between names and addresses. Live network state — ARP tables, DHCP leases, and actual DNS resolution — reveals what the network actually looks like. The gap between recorded allocations and live reality is the reconciliation target.

This skill complements source-of-truth-audit (which covers the full device inventory) by focusing specifically on IP address and DNS record accuracy. Reference references/cli-reference.md for DNS query tools, ARP/neighbor table commands, DHCP inspection, and IPAM API patterns. Reference references/subnet-dns-reference.md for RFC allocation guidance, CIDR math, DNS record types, and DHCP scope planning.

When to Use

  • Subnet exhaustion investigation — determining actual utilization when IPAM shows a prefix nearing capacity
  • DNS troubleshooting — validating forward/reverse consistency when name resolution failures occur
  • IP conflict diagnosis — tracking duplicate IP assignments causing intermittent connectivity
  • Pre-migration planning — auditing IP allocations before data center moves or re-addressing projects
  • DHCP scope health check — verifying lease utilization and scope configuration against IPAM records
  • Compliance audit — demonstrating IP address accountability for regulatory or internal governance requirements
  • Post-change verification — confirming that IP moves, DNS updates, or subnet resizing are reflected in IPAM

Prerequisites

  • IPAM data access — read-only access to the IPAM platform via API or export; for NetBox IPAM module: API token with IPAM read permissions; for Infoblox: WAPI credentials with network/record read access; for BlueCat: API credentials with Address Manager read access
  • DNS server access — ability to query authoritative DNS servers directly (not just recursive resolvers); zone transfer (AXFR) access preferred for comprehensive audits; at minimum, individual record lookups via dig or nslookup against the authoritative server
  • Network device access — read-only credentials for switches and routers to collect ARP tables and DHCP relay information; SNMP v2c/v3 community strings or SSH access for CLI commands
  • Scope definition — target subnets, VRFs, and DNS zones identified before the audit begins; large environments should scope by site, VRF, or /16 aggregate to keep the audit manageable
  • Baseline IPAM expectations — understand what the IPAM is expected to track: all IPs including DHCP dynamics, or only static allocations? This determines what constitutes a "gap" versus expected behavior

Procedure

Follow these six steps sequentially. Each step builds on the previous — IPAM extraction and live discovery feed the diff and conflict detection, which feeds utilization analysis, culminating in the reconciliation report.

Step 1: IPAM Inventory Analysis

Extract authoritative IP allocation data from the IPAM system to build a complete picture of intended address space usage.

Prefix Hierarchy Review — Export the prefix hierarchy for in-scope VRFs. Verify supernet/subnet containment: every child prefix must be within its parent aggregate. Identify orphaned prefixes (no parent) and overlapping definitions (same address space in same VRF). See references/cli-reference.md for IPAM API patterns (NetBox, Infoblox, BlueCat).

VLAN-to-Subnet Mapping — Cross-reference VLAN assignments with prefix VLAN fields. Flag VLANs with no subnet (unused or misconfigured) and subnets with no VLAN association (missing metadata).

IP Reservation Audit — Categorize IPs by status: static, DHCP pool, reserved (gateways, HSRP/VRRP VIPs), and available. Verify gateway IPs are marked reserved. Check for IPs marked "Active" with no device or interface record — orphaned allocations.

IPv4 Exhaustion Assessment — Calculate raw utilization per subnet: assigned addresses / total usable addresses. Flag prefixes above threshold (typically 80% warning) and identify remaining contiguous free blocks.

Step 2: Live Subnet Discovery

Discover actual IP address usage to compare against IPAM records. No single source captures all active addresses — multiple collection methods are required.

ARP Table Analysis — Collect ARP tables from Layer 3 gateways for each in-scope subnet. Each ARP entry represents a recently active IP. On Cisco IOS: show ip arp vrf <name>. On Juniper JunOS: show arp interface <l3-interface>. On Arista EOS: show ip arp vrf <name>.

DHCP Lease Correlation — Extract active leases from the DHCP server. Compare against IPAM DHCP scope definitions to ensure boundaries match. Identify leases outside defined scopes — these indicate misconfigured or rogue DHCP servers.

Ping Sweep Validation — For subnets where ARP data is incomplete (routed subnets with no local L3 interface), use ICMP sweeps: nmap -sn <prefix> or fping -g <prefix>. Non-responding IPs are not necessarily unused — firewalls may block ICMP.

Duplicate IP Detection — Analyze ARP tables for multiple MAC addresses on the same IP (gratuitous ARP conflicts). Rapidly alternating MACs for a single IP indicate active conflicts causing intermittent connectivity.

Step 3: DNS Record Audit

Audit DNS records for consistency, accuracy, and hygiene. DNS errors cause application failures often misdiagnosed as network issues.

Forward/Reverse Consistency — For each A record, verify a corresponding PTR record points back to the same hostname. For each PTR, verify the referenced hostname has a matching A record. Use dig +short <hostname> A and dig +short -x <ip> to test pairs. Inconsistencies break reverse DNS used by mail servers, logging, and security tools.

Stale Record Detection — Cross-reference A records against IPAM and live ARP tables. A records pointing to IPs that IPAM shows as available or decommissioned are stale. Records pointing to IPs with no ARP activity for 90+ days may reference removed hosts.

CNAME Chain Validation — Verify CNAME records resolve to valid targets. Flag chains longer than two hops (add latency and fragility). Verify no CNAME exists at a zone apex or alongside MX/NS records (RFC 1034 prohibition).

Delegation Chain Integrity — Verify NS records for delegated zones point to responding servers. Check MX records resolve to A records (not CNAMEs, per RFC 2181). Validate SOA serial numbers across primary and secondary servers for replication currency.

TTL Review — Audit TTL appropriateness: infrastructure records (NS, MX, SOA) should use 3600–86400s; frequently changing records (load balancers, failover) need 60–300s; static host records typically use 3600s.

Show full SKILL.md (755 more words)Show less
Step 4: Conflict Detection

Identify conflicts that cause operational problems — higher severity than record hygiene issues from Step 3.

Overlapping Subnet Definitions — Compare all prefix entries within each VRF for overlaps. Two /24 prefixes covering the same range, or a /24 outside its documented /16 parent, indicate data entry errors. Use bitwise comparison to detect non-obvious overlaps (e.g., 10.1.0.0/23 and 10.1.1.0/24).

Duplicate IP Assignments — Cross-reference IPAM assignments with live ARP. Two IPAM records for the same IP in the same VRF is a data conflict. Two MACs for the same IP in ARP is a live conflict. Either causes packet loss and needs immediate remediation.

DNS Record Conflicts — Multiple A records for the same hostname (without intentional round-robin) indicate misconfiguration. CNAME records conflicting with other types at the same name violate standards. PTR records with no matching forward A record are orphaned.

Orphaned PTR Records — Reverse zone entries pointing to hostnames with no forward A record, or to IPs that IPAM shows unallocated. These accumulate after decommissions when reverse zones are not cleaned. Audit by iterating PTR records and performing forward lookups.

Step 5: Utilization Reporting

Compute utilization metrics for capacity planning, exhaustion risk identification, and overprovisioning detection.

Subnet Utilization Calculation — For each prefix: utilization = allocated_addresses / usable_addresses × 100%. Usable addresses exclude network and broadcast. Compare IPAM-calculated vs ARP-based utilization (active IPs vs total) — significant divergence indicates stale IPAM data.

Threshold Classification — Apply standard thresholds: >90% critical (expand immediately), >80% warning (plan within quarter), 50–80% healthy, <20% oversized (reclaim candidate). DHCP pools tolerate higher utilization than static ranges.

DHCP Scope Exhaustion Projection — Calculate remaining leases per scope and project time-to-exhaustion based on lease growth rate. Scopes with <10% free and growing demand need immediate expansion or lease time reduction.

IPv6 Adoption Coverage — For dual-stack environments, measure the percentage of subnets with corresponding IPv6 prefixes. Track GUA vs ULA adoption rates. Identify IPv4-only sites as migration gaps.

Step 6: Reconciliation Report

Compile findings into a structured report with health scores, conflict inventory, and actionable remediation.

IPAM Health Scorecard — Aggregate subnet utilization distribution, IPAM-vs-live accuracy, prefix hierarchy integrity, and VLAN mapping completeness into a composite health score.

DNS Audit Findings — Summarize forward/reverse consistency rate, stale record count, CNAME chain issues, and delegation integrity. Group by zone for targeted remediation.

Conflict Inventory — List conflicts ordered by severity: duplicate IPs first (packet loss), overlapping subnets second (routing ambiguity), DNS conflicts third (resolution failures). Include affected hosts and recommended resolution.

Capacity Planning Recommendations — Identify subnets needing expansion within 90 days, recommend oversized subnet reclamation, suggest DHCP scope adjustments, and flag IPv6 migration gaps.

Threshold Tables

MetricGoodWarningCriticalNotes
Subnet utilization<80%80–90%>90%Per-prefix allocated/usable ratio
DHCP scope free>20%10–20%<10%Remaining leases in scope
Forward/reverse match≥95%85–95%<85%A records with valid PTR
Stale A records<5%5–15%>15%A records pointing to inactive IPs
IPAM vs ARP accuracy≥90%80–90%<80%IPAM entries confirmed by ARP
Duplicate IPs detected01–3>3Per-VRF duplicate IP count
Orphaned PTRs<5%5–15%>15%PTR records with no forward match
VLAN-subnet mapping≥95%85–95%<85%VLANs with correct subnet association
IPv6 dual-stack coverage≥80%50–80%<50%Subnets with IPv6 counterparts

Decision Trees

Audit Scope Selection:
├─ Full enterprise audit?
│  ├─ >1000 subnets? → Scope by site/region, audit iteratively
│  └─ <1000 subnets? → Full-scope audit feasible in single pass
├─ Targeted investigation?
│  ├─ IP conflict report? → Focus on affected VRF/subnet
│  ├─ DNS resolution failures? → Focus on affected zones
│  └─ Capacity planning? → Focus on high-utilization prefixes
└─ Pre-migration audit? → Scope to migrating subnets and DNS zones

IPAM Data Source Selection:
├─ NetBox IPAM module? → Use /api/ipam/ REST endpoints
├─ Infoblox NIOS? → Use WAPI with network_view filtering
├─ BlueCat Address Manager? → Use REST v2 API
├─ Spreadsheet/manual? → Export to structured format first
└─ Multiple IPAM sources? → Reconcile between sources before live comparison

Duplicate IP Response:
├─ ARP table shows conflicting MACs for same IP?
│  ├─ Both MACs belong to known devices? → IP assignment error — reassign one
│  ├─ One MAC unknown? → Potential rogue device — investigate
│  └─ MACs alternating rapidly? → Active conflict — disable one port immediately
├─ IPAM shows same IP assigned to two records?
│  ├─ One record stale? → Archive stale record, confirm active device
│  └─ Both records active? → Investigate which device is using the IP
└─ Different VRFs? → Verify VRF isolation is intact (expected overlap)

Stale DNS Record Disposition:
├─ A record points to IPAM-available IP? → Delete (confirmed decommissioned)
├─ A record points to IP with no ARP activity?
│  ├─ Device exists in IPAM as active? → Verify device is powered on
│  └─ No device record? → Delete after 30-day notification hold
├─ PTR record with no forward match? → Delete (orphaned reverse entry)
└─ CNAME target unresolvable? → Delete or update to valid target

Report Template

markdown
# IPAM/DNS Reconciliation Report

## Executive Summary
- **IPAM source:** [NetBox IPAM / Infoblox / BlueCat / other]
- **Scope:** [VRFs/sites] — [prefix count] prefixes, [zone count] DNS zones
- **Audit date:** [date]
- **Composite IPAM Health Score:** [score]%

## Utilization Summary
| Tier | Prefix Count | Avg Utilization | At Risk |
|------|-------------|-----------------|---------|
| Critical (>90%) | | | Expand immediately |
| Warning (80–90%) | | | Plan expansion |
| Healthy (20–80%) | | | Monitor |
| Oversized (<20%) | | | Reclaim candidate |

## DNS Audit Summary
| Metric | Value | Threshold | Status |
|--------|-------|-----------|--------|
| Forward/reverse consistency | [%] | ≥95% | |
| Stale A records | [count] | <5% | |
| Orphaned PTR records | [count] | <5% | |
| CNAME chain violations | [count] | 0 | |
| Delegation integrity | [pass/fail] | pass | |

## Conflict Inventory

### Critical — Duplicate IP Assignments
| # | IP Address | VRF | MAC 1 | Device 1 | MAC 2 | Device 2 | Action |
|---|-----------|-----|-------|----------|-------|----------|--------|

### High — Overlapping Subnets
| # | Prefix A | Prefix B | VRF | Overlap Range | Action |
|---|----------|----------|-----|---------------|--------|

### Medium — DNS Record Conflicts
| # | Record | Type | Conflict | Action |
|---|--------|------|----------|--------|

## Capacity Planning
| Subnet | Current Util | Growth Rate | Projected Exhaustion | Recommendation |
|--------|-------------|-------------|---------------------|----------------|

## Remediation Priorities
1. [Immediate — Resolve duplicate IP conflicts]
2. [Short-term — Remove stale DNS records]
3. [Medium-term — Expand critical-utilization subnets]
4. [Ongoing — Reclaim oversized subnets for reallocation]
5. [Strategic — Close IPv6 dual-stack gaps]

## Appendix
- IPAM extraction parameters and query details
- DNS audit methodology (zones, servers, tools)
- ARP collection scope and device list
- Subnet math reference for utilization calculations

Troubleshooting

ARP tables show fewer IPs than expected — ARP entries expire (240s on Cisco, 1200s on Juniper). Collect during peak usage for maximum coverage. Devices communicating only within the same VLAN (L2 adjacent) may not appear in router ARP — check switch MAC tables. Ping sweeps supplement ARP for idle subnets.

DNS zone transfer (AXFR) denied — Many servers restrict AXFR to authorized secondaries. Fall back to individual lookups for known hostnames using dig @<auth-server> <name> A. Slower but avoids AXFR permissions. Check allow-transfer (BIND) or zone transfer settings (Windows DNS).

DHCP lease data unavailable — If the DHCP server is not directly accessible, check IPAM platforms that sync DHCP natively (Infoblox manages DHCP; NetBox requires external sync). Alternatively, analyze relay statistics: show ip dhcp relay statistics.

Subnet utilization mismatch between IPAM and ARP — IPAM shows high allocation but ARP shows few active hosts, indicating stale records. Cross-reference against device inventory (source-of-truth-audit skill). Clean stale allocations to restore accurate metrics.

Overlapping subnets not detected — Overlap detection requires VRF-scoped comparison. Multi-VRF environments legitimately overlap (e.g., 10.0.0.0/8 in multiple VRFs). Verify IPAM VRF assignments are correct — wrong VRF produces false alerts or misses real overlaps.

IPv6 utilization always ~0% — IPv6 /64 subnets have 2^64 addresses, making percentage meaningless. Measure by active host count instead. Focus audits on prefix hierarchy (/48 per site, /64 per VLAN) rather than per-subnet exhaustion.

© LeoYeAI, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/ipam-dns-audit of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • references/cli-reference.md
  • references/subnet-dns-reference.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Ipam DNS Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ipam DNS Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ipam DNS Audit this skillLeoYeAI/openclaw-master-skills2.2k—~4.4kAutomated safety check: PassApache-2.0
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence
ERPClaw ERP Controlleravansaber/erpclaw116—~18kAutomated safety check: PassGPL-3.0
Odoo Agency Fleet Reviewerpipe-org/mcp-odoo421—~699Automated safety check: PassMIT
Beancount Closebex-co/beancount-io296—~1.4kAutomated safety check: PassMIT

Similar skills

  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 7 days ago
    Business, Finance & HRAuto-check passed

  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 19 days ago
    Business, Finance & HRAuto-check passed

  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    116 GitHub stars~18k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    421 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

  • Beancount Close

    bex-co/beancount-io

    Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…

    296 GitHub stars~1.4k tokensUpdated today
    Business, Finance & HRAuto-check passed

  • Forward Implementation First

    Vuk97/forward-implementation-first

    Keeps an agent building and validating real output instead of servicing its own bookkeeping.

    176 GitHub stars~1.8k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo

  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Ipam DNS Audit

What does Ipam DNS Audit do?

IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health. Ipam DNS Audit is an agent skill from LeoYeAI/openclaw-master-skills. IP Address Management and DNS record reconciliation audit covering subnet utilization analysis, DNS forward/reverse consistency, IP conflict detection, and DHCP scope health.

When should I use Ipam DNS Audit?

Ipam DNS Audit fits situations like: tasks that involve Accounting and bookkeeping.

How do I install Ipam DNS Audit in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill ipam-dns-audit -a claude-code`. Or copy the skill folder (skills/ipam-dns-audit in LeoYeAI/openclaw-master-skills) into .claude/skills/ipam-dns-audit in your project. Claude Code loads it when a task matches its description.

How do I install Ipam DNS Audit in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill ipam-dns-audit -a codex`. Or copy the skill folder (skills/ipam-dns-audit in LeoYeAI/openclaw-master-skills) into .agents/skills/ipam-dns-audit in your project. Codex loads it when a task matches its description.

Can I use Ipam DNS Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill ipam-dns-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ipam-dns-audit, .gemini/skills/ipam-dns-audit, .github/skills/ipam-dns-audit and .opencode/skills/ipam-dns-audit in your project.

What does Ipam DNS Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Ipam DNS Audit is instructions for the agent only.

Does Ipam DNS Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ipam DNS Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ipam DNS Audit use?

Ipam DNS Audit is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ipam DNS Audit use?

About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.

What are the alternatives to Ipam DNS Audit?

Skills that share tags, products or a category with Ipam DNS Audit: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ipam DNS Audit?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.