CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

81%

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

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 body is a model orchestrator skill: a clearly sequenced nine-step workflow with explicit validation checkpoints, feedback loops with exit criteria and iteration limits, concrete commands and sub-skill delegation, and a context-passing checklist. Only minor trimming of a few justificatory asides would push conciseness to the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and imperative with well-budgeted sections, but contains a few trimmable asides such as "This prevents authentication failures later in the workflow", "allowing for more flexible and reusable querying", and a one-line definition of what an ASIM parser is, fitting anchor 4 rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

As an instruction-only orchestrator, the guidance is fully concrete: exact command (`az account show`), named sub-skills for each step, concrete testers (`ASimSchemaTester`, `ASimDataTester`), file naming conventions (`ASim<Schema><Vendor><Product>.kql`), explicit exit criteria ("no Error-level `(0)` results"), and a 5-iteration limit — matching anchor 5 for instruction skills.

5 / 5

Workflow Clarity

Nine explicitly sequenced steps with a requirements checklist gating Step 3, dedicated validation steps (4 and 7), an explicit refine→re-validate feedback loop with exit criteria and iteration limit, re-validation of the parameterized parser, and a context-passing table — exactly anchor 5's 'explicit validation steps; feedback loops; checklists'.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: all detail is delegated one level deep to named requiredSkills, nothing that belongs elsewhere is inlined, and the body is a clean, well-sectioned orchestration overview matching anchor 5's 'content appropriately split; easy navigation'.

5 / 5

Total

19

/

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 correctly uses third person and explicitly pairs a 'what' with a 'when', but it undersells the skill's scope: creation and validation are mentioned while deployment and GitHub PR packaging — two of the nine workflow steps — are absent. Trigger coverage is narrow around the single phrase 'ASIM parser'.

Suggestions

List the full capability set in the 'what' clause, e.g. "Orchestrates the creation, validation, refinement, deployment, and GitHub PR packaging of a new ASIM schema parser."

Add natural trigger variations users would say, such as "Microsoft Sentinel", "Sentinel parser", or "KQL function", to improve trigger term coverage.

Broaden the 'when' clause slightly, e.g. "Use when asked to create, build, or set up a new ASIM (Advanced SIEM Information Model) parser for Microsoft Sentinel."

DimensionReasoningScore

Specificity

"Orchestrates the creation and validation of a new ASIM schema parser" names the domain with two concrete actions, but omits major workflow capabilities the skill performs (Log Analytics deployment, GitHub PR packaging), so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

It explicitly answers both questions — what ("Orchestrates the creation and validation of a new ASIM schema parser") and when ("Use this skill when asked to create a new ASIM parser") — but the 'what' is thin (omits deployment/PR packaging) and the trigger is a single phrase, falling short of anchor 5's comprehensive coverage.

4 / 5

Trigger Term Quality

"create a new ASIM parser" is a natural trigger phrase, but the description is missing common variations and synonyms a user would say, such as "Microsoft Sentinel", "Sentinel parser", or "KQL function", matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

ASIM parser creation is a clear niche with distinct triggers, but this orchestrator overlaps with the closely related sub-skills it invokes (e.g. asim-parser-create-parser, asim-parser-validator), giving minor overlap risk consistent with anchor 4.

4 / 5

Total

14

/

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.

Validation — 15 / 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

Path

.github/skills/asim-parser-creator-orchestrator/SKILL.md

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.