CtrlK
BlogDocsLog inGet started
Tessl Logo

asim-parser-github-pr-packager

Packages the created and validated ASIM schema parser into a GitHub PR for the Azure-Sentinel repository. Use this skill when asked to package a parser into a GitHub PR.

64

Quality

75%

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

Fix and improve this skill with Tessl

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

Quality

Content

68%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 highly actionable and reasonably concise, with concrete templates and paths for an 11-step packaging workflow. Its main weaknesses are broken step numbering (missing Step 5, duplicate Step 11) and the absence of explicit validation checkpoints before destructive operations like ARM generation and commit.

Suggestions

Add explicit validation checkpoints for destructive/batch operations — e.g., a verification command after `.script\kqlFuncYaml2Arm.ps1` and a 'verify all files present and tests pass' gate before the final commit.

Fix the step numbering: Step 5 is missing (the flow jumps from Step 4 to Step 6) and two steps are both labeled Step 11 (ARM templates and Commit); renumber sequentially.

Collapse the two near-identical changelog templates (and the two parser YAML templates) into a single parameterized example to reduce repetition and token cost.

DimensionReasoningScore

Conciseness

The body is mostly lean — exact paths, templates, and a naming convention with no padding explaining ASIM or KQL — though the two near-identical changelog templates and repeated YAML blocks could be tightened slightly.

4 / 5

Actionability

Provides executable guidance: concrete directory paths, full YAML/JSON templates, branch naming, and the ARM script command, with only minor gaps such as the conditional Step 8 table check lacking an explicit command.

4 / 5

Workflow Clarity

Steps are clearly sequenced and include a file-presence checklist (Step 10), but a batch/destructive repo operation (modifying unifying parsers, ARM generation, commit) lacks explicit validation checkpoints, and the numbering is broken — Step 5 is missing and Step 11 is duplicated — which the validation-cap guideline pins at 3.

3 / 5

Progressive Disclosure

No bundle files exist and all content is inline in a single well-organized SKILL.md with clear step-based section headers; it is longer than ideal but appropriately sectioned rather than monolithic.

4 / 5

Total

15

/

20

Passed

Description

82%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 specific, distinctive, and explicitly covers both the what and the when with a concrete trigger phrase. Its only weakness is that it states a single packaging action rather than enumerating the full range of sub-tasks the skill performs.

DimensionReasoningScore

Specificity

Names the domain and one concrete action — "Packages the created and validated ASIM schema parser into a GitHub PR for the Azure-Sentinel repository" — but does not enumerate multiple specific actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Explicitly answers both what ("Packages... ASIM schema parser into a GitHub PR") and when ("Use this skill when asked to package a parser into a GitHub PR") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

"package a parser into a GitHub PR" and "Azure-Sentinel" are natural, specific phrases a user would say, giving good keyword coverage, though a few synonyms (e.g., "pull request") are absent.

4 / 5

Distinctiveness Conflict Risk

The ASIM-parser-to-Azure-Sentinel-PR niche is highly specific with distinct triggers, creating minimal conflict risk with other skills.

5 / 5

Total

17

/

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.