asim-parser-create-parameter-parser

This creates the parameterized version of the ASIM schema parser. You should already have the parameter-less version of the parser to help facilitate the parameter parser creation.

Quality

64%

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-create-parameter-parser/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 content is well-structured, concise, and clearly sequenced with a validation step, and its single-purpose scope keeps progressive disclosure clean. The main weakness is the lack of an executable KQL example for the central 'add parameters' step, which keeps actionability at the middle of the scale.

Suggestions

Add a short, executable KQL snippet showing a parameterized function signature and a where-clause filter applied at the start of the query.

Make the validation step an explicit feedback loop: 'If the query fails, fix the KQL and re-run via the queryer skill until it executes without errors.'

Tighten or remove the sentence explaining why filters improve efficiency, since Claude already understands that rationale.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly instruction, with only minor over-explanation (the sentence justifying why filters improve efficiency) that could be trimmed, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Concrete rules are given (file naming like 'vimNetworkSessionCiscoASA.kql', enumerated prohibited operators like 'mv-expand'/'summarize', doc links, validation via the queryer skill) but the core 'add parameters' step has no executable KQL example, leaving key details missing as in the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	Steps are clearly sequenced via section headers and end with an explicit validation checkpoint (run the KQL via the queryer skill to confirm no syntax errors), with only a minor gap in that no explicit error-recovery feedback loop is described.	4 / 5
Progressive Disclosure	This is a sub-50-line single-purpose skill with no bundle files and well-organized section headers, which per the scoring notes earns a 5 for progressive disclosure with just well-organized sections.	5 / 5
	Total	16 / 20 Passed

Description

57%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 communicates a specific, niche purpose but lacks an explicit 'Use when...' trigger clause and richer natural trigger terms. It is distinct and hard to misfire on, yet stops short of comprehensive action coverage.

Suggestions

Add a 'Use when...' clause stating when to invoke this skill, e.g. 'Use when parameterizing an existing ASIM parser to accept filtering parameters.'

Include a few natural user phrasings or synonyms such as 'add parameters to an ASIM parser' or 'parameterize a Sentinel ASIM parser'.

Expand the action list slightly to signal the core outcomes (e.g., add filter parameters, apply where-clauses, validate execution).

Dimension	Reasoning	Score
Specificity	Names the domain (ASIM schema parser) and one concrete action ('creates the parameterized version') but offers no broader list of actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	The description clearly states what the skill does but contains no 'Use when...' trigger clause (only a prerequisite note), so per the missing-trigger-guidance cap it cannot exceed 3.	3 / 5
Trigger Term Quality	Relevant domain terms ('parameterized version', 'ASIM schema parser', 'parameter parser') are present but there are no synonyms, common phrasings, or file extensions a user might naturally say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	It targets a narrow niche (the parameterized ASIM parser, explicitly distinguished from the parameter-less version) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	14 / 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-create-parameter-parser/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.