sentinel-xdr-migration
Orchestrate Sentinel-to-Defender-XDR authoring and optional internal qualification through the repository's canonical workflow and deterministic tools.
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/sentinel-xdr-migration/SKILL.mdSentinel to Defender XDR migration
Read and follow:
Tools\SentinelToXDRMigration\agent-workflows\end-to-end-migration.md
Use sentinel-xdr-migration and the repository PowerShell packaging entry
points for all deterministic actions. Default to authoring; ask before
optional qualification. Use V3.1 through package-v3-1 for Sentinel and XDR
solution packaging, resume workflow-state.json, preserve disabled rules, and
obtain explicit approval before environment writes.
The goal is solution migration and validated publication. Follow the
canonical workflow for the strict over-50% partial-publication policy,
selected-scope Qualification, and the single-owner ACTION_REQUIRED watchdog
best practice; do not create competing policy text or watchdog tooling here.
- Repository
Azure/Azure-Sentinel
- Revision
2985095
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.