dcim-asset-management
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, read, update, and delete a physical data-center asset (server, PDU, patch panel, network device chassis) and its rack-unit placement on a supported Data Center Infrastructure Management (DCIM) platform. Distinct from cmdb-asset-management, which manages logical Configuration Items and their service/relationship model — this skill manages the physical object's location, not its logical role. The same real-world server is often represented in both systems from two different angles; that overlap is expected, not a reason to merge the skills. Assumes an authenticated client for the target platform's API is already available; this skill does not provision or authenticate it. Currently covers NetTerrain (Graphical Networks), NetBox, and Nautobot — see references/INDEX.md for the full vendor list.
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
- dhcp-scope-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
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 a logical Configuration Item's service/relationship model (what depends on what, application ownership) — see cmdb-asset-management …
- Distinctive: line 22
Not for environmental/power-draw monitoring (temperature, humidity, real-time power consumption) — that is read-only telemetry, a different …
- Distinctive: line 28
No claims are stated as shared across vendors.
- Very specific: line 48
Does not cover logical CI/service-relationship data — see cmdb-asset-management for that.
- Distinctive: line 49
Does not cover environmental or real-time power-draw monitoring — that would be a separate, read-only/diagnostic-shaped capability, not …
≈ “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
DCIM Asset Management
Manages physical data-center assets and their rack-unit placement on whichever DCIM platform the caller is targeting, following that platform's own documented procedure exactly.
When to use this skill
- Creating, reading, updating, or deleting a physical asset record, or assigning/reassigning its rack-unit position, on a supported platform.
- Not for a logical Configuration Item's service/relationship model (what depends on what,
application ownership) — see
cmdb-asset-managementfor that. The same physical server commonly has a record in both systems: this skill's record is "where is it and what powers it," the CMDB's is "what does it do and what relies on it." Confirming or syncing a physical asset's identifier between the two systems is a real, expected integration point, not something either skill performs automatically — check both systems' own procedures if a caller needs both facts. - Not for environmental/power-draw monitoring (temperature, humidity, real-time power consumption) — that is read-only telemetry, a different shape from this skill's CRUD operations, and does not exist as a capability in this repository yet.
Universal concepts (shared DCIM vocabulary, not a wire standard)
No claims are stated as shared across vendors. Each platform's own procedure states what holds for it; do not assume shared behavior.
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
- Vendor coverage is limited to what's listed in
references/INDEX.md— a platform not listed there needs a new reference file before this skill can be used for it. - Does not cover logical CI/service-relationship data — see
cmdb-asset-managementfor that. - Does not cover environmental or real-time power-draw monitoring — that would be a separate, read-only/diagnostic-shaped capability, not part of this CRUD-shaped one.
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 API path — belong in that platform's own
references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated client — 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 - That platform's own
procedure.mdwas followed, including its own confirmation gates on destructive changes (asset deletion, rack-unit unassignment affecting a live device) - 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.

