agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/Azure-Sentinel/.github/skills/sentinel-xdr-migration-orchestrator/SKILL.md

sentinel-xdr-migration-orchestrator

Skill6.2k starsChanged 16 days agoMITView on GitHub

Orchestrate conversion of a Microsoft Sentinel solution into Defender XDR Custom Detection YAML by using repository utilities and available runtime providers.

  • Installs packages

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow the canonical workflow's strict over-50% partial-publication policy and single-owner ACTION_REQUIRED watchdog best practice.

    line 12
  2. Distinctive:

    If the package is unavailable, install it from the repository:

    line 30
  3. Very specific:

    If firstRun is true, run sentinel-xdr-migration setup --non-interactive.

    line 37
  4. Distinctive:

    Ask before launching interactive CLI or MCP sign-in.

    line 43
  5. Very specific:

    Use sentinel-xdr-rule-converter.

    line 46
  6. Very specific:

    Use sentinel-xdr-detection-validator.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Migrate a Microsoft Sentinel solution to XDR Detection YAML

The 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.

Scope

This milestone creates and validates XDR Detections/*.yaml.

It does not:

  • generate or modify ARM templates;
  • deploy analytic rules or Custom Detections;
  • generate or ingest mock data;
  • convert workbooks;
  • compare generated alerts.

Workflow

  1. If the package is unavailable, install it from the repository:

    python -m pip install -e Tools\SentinelToXDRMigration
  2. Run sentinel-xdr-migration doctor.
  3. If firstRun is true, run sentinel-xdr-migration setup --non-interactive.
  4. 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.
  5. Ask before launching interactive CLI or MCP sign-in. Continue with offline conversion if authentication is declined or unavailable.
  6. Confirm the solution path.
  7. Use sentinel-xdr-rule-converter; conversion always runs locally and does not depend on MCP.
  8. Review every needsReview result. Never present it as XDR-ready.
  9. 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.
  10. Report:
  • source analytic rules;
  • generated detection files;
  • deterministic rewrites;
  • provenance status;
  • Sentinel and Advanced Hunting execution status;
  • unresolved parity gaps.

An XDR-ready result requires valid YAML, no conversion errors, successful runtime execution on both platforms, and reviewed entity mappings.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 2 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 4 mentionsSep 2026: 6 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Azure/Azure-Sentinel repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about Azure/Azure-Sentinel

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub, Stack Overflow and Bluesky (57 times).

On GitHub · 43

38 more on GitHub

On Stack Overflow · 13

8 more on Stack Overflow

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free