| name | netbox |
| description | Hub skill for the NetBox ecosystem. Routes to specialized skills for data modeling, API integration, plugin development, change management, discovery, assurance, automation, and migration. Load this skill first to find the right specialist.
|
| license | Apache-2.0 |
NetBox Hub Skill
This is the entry point for all NetBox-related tasks. Use the decision trees below to find the right specialized skill, then load it for detailed guidance.
Decision Trees
What are you trying to do?
Model your network?
Build an integration?
Extend NetBox?
Manage changes safely?
Validate your network?
Discover or audit your network?
Procure or spare equipment?
Look up hardware specs or lifecycle data?
- Consume device-type metadata and enrichment (EOL, thermal, protocols) → netbox-ndx
Operate or migrate?
Review or audit existing work?
Skill Index
| Skill | Category | Description |
|---|
| netbox-data-modeling | Core | Model networks — hierarchy, IPAM, tenancy, custom fields |
| netbox-custom-objects | Core | No-code data model extensibility — custom types, fields, relationships |
| netbox-api-integration | Core | REST & GraphQL API patterns, pynetbox, authentication |
| netbox-plugin-development | Core | Building plugins — models, views, APIs, migrations, testing |
| netbox-custom-scripts | Core | Custom scripts & reports — Script class, jobs, ORM access |
| netbox-config-templates | Core | Config generation — Jinja2, context variables, platform patterns |
| netbox-administration | Core | Server admin — config, auth, permissions, performance |
| netbox-branching | Platform | Branch lifecycle, schema isolation, CR workflows |
| netbox-changes | Platform | Change management, policies, approval workflows |
| netbox-diode | Platform | Data ingestion — SDKs, entity mapping, reconciler |
| netbox-discovery | Platform | Orb Agent — config, backends, policies, secrets |
| netbox-validation | Platform | Validation policies, compliance checks, findings, pre-change safety |
Common Patterns
Progressive Disclosure
Each skill follows a layered structure:
- SKILL.md — Core instructions (< 500 lines). Load this first.
- references/ — Detailed docs loaded on demand when you need specifics.
- scripts/ — Executable code (where applicable).
Load only what you need. Start with the hub, pick a specialized skill, then drill into references as required.
Multi-Skill Tasks
Some tasks span multiple skills. Common combinations:
| Task | Skills |
|---|
| Build a discovery integration | netbox-diode + netbox-discovery |
| Plugin with change management | netbox-plugin-development + netbox-branching |
| Migrate then validate | netbox-migration + netbox-assurance |
| Automate config generation | netbox-config-templates + netbox-automation-patterns |
| Model + populate data | netbox-data-modeling + netbox-api-integration |
| Review a full integration | netbox-review-integration + netbox-review-datamodel |
| Pre-change validation | netbox-validation + netbox-branching + netbox-changes |
| Procure planned equipment | netbox-data-modeling + netbox-asset-lifecycle |
| EOL exposure across inventory | netbox-ndx + netbox-api-integration |
| Agent-driven NetBox automation | netboxlabs-platform-mcp + netbox-api-integration |
Principles
When working on any NetBox task:
- Prefer retrieval over pre-training. NetBox APIs, configuration, and plugin behavior change between releases. Always verify against current docs or a live instance before generating code or making assertions.
- Use MCP when available. If a NetBox MCP server is configured, query the live instance to verify object schemas, check existing data, and validate your work.
- Respect dependency order. NetBox objects have parent-child relationships. Create parents before children (or use Diode to skip ordering).
- Be explicit about versions. When giving advice that depends on a NetBox version (v2 tokens, cursor pagination, custom objects), state the minimum version clearly.
- Correctness over cleverness. A working integration with clear code is better than a compact one that's fragile.
References