Validates ASIM parser filtering parameters by running filter tests against a Log Analytics workspace. Pure PowerShell using az CLI for authentication — no Python or Azure SDK packages required. Use this skill after creating or modifying an ASIM parser to verify that its filtering parameters work correctly.
npx skills add https://github.com/Azure/Azure-Sentinel --skill asim-parser-filter-validator
Validates that an ASIM parser's filtering parameters (e.g. disabled, starttime, endtime, srcipaddr_has_any_prefix, etc.) behave correctly by running queries against a Log Analytics workspace.
This skill is a pure PowerShell implementation that uses az CLI for authentication. No Python, Azure SDK packages, or YAML modules are required.
az login)For every filtering parameter declared in the parser's KQL function signature:
| Parameter type | Tests performed |
| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| disabled | disabled=true returns 0 rows; disabled=false returns rows |
| datetime (starttime / endtime) | Filtering by the midpoint timestamp returns fewer rows than unfiltered |
| Scalar (string, int) | Filtering by a real value returns exactly that value; filtering by a fictitious value returns 0 rows |
| dynamic (*_has_any, *_has_all, *_has_any_prefix) | Filtering by one/two real values returns fewer rows; fictitious value returns 0 rows; substring / prefix variants tested where applicable |
AgentEvent, AlertEvent, AssetEntity, AuditEvent, Authentication, DhcpEvent, Dns, FileEvent, NetworkSession, ProcessEvent, RegistryEvent, UserManagement, WebSession.
| Input | Required | Description |
| --------------- | -------- | ----------------------------------------------------------------- |
| Parser KQL path | Yes | Path to the ASIM parser .kql file to test |
| Schema name | Yes | ASIM schema name (e.g. Dns, Authentication, NetworkSession) |
| Workspace ID | Yes | Log Analytics workspace GUID to run queries against |
.\scripts\asimFilterTest.ps1 -ParserFile "{PathToFilterParserKQL}" -SchemaName "{SchemaName}" -WorkspaceId "{your-workspace-guid}"
az login if not already logged in. If you get an authentication error, use the az-cli-command-runner skill to verify login status.EventResult), Authentication (EventType), and Dns (EventType) have known single-failure scenarios that are automatically ignored.When analyzing filter-validation failures, a failure can be ignored if it matches one of these inherent-limitation categories:
When reviewing filter-validation output, analyze each failure message against these categories. If all other parameters pass and every failure maps to one of the reasons above, the parser's filtering implementation is considered correct.
| Symptom | Fix |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Failed to acquire access token via az CLI | Run az login |
| No data in the provided workspace | Ensure the workspace has ingested data for the relevant tables within the last 2 days |
| Schema: X - Not supported | The schema name is not in the supported list — update the $AllSchemasParameters hashtable in asimFilterTest.ps1 |
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take azure/asim-parser-filter-validator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.