asim-parser-user-prompter

Prompts the user for inputs to create a new ASIM schema parser. Use this skill when you need to gather information from the user to create a new ASIM parser.

Quality

66%

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-user-prompter/SKILL.md

Quality

Content

71%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 compact, well-structured interactive requirements-gathering workflow with a real validation feedback loop. Its main gap is underspecified execution detail for the workspace validation query.

Suggestions

Specify the exact query to run for validation (e.g. a sample KQL query like the table name or a 'Get-WorkspaceTable' invocation) and how to invoke the log-analytics-workspace-queryer skill, to make the validation step executable.

Add a brief validation or confirmation checkpoint for Step 4 (e.g. confirm the chosen ASIM schema with the user before declaring the parser scope) to strengthen workflow clarity.

Remove the redundant restating sentence in Step 1 ('The source data type is the type of data that the ASIM parser will be parsing') to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of ASIM/Log Analytics, with only one mildly redundant restatement ('The source data type is the type of data that the ASIM parser will be parsing'), fitting the score-4 anchor of efficient content with minor trims possible.	4 / 5
Actionability	It provides concrete references (the log-analytics-workspace-queryer skill, the schemas URL) but the validation query is underspecified ('the workspace ID and the table name as the query' lacks query syntax), leaving key execution details missing per the score-3 anchor.	3 / 5
Workflow Clarity	A clear 4-step sequence includes an explicit validation checkpoint with a feedback loop in Step 3 ('If the query fails, ask the user to provide the information again'), but Steps 1, 2, and 4 lack checkpoints, fitting score 4 rather than 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is cleanly organized into four well-labeled '## Step' sections, so the simple-skill exception grants a 5 for well-organized structure.	5 / 5
	Total	16 / 20 Passed

Description

62%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 clearly identifies the skill's purpose and includes an explicit 'Use when' clause, with a distinct ASIM-parser niche. Its main weakness is generic trigger phrasing and limited keyword coverage that could be more natural and specific.

Suggestions

Add concrete user-sayable trigger phrases (e.g. 'Use when the user asks to build, create, or generate an ASIM parser, normalize a source into an ASIM schema, or map a Sentinel table to ASIM') to lift completeness and trigger_term_quality.

List the specific inputs gathered (source documentation link, Sentinel table name, Log Analytics workspace GUID, target ASIM schema) in the description to improve specificity and distinctiveness.

Include common synonyms/extensions (e.g. 'ASIM parser', 'Sentinel parser', 'normalization parser') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('ASIM schema parser') and one concrete action ('Prompts the user for inputs to create a new ASIM schema parser'), matching the score-3 anchor of domain plus 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a clear 'what' ('Prompts the user for inputs to create a new ASIM schema parser') and an explicit 'Use this skill when...' clause, but the trigger is somewhat generic rather than concrete user-sayable phrases, so it sits at score 4 rather than 5.	4 / 5
Trigger Term Quality	It includes relevant terms like 'ASIM schema parser' and 'create a new ASIM parser', but leans technical and lacks common variations or synonyms a user would naturally say, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The 'ASIM schema parser' niche within Microsoft Sentinel is mostly distinct with minimal conflict risk, but the generic 'gather information' framing leaves minor overlap with related parser-creation skills, fitting score 4.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Azure/Azure-Sentinel
Path: .github/skills/asim-parser-user-prompter/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.