Orchestrate conversion of a Microsoft Sentinel solution into Defender XDR Custom Detection YAML by using repository utilities and available runtime providers.
78%
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 ./.github/skills/sentinel-xdr-migration-orchestrator/SKILL.mdThe goal is to migrate the solution and support publishing validated content.
Follow the canonical workflow's strict over-50% partial-publication policy and
single-owner ACTION_REQUIRED watchdog best practice; do not reproduce those
policies here.
This milestone creates and validates XDR Detections/*.yaml.
It does not:
If the package is unavailable, install it from the repository:
python -m pip install -e Tools\SentinelToXDRMigrationRun sentinel-xdr-migration doctor.
If firstRun is true, run
sentinel-xdr-migration setup --non-interactive.
Inspect the official Triage MCP capabilities. Prefer its advertised tools
for every supported runtime query operation, including
RunAdvancedHuntingQuery. This check is separate from doctor, because MCP
authentication belongs to the agent host rather than the Python CLI.
Ask before launching interactive CLI or MCP sign-in. Continue with offline conversion if authentication is declined or unavailable.
Confirm the solution path.
Use sentinel-xdr-rule-converter; conversion always runs locally and does
not depend on MCP.
Review every needsReview result. Never present it as XDR-ready.
Use sentinel-xdr-detection-validator. Prefer Triage MCP for supported
original Sentinel and Advanced Hunting queries. Fall back to Log Analytics
CLI/API for Sentinel queries and the Graph CLI for Advanced Hunting only
when the MCP lacks the capability or has a provider-level failure, never
for genuine KQL failures.
Report:
An XDR-ready result requires valid YAML, no conversion errors, successful runtime execution on both platforms, and reviewed entity mappings.
Azure/Azure-Sentinel
2985095
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.