UniFi Client Data Integrity
Ensures accurate and resilient UniFi client data retrieval by enforcing validated architectural patterns and fallback logic.
This skill provides domain-specific guidance for developers working on the unifi-mcp monorepo to prevent silent data corruption and handle firmware variances across the UniFi suite. It enforces five critical architectural fixtures—including dual-endpoint fallback, field preservation for user aliases, and uptime-based status derivation—verified against live hardware to ensure high-fidelity client telemetry. By applying this skill, developers can reliably manage the 85-field gap between live and historical endpoints while maintaining cross-layer symmetry between Pydantic models and GraphQL types.
Key Features
01Resilient uptime-based online status derivation for modern firmware
02Cross-layer synchronization between Pydantic models and GraphQL types
03Independent preservation of user-assigned aliases and DHCP hostnames
04Dual-endpoint logic for live vs. historical data synchronization
05Fault-tolerant API fallback chains with priority-based merging
06430 GitHub stars
Use Cases
01Extending client data models in unifi-core to include new telemetry fields
02Refactoring the UniFi GraphQL API layer to ensure data correctness
03Debugging discrepancies between active client lists and historical records