# Manage UniFi Device Inventory

UniFi teams need clear device status before adopting, tracking, or replacing hardware. This skill helps Claude, Codex, and Claude Code organize inventory and controller health.

## Install

```bash
npx skillstore add dataknifeai/device-management
```

## Metadata

- Status: approved
- Slug: dataknifeai-device-management
- Skillstore revision: r1
- Version status: missing
- Tree hash: 5557d3a459996a41a0e0ce69bd7e1e0b9bc7e31bf660280600295dee54c00b06
- Author: DataKnifeAI
- GitHub username: DataKnifeAI
- License: MIT
- Repository: https://github.com/DataKnifeAI/unifi-network-mcp/tree/main/.github/skills/device-management
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/dataknifeai-device-management
- Manifest: https://skillstore.pages.dev/api/skills/dataknifeai-device-management/manifest

## Capabilities

- Lists UniFi devices that are pending adoption.
- Lists adopted network devices for inventory work.
- Retrieves device specifications, firmware, and status details.
- Checks UniFi controller information and system status.
- Explains how to handle empty UniFi site IDs.
- Supports inventory reports and upgrade planning workflows.

## Use Cases

- Adopt New Network Hardware: Find pending UniFi devices and prepare adoption notes by model, IP address, and planned role.
- Maintain Device Inventory: Create a current inventory grouped by device type, location, firmware version, and operational status.
- Plan Hardware Refreshes: Review device specifications and controller status to prioritize upgrades, replacements, and maintenance windows.

## Prompt Templates

### Show Pending Devices

```
Use device-management to list devices pending adoption. Include MAC address, IP address, model, and recommended next action.
```

### Build Inventory Report

```
List all adopted UniFi devices and group them by type. Include model, firmware, status, and any missing inventory details.
```

### Assess Controller Health

```
Check UniFi controller information and summarize version, uptime, system status, and maintenance concerns.
```

### Plan Lifecycle Actions

```
Review pending devices, adopted devices, device stats, and controller status. Produce a prioritized adoption and upgrade plan with risks.
```

## Limitations

- Requires a configured UniFi MCP server and valid API access.
- The documented tools are mostly read-oriented and do not show a direct adoption command.
- Inventory quality depends on current UniFi controller data.
- Curl examples may need trusted certificate configuration before use.

## Best Practices

- Use scoped UniFi API credentials and avoid sharing keys in prompts or reports.
- Verify site IDs before comparing devices across multiple UniFi sites.
- Document device purpose, location, and owner after every adoption workflow.

## Anti Patterns

- Do not run device discovery against networks you do not administer.
- Do not paste raw API keys, controller URLs, or full device identifiers into shared channels.
- Do not treat inventory output as complete without checking controller sync status.

## Security Audit

- Audited at: 2026-07-05T09:27:09.149\+00:00
- Summary: The external command findings are Markdown formatting false positives, and the API key finding is a placeholder rather than a hardcoded secret. The main security issue is the curl example that disables TLS certificate verification while sending an API key. No prompt injection or malicious intent was found in SKILL.md.

## Stats

- Views: 229
- Downloads: 6
- Favorites: 0
- Popularity score: 0