CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-monitor-ingestion-py

Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.

64

Quality

78%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-monitor-ingestion-py/SKILL.md

The canonical home for this skill is azure-monitor-ingestion-py in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is actionable and concise with strong executable examples, but it inlines everything into a single file and omits a verification step for the batch ingestion workflow. Adding a log-landing verification checkpoint and splitting advanced examples into references would raise both capped dimensions.

Suggestions

Add an explicit validation checkpoint after upload (e.g., query Log Analytics or check the upload return value) to lift workflow_clarity above the batch-operation cap of 3.

Deduplicate the client-construction snippet between 'Authentication' and 'Upload Custom Logs' to improve conciseness toward 5.

Move advanced material (async client, sovereign clouds) into a references/ file and signal it from the overview to improve progressive_disclosure and reduce inline length.

DimensionReasoningScore

Conciseness

The body is largely lean code-driven sections without explaining concepts Claude already knows, but the client-construction block is duplicated nearly verbatim across 'Authentication' and 'Upload Custom Logs', a minor trim candidate.

4 / 5

Actionability

It provides multiple concrete, mostly copy-paste-ready Python examples (sync upload, JSON file, error callbacks, sovereign clouds), but the async example references undefined outer-scope variables (endpoint, rule_id, logs, stream_name), leaving minor gaps.

4 / 5

Workflow Clarity

The batch-ingestion workflow lists steps and components but lacks an explicit verification checkpoint confirming logs landed in Log Analytics; per the rubric, missing validation for batch operations caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the body references no external files, so all ~200 lines are inline; section headers and tables give structure, but content that could be split (async, sovereign clouds) is inlined with no one-level-deep references signaled.

3 / 5

Total

14

/

20

Passed

Description

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

The description clearly states what the skill does and when to use it within a well-defined niche, though it covers only one concrete action and its trigger phrasing is somewhat technical. Distinctiveness is strong.

Suggestions

Broaden specificity by listing 1-2 more concrete actions the SDK supports (e.g., async upload, partial-failure retry) instead of only 'sending custom logs'.

Add natural user-facing trigger phrasing such as 'Use when sending logs to Azure Log Analytics or ingesting custom log data' to improve trigger_term_quality.

Expand the 'when' clause with concrete trigger conditions (e.g., mentioning custom tables ending in _CL or DCR/DCR setup) to lift completeness toward 5.

DimensionReasoningScore

Specificity

Names the domain ('Azure Monitor Ingestion SDK for Python') and one concrete action ('sending custom logs to Log Analytics workspace via Logs Ingestion API'), matching the anchor for a domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Both 'what' (the SDK sends custom logs via the Logs Ingestion API) and 'when' ('Use for sending custom logs...') are present, though the 'when' clause is singular and could be more explicit.

4 / 5

Trigger Term Quality

It includes relevant domain keywords ('Azure Monitor', 'Log Analytics', 'custom logs', 'Logs Ingestion API', 'Python') but leans technical and misses the natural colloquial variations a user would actually say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear, narrow niche (Azure Monitor Logs Ingestion API for Python) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.