CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asim-parser-user-prompter

Prompts the user for inputs to create a new ASIM schema parser. Use this skill when you need to gather information from the user to create a new ASIM parser.

Quality

73%

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-user-prompter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, well-organized requirements-gathering workflow with a real validation feedback loop, but the steps tell Claude what to ask without showing how — no example prompts, query shapes, or schema-selection criteria.

Suggestions

Add a concrete example of the validation query invocation, e.g. the workspace ID format and a sample table lookup passed to the 'log-analytics-workspace-queryer' skill.

Provide one or two example questions per step so the requested inputs (documentation link, table name, workspace GUID) are unambiguous.

Give brief selection criteria or examples for mapping source data types to ASIM schemas (e.g., 'network flow logs -> ASimNetworkSessionLogs') instead of only linking to the schema overview.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, but minor padding could be trimmed, e.g. the tautological 'The source data type is the type of data that the ASIM parser will be parsing' and 'This workspace ID is a GUID'.

4 / 5

Actionability

Each step states what information to request, but guidance is incomplete: no example question phrasing, no example KQL or parameter shape for the workspace validation query, and no criteria for choosing among ASIM schemas. This sits between minimal concrete guidance (2) and mostly executable guidance (4).

3 / 5

Workflow Clarity

A clear four-step sequence with an explicit validation feedback loop ('If the query fails, ask the user to provide the information again'), but the schema-mapping step has no verification checkpoint and there is no guidance on what happens after the schema is identified. This matches the 4 anchor rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files; content is appropriately split into well-organized sections and the one external link (ASIM schema reference) is clearly signaled, so no separate files are needed.

5 / 5

Total

16

/

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.

A concise, third-person description with an explicit use-when clause and a clear niche, but it does not enumerate the specific inputs gathered and relies on niche jargon without natural trigger variations.

Suggestions

List the concrete inputs gathered (e.g., source documentation link, Sentinel table name, workspace ID) instead of the generic 'prompts the user for inputs'.

Add natural trigger phrases users would say, such as 'Use when the user asks to create, build, or set up an ASIM parser in Microsoft Sentinel'.

Clarify the boundary with related skills, e.g., note that this skill gathers requirements while a separate skill generates the parser KQL.

DimensionReasoningScore

Specificity

Names the domain ('ASIM schema parser') and one concrete action ('Prompts the user for inputs'), matching the anchor for domain plus 1-2 actions without broader coverage of what the gathering involves.

3 / 5

Completeness

Both 'what' ('Prompts the user for inputs to create a new ASIM schema parser') and an explicit 'Use this skill when...' clause are present, but the 'when' merely restates the 'what' rather than adding concrete trigger phrases, so it does not reach the 5 anchor.

4 / 5

Trigger Term Quality

Terms like 'ASIM', 'parser', and 'gather information' are relevant but only niche jargon; common variations or synonyms a user might naturally say are missing.

3 / 5

Distinctiveness Conflict Risk

The ASIM parser niche is clear and unlikely to fire for unrelated skills; only minor overlap risk with a hypothetical sibling skill that actually creates the parser. Mostly distinct with minor overlap risk matches the 4 anchor.

4 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Azure/Azure-Sentinel

Path

.github/skills/asim-parser-user-prompter/SKILL.md

Revision

2985095

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill