CtrlK
BlogDocsLog inGet started
Tessl Logo

asim-parser-pr-reviewer

Reviews pull requests for ASIM parser changes and summarizes suggestions. This is not to be called by asim-parser-creator-orchestrator or when creating ASIM parsers in general. This is strictly for reviewing pull requests after necessary workflows have ran.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/asim-parser-pr-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficiently written, highly actionable review checklist with a clear sequenced workflow and explicit validation/error-recovery guidance. Its main weaknesses are the absence of concrete KQL before/after examples and some formatting inconsistencies in nested lists.

DimensionReasoningScore

Conciseness

The body is lean and directive, assuming KQL/ASIM competence without explaining basics, with only minor repetition of prohibited-pattern framing across the two parser sections, matching 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

It gives a concrete checklist of operators to flag (mv-expand, summarize, project-away) and a fully specified output table format, but lacks example KQL queries showing a violation versus a fix, leaving minor gaps.

4 / 5

Workflow Clarity

Responsibilities are sequenced as a clear numbered list with a validation checkpoint (verify CI/ASim workflows passed) and error-recovery guidance ('If the workflow failed, check the errors or logs'), fitting 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and no external references needed for this self-contained review task, but the flush-left bullet list nested under numbered step 1 and the restarted sub-numbering in the vim section are minor organization gaps.

4 / 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 is distinct and appropriately scoped to a niche task, but its trigger guidance is framed negatively rather than as a positive 'Use when...' clause, and it lists only a couple of concrete actions. Adding an explicit positive trigger and synonyms would raise completeness and trigger-term quality.

Suggestions

Add an explicit positive trigger clause, e.g. 'Use when reviewing pull requests that add or modify ASIM parsers in the Azure-Sentinel repository.'

Include natural synonyms and variants users might say, such as 'PR', 'ASim parsers', or 'parser pull request review', to improve trigger-term coverage.

Briefly enumerate the concrete review actions (e.g. 'verifies CI/ASim validation workflows passed, checks CHANGELOG dates and versions, and reviews KQL query performance') to move specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('ASIM parser changes') and two concrete actions ('Reviews pull requests', 'summarizes suggestions'), but offers no broader coverage of what the review entails, matching the '1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear (reviews and summarizes ASIM parser PRs), but the 'when' is conveyed only via negative exclusions ('not to be called by...') rather than an explicit positive 'Use when...' clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant terms like 'pull requests' and 'ASIM parser', but offers no synonyms ('PR', 'ASim parsers') or a positive trigger clause, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (ASIM parser PR review in Azure-Sentinel) and explicitly disambiguates from asim-parser-creator-orchestrator, giving minimal conflict risk per the 'clear niche with distinct triggers' anchor.

5 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.