Borrowing it
Nothing to install: this file belongs to rcobb2/desktop-management-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rcobb2/desktop-management-mcp/main/.claude/skills/troubleshoot-intune-deployment/SKILL.mdgit clone --depth 1 https://github.com/rcobb2/desktop-management-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rcobb2/desktop-management-mcp/troubleshoot-intune-deployment)<a href="https://agentmods.dev/skills/rcobb2/desktop-management-mcp/troubleshoot-intune-deployment"><img src="https://agentmods.dev/badge/skills/rcobb2/desktop-management-mcp/troubleshoot-intune-deployment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rcobb2/desktop-management-mcp/troubleshoot-intune-deployment"><img src="https://agentmods.dev/badge/skills/rcobb2/desktop-management-mcp/troubleshoot-intune-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.01600 |
| Opus 5 | $0.00029 | $0.00800 |
| Sonnet 5 | $0.00012 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
troubleshoot-intune-deployment scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Intune deployment issues
Route the question to the right tool first — several plausible-looking Graph resources for this are either dead, permission-gated, or empty in practice, and re-discovering that live wastes a turn. Everything below is confirmed against this tenant unless marked otherwise.
Which tool for which question
- "Which devices have an issue with policy X?" →
intune_get_configuration_conflicts(classic device configuration profiles only). It callsdeviceConfigurations/{id}/deviceStatusesdirectly off the policy — this names real devices with no group-membership resolution needed, so it works even without theDevice.Read.AllGraph permission gap below. Confirmed live: named all 7 real devices in error on a real profile, plus surfaced one stale row with an empty device name (fell back to the assigned user's UPN). - "Why does this specific device have an issue?" →
intune_troubleshoot_device_policies(deviceName/serial in, full config+compliance state dump + heuristic issues out) orintune_troubleshoot_policy(one device × one policy, correlates assignment scope with deployment state — catches "device isn't actually in scope" cases the state dump alone won't). - "Why did app X fail to install?" →
intune_get_app_install_status, backed by the Reports API (see dead-end below — do not reach for the obvious-lookingmobileApps/{id}/deviceStatuses). Gives real per-deviceinstallStateDetailfailure reasons (autoInstallDisabled,dependencyFailedToInstall, etc.) plus rawerrorCode, not just a pass/fail count. - "What's this profile actually configured to do, and what's it scoped to?" →
intune_get_configuration_profilefor the payload,intune_get_policy_assignmentsfor scope (readsresolvedTargets, notassignments[].target— see bug note below if extending this). - Settings Catalog policies have none of the above navigation properties — no
deviceStatuses, nodeviceStatusOverview, no conflict summary. The only lever is the Reports API'sgetConfigurationPolicyNonComplianceReportaction, not yet wrapped as a tool here.intune_get_configuration_conflictscorrectly returnssupported: falsefor these rather than a silently-empty result — don't interpret that as "no conflicts."
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 32 lines · 58 tokens per session scan A b67e77b5ae48
troubleshoot-intune-deployment is a skill published in the GitHub repository rcobb2/desktop-management-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 1,600 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.