asim-parser-la-deployer

Gets the ASIM parser of interest and deploys it to the customer's LA workspace.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/asim-parser-la-deployer/SKILL.md

Quality

Content

85%

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

The body is highly actionable with a clear, validated deployment workflow and self-contained organization; its only weakness is a small amount of unnecessary framing prose in the Context section.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and a full ARM template, but the opening Context paragraph ("You are responsible for... ensuring that it is properly configured to work with the customer's environment") is mild framing Claude does not need. Mostly efficient with minor tightening possible, matching anchor 2 rather than the every-token-earns-its-place anchor 3.	2 / 3
Actionability	It gives fully executable az CLI commands (`az account show`, `az monitor log-analytics workspace list`, `az deployment group create`), a complete ARM template JSON, and a copy-paste KQL test query. Matches anchor 3 (fully executable, specific, copy-paste ready) rather than the pseudocode/incomplete anchor 2.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with explicit validation (auth check in Step 1, a test query in Step 5) and an error feedback loop in Step 4 (check error, fix, retry). Matches anchor 3 (clear sequence, explicit validation, feedback loops) rather than the missing-checkpoints anchor 2.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the body is self-contained with well-organized sections (Context, Requirements, Steps 1-5) and no nested references. Per the simple-skill guideline, well-organized sections without external references score 3 rather than anchor 2's poorly-signaled references.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific to a clear niche but only states what the skill does, omitting any 'when to use' trigger guidance and using technical jargon ("LA workspace") over natural user terms.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill, e.g. "Use when the user needs to deploy an ASIM parser to a Log Analytics / Sentinel workspace."

Expand the action list beyond 'Gets' and 'deploys' (e.g., escapes KQL, builds the ARM template, verifies the deployment) to raise specificity.

Replace jargon with natural trigger terms users would say ("Sentinel", "Log Analytics workspace") alongside "ASIM parser" and "LA".

Dimension	Reasoning	Score
Specificity	Names the domain ("ASIM parser", "LA workspace") and the actions "Gets" and "deploys", but only two actions and not comprehensive. It is above the vague anchor 1 ("Helps with documents") but below anchor 3's multiple specific concrete actions.	2 / 3
Completeness	It states what the skill does ("Gets the ASIM parser... and deploys it") but has no "Use when..." trigger or equivalent when-guidance. Per the judging guidelines a missing 'Use when' clause caps completeness at 2, which is above the missing-both anchor 1 but below the explicit both anchor 3.	2 / 3
Trigger Term Quality	"ASIM parser" and "deploys" are reasonable natural terms, but "LA workspace" is technical jargon and common variations ("Sentinel", "Log Analytics", "KQL parser") are missing. Matches anchor 2 (some relevant keywords, missing common variations) rather than the full coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	The ASIM-parser-to-LA-workspace niche is narrow and Sentinel-specific, so it is clearly distinguishable and unlikely to trigger the wrong skill. Matches anchor 3 (clear niche, unlikely to conflict) rather than the overlapping anchor 2.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Azure/Azure-Sentinel
Path: .github/skills/asim-parser-la-deployer/SKILL.md
Commit: fd26ba7

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.