device-compliance

Correlate Intune compliance and NinjaOne patch data to detect policy failures.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill device-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: device-compliance
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/chelsea-piers-itops/skills/device-compliance
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill device-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Device compliance checks are hard to perform consistently across Intune (MDM) and NinjaOne (RMM), so non-compliant or critically unpatched endpoints can slip through audits and day-to-day risk reviews.

Core Features & Use Cases

  • Cross-source compliance visibility: correlates Intune compliance state with NinjaOne patch posture to surface devices that pass one view but still pose risk.
  • Non-compliant device reporting: identifies failing policies and suggests remediations tailored to common compliance controls (OS version, BitLocker, Defender, firewall, jailbreak/rooting, Entra join, screen lock).
  • Patch gap assessment: classifies critical missing patches and flags stale reboot states to prioritize remediation work.
  • Use case: prepare for a security audit by generating a single compliance report for a specific user, specific device, or org-wide scope before you file findings.

Quick Start

Run /device-compliance all to produce an org-wide compliance and patch-gap report for the current date.

Frequently Asked Questions about device-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check endpoint compliance across Intune and NinjaOne?

To check endpoint compliance, the system queries Intune compliance states and NinjaOne patch posture, then correlates the results. This process identifies failing policies and critical patch gaps, mapping them to recommended remediation actions for security audits and risk triage.

How do I find non-compliant devices and missing patches for a security audit?

Finding non-compliant devices involves querying MDM and RMM sources to detect policy failures and classify missing critical patches. The system generates a structured compliance report mapping failing controls—like BitLocker, Defender, or firewall states—to recommended remediation actions for audit preparation.

Do I need both Intune and NinjaOne connectors to assess device compliance?

You need connected MDM (Intune) and/or RMM (NinjaOne) connectors to assess device compliance. The system queries these platforms to correlate compliance states and patch postures, producing a structured report even if only one data source is available.

What endpoint security policies does a device compliance check cover?

A device compliance check covers common security controls including OS version, BitLocker, Defender, firewall, jailbreak or rooting status, Entra join, and screen lock. It correlates these policy states with patch posture to identify failing controls and suggest tailored remediations.

How do I identify stale reboot states and critical patch gaps for remediation triage?

Identifying stale reboots and patch gaps requires querying NinjaOne patch posture to classify missing critical updates. The system flags devices with pending reboots and maps the patch gaps to recommended actions, prioritizing remediation work for flagged users or endpoints.