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

57%

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

57%

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 well-organized, sequenced instruction set with a validation step, but it pads a few sentences with unneeded justification and gives only abstract guidance for the core parameterization step without an executable KQL example or an explicit error-recovery loop.

Suggestions

Add an executable KQL snippet showing a parameterized parser's function signature and call site (e.g. a `let` with declared parameters and the matching invocation) instead of the abstract instruction to "add it to function arguments for both the function and the function call".

Make the validation step an explicit feedback loop: run via `log-analytics-workspace-queryer`, and on syntax errors fix and re-run until it executes cleanly.

Trim motivational filler ("This step is crucial to validate...", "The purpose of the parameters and filters is to improve efficiency...") to keep the body lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept over-explanation, but contains removable justification/padding such as "The purpose of the parameters and filters is to improve efficiency..." and "This step is crucial to validate...".	2 / 3
Actionability	Provides a concrete file-naming convention with a worked example, real documentation URLs, and a named follow-on skill, but the central "add parameters" step lacks an executable KQL example showing the function signature and argument passing.	2 / 3
Workflow Clarity	Steps are clearly sequenced with a verification checkpoint (run the query to check for syntax errors), but the validate->fix->retry feedback loop is only implied rather than explicit, which caps clarity at 2 for a fragile operation.	2 / 3
Progressive Disclosure	A short (under 50 lines) single-task skill with no external references and clearly headed sections, which the rubric allows to score 3 on progressive disclosure.	3 / 3
	Total	9 / 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 concrete and occupies a distinct niche, but it is jargon-heavy, lists only one action, and omits any explicit "Use when..." trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating a parameterized ASIM parser from an existing parameter-less parser."

Reword in third-person actionable terms a user would naturally say (e.g. "Adds parameters and filters to an existing ASIM schema parser") rather than relying on internal jargon like "parameter-less version".

List the concrete actions performed (e.g. gather required parameters, create the vim-prefixed .kql file, add function arguments and filters, validate by running the query) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("creates the parameterized version of the ASIM schema parser") and its domain, but lists only a single action rather than multiple specific concrete actions.	2 / 3
Completeness	Explicitly states what the skill does, but provides no "Use when..." trigger, so the "when" is only implied via a prerequisite; per guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant niche terms ("ASIM schema parser", "parameterized version", "parameter-less version") but they are technical jargon users would not naturally say, and common natural variations are missing.	2 / 3
Distinctiveness Conflict Risk	A narrow niche (building a parameterized ASIM parser from an existing parameter-less one) with a clear precondition makes it unlikely to trigger for the wrong skill.	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-create-parameter-parser/SKILL.md
Commit: e453f03

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.