# Track UniFi Deployment Status

UniFi teams need a clear view of active deployments, configuration changes, and progress. This skill helps Claude, Codex, and Claude Code collect status and guide deployment reviews.

## Install

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

## Metadata

- Status: approved
- Slug: dataknifeai-deployment-management
- Skillstore revision: r1
- Version status: missing
- Tree hash: 40b1853af9d9a0d3f64571faee0d134d6a387f2f3b57d813d4c43e3890ce6f59
- Author: DataKnifeAI
- GitHub username: DataKnifeAI
- License: MIT
- Repository: https://github.com/DataKnifeAI/unifi-manager-mcp/tree/main/.github/skills/deployment-management
- Ref: 34f316ba14ef36c7a620fc09f2676d2429997a77
- 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
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dataknifeai-deployment-management
- Manifest: https://skillstore.pages.dev/api/skills/dataknifeai-deployment-management/manifest

## Capabilities

- List active deployments across UniFi sites.
- Retrieve detailed information for a specific deployment.
- Monitor deployment status, progress, and health.
- Track deployment configuration and change history.
- Analyze deployment metrics for operational review.
- Generate deployment status and history reports.

## Use Cases

- Monitor Active Rollouts: Review current UniFi deployments, progress, and health before an operations check-in.
- Plan Maintenance Windows: Understand current deployment load before scheduling infrastructure updates across sites.
- Document Change History: Summarize deployment changes, status, and configuration details for audit records.

## Prompt Templates

### Show Current Deployments

```
Show all active UniFi deployments and summarize current status, progress, and affected sites.
```

### Review One Deployment

```
Get details for the selected deployment and explain its status, configuration, health, and next expected step.
```

### Prepare Change Summary

```
Create a deployment report that lists recent changes, current progress, health concerns, and items needing follow-up.
```

### Assess Rollout Risk

```
Compare active deployments, identify stalled or failed work, assess operational impact, and prepare handoff notes with rollback considerations.
```

## Limitations

- It depends on available deployment data and tool permissions.
- It does not create, approve, or roll back deployments.
- It cannot guarantee real-time status if source data is stale.
- It does not replace production change control procedures.

## Best Practices

- Review deployment status before and after each maintenance window.
- Document configuration changes and affected sites during every rollout.
- Confirm rollback plans before coordinating multi-site deployments.

## Anti Patterns

- Do not use stale deployment data for production decisions.
- Do not skip normal approval steps because a status report looks healthy.
- Do not treat monitoring output as a replacement for deployment logs.

## Security Audit

- Audited at: 2026-07-06T10:18:43.387\+00:00
- Summary: The static external-command findings are false positives caused by Markdown inline code that names available tools. The network reconnaissance findings are false positives from benign deployment monitoring language in SKILL.md. No prompt injection, data exfiltration intent, or malicious semantic behavior was found.

## Stats

- Views: 218
- Downloads: 8
- Favorites: 0
- Popularity score: 0