CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asim-parser-la-deployer

Gets the ASIM parser of interest and deploys it to the customer's LA workspace.

Quality

76%

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-la-deployer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

This is a strong, highly actionable skill body: concrete executable commands at every step, an explicit failure-recovery loop, and a final verification step. Its only weaknesses are mild redundancy in the opening sections and the inlining of the large ARM template that could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is largely efficient — escaping rules, concrete commands, and the ARM template all earn their tokens — but the Context and Requirements intro paragraphs ("You are responsible for deploying... You will use the az cli to deploy...") restate the description and could be trimmed. This matches 'efficient with minor instances of over-explanation' rather than the lean 5.

4 / 5

Actionability

Every step ships copy-paste-ready commands: `az account show`, the full `az monitor log-analytics workspace list` JMESPath query, `az deployment group create` with parameter placeholders, a complete ARM template, and the KQL test query `<FunctionAlias>() | take 10`. The placeholders (e.g., "<escaped KQL query>") are inherent parameterization that the skill explicitly explains how to fill, not gaps.

5 / 5

Workflow Clarity

A clear five-step sequence (auth verification → workspace lookup → template setup → deploy → test) with explicit validation and feedback loops: Step 1 validates authentication, Step 4 prescribes check-error → fix → retry on deployment failure, and Step 5 verifies each parser with a stated success criterion ("If the query returns results, the deployment was successful").

5 / 5

Progressive Disclosure

The body is well-organized into clearly signaled sections with no nested references (no bundle files exist at all), but the ~50-line ARM template example is inlined where it could live in a references/ file, and the skill exceeds the ~50-line simple-skill threshold where section organization alone would justify a 5.

4 / 5

Total

18

/

20

Passed

Description

53%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 to its niche but reads as an internal capability label rather than a trigger-optimized skill description. Its main weakness is the complete absence of 'when to use' guidance, which both caps completeness and limits its trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user or orchestrator asks to deploy or publish an ASIM parser to a Microsoft Sentinel / Log Analytics workspace.'

Replace the vague 'Gets the ASIM parser of interest' with concrete actions such as 'Deploys parameter-less and parameterized ASIM parser functions as saved searches via an ARM template and verifies them with a test query.'

Spell out abbreviations and add natural synonyms users would say: 'ASIM parser', 'Microsoft Sentinel', 'Log Analytics workspace' instead of only 'LA workspace'.

DimensionReasoningScore

Specificity

The description names the domain plus two actions ("Gets the ASIM parser" and "deploys it to the customer's LA workspace"), but "gets" is generic and coverage of the deployment workflow is not comprehensive. It matches the anchor for 1-2 concrete actions without full coverage, not the several specific actions of a 4.

3 / 5

Completeness

It clearly answers 'what' (gets and deploys an ASIM parser to an LA workspace) but contains no 'Use when...' clause or any trigger guidance, which caps completeness at 3. It is not a 4 because the 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("ASIM parser", "deploy", "LA workspace") but they are jargon-heavy and missing common variations and synonyms users would naturally say (e.g., "Microsoft Sentinel", "Log Analytics workspace" spelled out). This matches the 'some relevant keywords but missing variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"ASIM parser" and "LA workspace" carve out a fairly distinct Sentinel deployment niche, with only minor overlap risk against closely related skills (e.g., a sibling parser-creation skill). It falls short of a 5 because there are no distinct trigger phrases that would reliably disambiguate it from those related skills.

4 / 5

Total

13

/

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-la-deployer/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.