Kql Validator Agent Skill
Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions. Use when the user wants to validate KQL syntax, check semantic alignment with recommendations, verify property names against Azure REST API schemas, or audit KQL queries before a pull request. WHEN: "validate kql", "check kql files", "kql syntax error", "validate aks kql", "run kql validator", "validate azure resource graph queries", "check recommendations alignment", "validate kql for <service>".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Azure/azqr --skill kql-validatorWhat comes with it
28 502 bytes besides the instructionWhat it tells the agent to use
found in the instruction textThe instruction itself
7 sections, as written by the authorKQL Validator Skill
This skill validates KQL query files in Azure Quick Review by delegating to the KQLValidator subagent. The subagent handles the full validation pipeline — discovery, structural/semantic/schema checks, and report generation.
What the subagent validates
- Syntax: Correct KQL grammar, type casts, projection clauses
- Semantic alignment: Query finds violations (not compliance),
recommendationIdmatchesaprlGuid - Schema validity: Property references exist in Azure REST API specs (GitHub lookup, best-effort)
- 100% coverage: Never samples — validates every file in scope
How to invoke
Step 1: Determine scope from the user's request
Parse what the user wants to validate:
| User says | Scope argument to pass |
|-----------|----------------------|
| "validate all KQL" / no specific target | *(empty — validate everything)* |
| "validate ContainerService" / "validate AKS" | Service name, e.g. ContainerService |
| "validate aks-004.kql" | Filename, e.g. aks-004.kql |
| "validate internal/graph/azqr/azure-resources/Sql/" | Directory path |
Step 2: Launch the KQLValidator subagent
Spawn the subagent using the agent file at .agents/skills/kql-validator/agents/kql-validator.md. Pass the scope as the user argument.
Subagent prompt template:
Read and follow the instructions in .agents/skills/kql-validator/agents/kql-validator.md exactly.
User argument: <SCOPE_ARGUMENT_OR_EMPTY>
Workspace: /home/cmendibl3/_dev/azqr
The subagent is self-contained — it will discover files, validate them, and generate a full markdown report. Do not attempt to re-implement its logic inline.
Step 3: Surface results to the user
Once the subagent completes, present its markdown report directly. If the subagent encountered issues, highlight the critical ones and suggest fixes.
Important notes
- The subagent uses GitHub to look up Azure REST API schemas. If GitHub is unavailable, it continues with structural and semantic validation only and notes the limitation.
- For large scopes (all services), the run may take several minutes. Let the user know and launch the subagent in background mode.
- For focused scopes (single service or file), sync mode is fine.
Other skills for the same job
different authors, same section of the catalogue
This skill should be used as a mandatory final sanity check before git commit, PR creation, or declaring work done. Triggers on "commit", "push", "PR", "pull request", "done", "finished", "complete", "ship", "deploy", "ready to merge". Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.
Audits code against CI/CD style rules, quality guidelines, and best practices, then rewrites code to meet standards without breaking functionality. Use this skill after functionality validation to ensure code is not just correct but also maintainable, readable, and production-ready. The skill applies linting rules, enforces naming conventions, improves code organization, and refactors for clarity while preserving all behavioral correctness verified by functionality audits.
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
CI/CD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request/BRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.
>- Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and CI/CD integration of SARIF data. Does NOT run scans — use the Semgrep or CodeQL skills for that.
Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events). Use when the user asks to validate, review, or check domain models or DDD code; detect anemia; refactor domain objects; improve encapsulation; or mentions terms like "anemic model", "rich domain", "aggregate", "value object", "domain event", "ubiquitous language", "is this good DDD", "does this follow DDD", or "check my domain". Do NOT use for module or service boundary design, architectural decomposition, strategic DDD context mapping, or code outside the domain layer (DTOs, controllers, infrastructure adapters).
End-to-end iOS red-team pipeline — IPA acquisition (App Store extraction, TestFlight, enterprise/ad-hoc sideload), class-dump/Hopper/Ghidra static analysis, Info.plist + entitlements + Keychain secret extraction, App Transport Security (ATS) misconfig + certificate-pinning bypass (frida-ios-dump, objection, SSL Kill Switch 2), URL-scheme / Universal Link hijack, exported-service enumeration, Frida runtime instrumentation. Companion to apk-redteam-pipeline for the iOS side of a mobile app catalogue. Use when target has an iOS app (App Store listing, TestFlight link, enterprise MDM distribution), when an IPA URL is found hosted on a web server, or when post-recon mentions "iOS app" / "mobile app" in scope alongside an Apple developer account.
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
How to use it
Take azure/kql-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.