asim-parser-la-deployer

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

Quality

69%

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

92%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 content is a tight, fully executable deployment workflow with concrete CLI commands, a complete ARM template, explicit escaping rules, an error-recovery loop, and a verification step. It is well-structured for a single-purpose skill with no unnecessary reference indirection.

Dimension	Reasoning	Score
Conciseness	The body is efficient with no conceptual padding and assumes Claude's competence, providing only deployment-specific detail. It is not a 5 because the full inline ARM template is sizable, though it earns its place as a complete example.	4 / 5
Actionability	Fully executable, copy-paste-ready commands ('az account show', 'az monitor log-analytics workspace list ...', 'az deployment group create ...') plus a complete ARM template and a verification query cover the common cases. Necessary parameter placeholders do not reduce executability.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints (Step 1 auth check, Step 5 test query) and a feedback loop in Step 4 (check error, fix, retry). The destructive/batch deployment has validation, so it is not capped at 3.	5 / 5
Progressive Disclosure	A single, well-organized SKILL.md under 130 lines with no need for external references; section headers are clear and there are no nested references. Per the simple-skill guidance this is a 5.	5 / 5
	Total	19 / 20 Passed

Description

46%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 states a clear, specific purpose but omits any 'when to use' trigger guidance and relies on technical jargon rather than natural user keywords. It is distinguishable from sibling skills but would be strengthened by an explicit use-when clause.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when deploying an ASIM parser to a customer Log Analytics workspace') to raise completeness and trigger-term quality.

Include natural user-facing synonyms alongside jargon (e.g., 'Log Analytics workspace' instead of only 'LA workspace', and 'Sentinel ASIM parser') so users' phrasings match.

Consider mentioning the paired parameter-less and parameterized parser files in the description to broaden specificity and coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('Gets the ASIM parser', 'deploys it to the customer's LA workspace'), but coverage is not comprehensive. It sits at anchor 3 rather than 4 because it lists only 1-2 actions, and above 2 because the actions are concrete rather than minimal/generic.	3 / 5
Completeness	There is a clear 'what' (get and deploy the parser) but no 'when' or 'Use when' trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because no explicit trigger clause is present.	3 / 5
Trigger Term Quality	Keywords are technical jargon ('ASIM parser', 'LA workspace') with no natural user phrasing or synonyms. It is slightly above the pure-jargon floor (1) because it does name the domain, but it misses the natural phrases users would say.	2 / 5
Distinctiveness Conflict Risk	The niche (ASIM parser -> LA workspace deployment) is specific with low overlap risk against other skills. Not 5 because it lacks distinct trigger phrasing that would make selection unambiguous.	4 / 5
	Total	12 / 20 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: ba5ab1c

Reviewed: 1 day 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.