CtrlK
BlogDocsLog inGet started
Tessl Logo

log-analytics-workspace-queryer

Uses REST API to query Log Analytics workspaces. Use this skill when you need to query a Log Analytics workspace, for example, to check if the table exists in the workspace, or to validate an ASIM parser.

64

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/log-analytics-workspace-queryer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 clean, well-structured simple skill that points to a real script and gives an executable command, with minor gaps around error handling and worked examples.

Suggestions

Add a short note on failure handling, e.g. what the script emits on a non-200 response and how the caller should interpret it.

Include one worked example with representative (non-sensitive) parameter values to make the command immediately runnable as a sanity check.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence; the only mildly trimmable line is "This information should come from another skill and you do not need to ask the user for it", which is still useful procedural guidance.

4 / 5

Actionability

It gives a concrete, copy-paste-ready command (`.\scripts\queryLogAnalytics.ps1 -WorkspaceId "<workspaceId>" -Query "<KQL query>"`) with clear parameters, but offers only one form and no worked example with sample values.

4 / 5

Workflow Clarity

Two steps are clearly sequenced (run query, return results) for a read-only operation, but there is no guidance on what to do when the query fails or returns an error payload.

4 / 5

Progressive Disclosure

Well-organized sections (Inputs, Step 1, Step 2) with a single one-level-deep reference to the real bundled file `scripts/queryLogAnalytics.ps1`; nothing is inlined that belongs elsewhere.

5 / 5

Total

17

/

20

Passed

Description

73%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 focused, third-person description that clearly states its niche and provides concrete example triggers, with minor room to broaden trigger-term coverage and de-tautologize the when-clause.

Suggestions

Add common synonyms to the trigger terms, e.g. KQL queries or Azure Monitor logs, so users searching with those terms land on this skill.

Rephrase the 'Use when' clause so the trigger is not a restatement of the capability, e.g. 'Use when validating ASIM parsers, checking table existence, or running KQL diagnostics against a workspace.'

DimensionReasoningScore

Specificity

"Uses REST API to query Log Analytics workspaces" names the domain plus one core action, with two concrete example use cases ("check if the table exists", "validate an ASIM parser"), but coverage is not comprehensive — it is essentially a single query action.

3 / 5

Completeness

It answers both what ("Uses REST API to query Log Analytics workspaces") and when ("Use this skill when you need to query a Log Analytics workspace, for example..."), but the when-clause is somewhat tautological and could be more explicit with varied triggers.

4 / 5

Trigger Term Quality

Natural phrases like "query Log Analytics workspace", "check if the table exists", and "validate an ASIM parser" map well to what a user would say, though common synonyms such as KQL or Azure Monitor logs are absent.

4 / 5

Distinctiveness Conflict Risk

"Log Analytics workspaces" plus REST API querying defines a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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.

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.