CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-sequenced with a genuine validate-and-retry loop, but actionability is held back by an undelivered 'how to ask' promise and a schema-mapping step that gives no selection criteria.

Suggestions

Fulfill the intro's 'how to ask for it' claim by adding example prompt phrasings or the specific questions to ask the user in each step.

Add concrete criteria or a short decision guide in Step 4 for mapping a source data type to an ASIM schema, rather than only pointing to the schema URL.

Clarify what to do after the schema is identified (e.g. the hand-off to parser creation) so the workflow has a defined completion point.

DimensionReasoningScore

Conciseness

The body is lean and step-structured with no re-explanation of concepts Claude already knows; each step earns its tokens, fitting the level-3 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete items to collect (documentation link, table name, workspace GUID) and a validation step, but the intro promises guidance on 'how to ask for it' that the steps never deliver, and Step 4's schema-mapping lacks decision criteria, leaving key details incomplete per the level-2 anchor.

2 / 3

Workflow Clarity

Four steps are clearly sequenced and Step 3 includes an explicit validation checkpoint with an error-recovery feedback loop ('If the query fails, ask the user to provide the information again'), matching the level-3 anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into clear Step 1–4 sections, satisfying the simple-skill allowance for level 3.

3 / 3

Total

11

/

12

Passed

Description

75%

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 well-structured with an explicit trigger clause and a distinctive niche, but it only names a single high-level action and offers limited keyword variation, capping specificity and trigger term quality at level 2.

DimensionReasoningScore

Specificity

The phrase 'Prompts the user for inputs to create a new ASIM schema parser' names a clear domain and one action, but does not list multiple specific concrete actions (e.g. it does not enumerate what inputs are gathered), so it matches the level-2 anchor rather than level 3.

2 / 3

Completeness

It states what the skill does ('Prompts the user for inputs to create a new ASIM schema parser') and gives an explicit when-trigger ('Use this skill when you need to gather information from the user to create a new ASIM parser'), satisfying both halves required for level 3.

3 / 3

Trigger Term Quality

Terms like 'ASIM schema parser' and 'gather information from the user' are relevant to the niche, but coverage of natural phrasings a user would say is thin and misses common variations, fitting the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The ASIM schema parser niche is specialized with distinct triggers, making it unlikely to fire for unrelated skills, matching the level-3 anchor for a clear niche.

3 / 3

Total

10

/

12

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.