CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sentinel-xdr-solution-deployer

Deploy and verify Sentinel Analytic Rules and Defender XDR Custom Detections disabled in an approved non-production environment.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/sentinel-xdr-solution-deployer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, safety-focused operational policy with genuinely strong approval gates, stop conditions, and verification criteria, plus concrete commands, flags, and paths for the core deployment operations. Its main weaknesses are repetitive consent/approval prose that could be consolidated, a mode-based structure that obscures the end-to-end workflow order, and several named-but-unshown CLI operations. Overall solid, safety-conscious content that would benefit from tightening and a sequential overview.

Suggestions

Consolidate the consent/approval rules stated across "One early scope-consent request", "Package acceptance", and "Safety gates" into a single table (consent type vs. what it authorizes vs. what it does not) to remove repetition and cut tokens.

Add a short ordered overview (consent → preflight → deploy → verify) at the top so the chronology is explicit rather than assembled from mode sections.

Show invocations for named-but-unshown operations (preflight-deployment, the consent-persistence CLI, ARM validation) the way the deploy commands are shown, and consider moving the scope-consent form specification into a reference file.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and almost every sentence encodes project-specific policy ("The current CLI can persist consent for the direct disabled AR/CD pair, fullPackageAcceptance, mockTelemetryIngestion..."), so information density is high. However, the consent/approval gating principles are restated across the scope-consent, package-acceptance, and safety-gates sections, and long stacked-clause sentences like the 12-line broad-scope paragraph could be tightened into lists — matching anchor 3 (mostly efficient but could be tightened) rather than 2, since little content is truly unnecessary.

3 / 5

Actionability

Concrete, executable guidance is present: copy-paste PowerShell commands with parameters, exact output paths ("Solutions\<solution>\Logs\sentinel-xdr-migration\<run-id>\deployment.sentinel.json"), exact package flags ("DeployAnalyticsRule=true"), exact API verbs (PUT/GET/POST/PATCH), and derived ID formats ("xdr-<source-rule-GUID>"). It falls short of 5 because several named operations — preflight-deployment, the consent-persistence CLI, ARM validation/preview invocation — are referenced but never shown with a command, leaving more than minor gaps.

4 / 5

Workflow Clarity

This write/batch-operation skill has strong validation machinery: a 7-item pre-write "Safety gates" checklist, explicit pass criteria and blocked-verification rules in "Verification", and explicit stop conditions ("Stop on unresolved conversion review...", "stop for maintainer review rather than overwriting it"), satisfying the destructive/batch validation requirement well above the cap of 3. It does not reach 5 because the end-to-end sequence (consent → preflight → deploy → verify) is never laid out as an ordered flow — the mode-based sections force the reader to assemble the chronology from scattered statements.

4 / 5

Progressive Disclosure

The single-file skill (no references/, scripts/, or assets/ exist) is organized into clear, well-named sections (## Modes with ### subsections, ## Safety gates, ## Verification), and the one external link (Microsoft Learn on unsupported deployment features) is used appropriately. It scores 4 rather than 5 because at ~193 lines, detailed policy blocks such as the scope-consent form specification and CLI component inventory are inline candidates for a one-level-deep reference file, and the over-50-line simple-skill exception does not apply.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is precise and domain-specific with a clear 'what', but it lacks any explicit 'use when' trigger guidance and offers only two action verbs with no synonyms or natural variations. It is safely distinct from unrelated skills though it brushes against sibling skills in the same suite. Overall a middle-of-the-road description: accurate and concrete, but not optimally discoverable.

Suggestions

Add an explicit trigger clause, e.g. "Use when deploying or verifying Sentinel analytic rules or Defender XDR custom detections in a non-production lab after validation and packaging have passed."

Include natural keyword variations users might say, such as "Microsoft Sentinel", "XDR", "detection rules", or "custom detections", to improve trigger matching.

Briefly enumerate the distinct capabilities (e.g., disabled deployment, idempotent re-deployment, package acceptance, read-back verification) so the 'what' is comprehensive rather than two verbs.

DimensionReasoningScore

Specificity

"Deploy and verify Sentinel Analytic Rules and Defender XDR Custom Detections disabled in an approved non-production environment" names a precise domain and exactly two concrete actions (deploy, verify) plus deployment constraints, matching the 'names domain and 1-2 concrete actions' anchor. It is below 4 because coverage is not comprehensive — no mention of validation, registration, or verification specifics — and above 2 because the actions and target are concrete, not generic.

3 / 5

Completeness

The 'what' is clear (deploy and verify disabled Sentinel AR / XDR CD content in a non-production environment), but there is no 'Use when...' clause or equivalent explicit trigger guidance; "in an approved non-production environment" only weakly implies the when. Per the judging guideline, a missing explicit trigger clause caps completeness at 3, and the clear-what/missing-when profile is exactly anchor 3.

3 / 5

Trigger Term Quality

Terms like "Sentinel Analytic Rules", "Defender XDR Custom Detections", and "deploy" are phrases a user in this domain would naturally say, but coverage stops there — no common variations or synonyms such as "Microsoft Sentinel", "M365 Defender", "detection rules", or "KQL". This matches anchor 3 (relevant keywords, missing variations/synonyms) rather than 4's good-but-nearly-complete coverage.

3 / 5

Distinctiveness Conflict Risk

The product-specific scope (Sentinel Analytic Rules, Defender XDR Custom Detections, disabled, non-production) carves a clear niche with minimal conflict against unrelated skills, fitting above anchor 3. It does not reach 5 because the body reveals closely related sibling skills (e.g., sentinel-xdr-alert-parity-validator, which also handles verification/enablement of the same rule types), creating minor overlap risk with near-identical triggers — the definition of anchor 4.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Azure/Azure-Sentinel

Path

.github/skills/sentinel-xdr-solution-deployer/SKILL.md

Reviewed

Table of Contents

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.