CtrlK
BlogDocsLog inGet started
Tessl Logo

asim-parser-creator-orchestrator

Orchestrates the creation and validation of a new ASIM schema parser. Use this skill when asked to create a new ASIM parser.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplar orchestration skill: concise, fully actionable, with a clearly sequenced workflow and robust validation/refinement feedback loops, and clean self-contained structure.

DimensionReasoningScore

Conciseness

Lean and efficient: each step is a tight, purposeful instruction that assumes Claude's knowledge of KQL and ASIM, with no padded concept explanations or filler.

5 / 5

Actionability

Concrete, executable guidance throughout — named skills per step, concrete file names (ASim<Schema><Vendor><Product>.kql), and specific commands (az account show, ASimSchemaTester, ASimDataTester) — copy-ready for the orchestrator role.

5 / 5

Workflow Clarity

A clearly sequenced 9-step workflow with explicit validation checkpoints, a refinement feedback loop with exit criteria, iteration limits, and gated progression before each phase.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no external bundle files; as a self-contained orchestrator skill it needs no separate reference files, and navigation is straightforward.

5 / 5

Total

20

/

20

Passed

Description

66%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 its specialized niche and answers both what and when, but it is more concise than comprehensive — it lists only two of the workflow's actions and offers a single trigger phrasing.

Suggestions

Broaden the action list to reflect the full workflow (e.g., "creates, validates, refines, parameterizes, and deploys ASIM parsers"), which would lift specificity.

Add a few natural trigger variations or synonyms ("Sentinel ASIM parser", "KQL ASIM parser") so the description fires on a wider range of user phrasings.

Make the "when" clause more concrete, e.g. "Use when asked to create, generate, or build a new ASIM parser for Microsoft Sentinel."

DimensionReasoningScore

Specificity

Names the domain ("ASIM schema parser") and two concrete actions ("creation and validation"), but the action coverage is not comprehensive — it omits refinement, parameterization, filtering, and deployment which the body actually performs.

3 / 5

Completeness

Explicitly answers both "what" (orchestrates creation and validation of an ASIM schema parser) and "when" (use when asked to create a new ASIM parser); the "when" is present and clear but could be more specific about the situations that call for it.

4 / 5

Trigger Term Quality

Includes the natural trigger phrase "Use this skill when asked to create a new ASIM parser", but misses common variations and synonyms (Sentinel parser, KQL parser, parser schema) and any file extensions; only one trigger phrasing is present.

3 / 5

Distinctiveness Conflict Risk

"ASIM schema parser" is a clear, specialized niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Azure/Azure-Sentinel
Reviewed

Table of Contents

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.