CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-applicationinsights-dotnet

Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management.

51

Quality

56%

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-claude/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md

The canonical home for this skill is azure-mgmt-applicationinsights-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is highly actionable with comprehensive executable examples and good section organization, but it is a long monolithic file that inlines reference material and time-sensitive version info, and its destructive workflows lack validation checkpoints. Splitting reference material into bundle files and adding verification steps would raise the lowest dimensions.

Suggestions

Move large lookup tables (Key Types, Application Types, Web Test Locations, Related SDKs, Reference Links) into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Add explicit validation steps before destructive/batch operations, e.g. confirm a component exists and print its name before DeleteAsync, with a retry-on-failure loop.

Relocate version and API-version details to a clearly labeled 'Current versions' or 'Deprecated/old patterns' section so time-sensitive information does not penalize conciseness.

DimensionReasoningScore

Conciseness

The body is mostly efficient code and tables rather than padded prose, but it runs ~490 lines with ten full workflows and embeds time-sensitive values ('Current Version: v1.0.0', 'API Version: 2022-06-15') outside any deprecated/old-patterns section, which the rubric penalizes.

3 / 5

Actionability

It provides extensive, executable C# examples with concrete commands and specific values covering the common cases (create, get keys, web tests, workbooks, linked storage, list, update, delete), plus install and authentication snippets.

5 / 5

Workflow Clarity

Workflows are presented as clear, discrete recipes with an error-handling section, but destructive and batch operations (Delete Resources, full-PUT Update) lack pre-flight verification or validation checkpoints, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but everything is inlined in a single monolithic file with no bundle files (references/, scripts/, assets/) and no one-level-deep pointers, so large reference tables and the ten workflows that could be split out are not progressively disclosed.

3 / 5

Total

14

/

20

Passed

Description

48%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 is accurate and reasonably specific to its niche but stops at naming the domain and purpose without concrete actions or an explicit use-when trigger. Adding a trigger clause and one or two concrete operations would lift the weakest dimensions.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when managing Application Insights components, web tests, workbooks, or API keys for .NET applications.'

Replace the generic 'resource management' phrasing with concrete actions such as 'create and configure Application Insights components, web tests, and workbooks'.

Include common synonyms users say, such as APM, telemetry, and monitoring, to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Azure Application Insights SDK for .NET') but the only action framing is the generic 'Application performance monitoring and observability resource management', with no concrete operations like create, configure, or query resources.

2 / 5

Completeness

It clearly states what the skill is (an Azure SDK for App Insights resource management) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes several natural terms a user would say ('Azure Application Insights', 'application performance monitoring', 'observability', '.NET') but omits common variations and synonyms such as APM, telemetry, or monitoring alerts.

3 / 5

Distinctiveness Conflict Risk

The '.NET' and 'Azure Application Insights' qualifiers carve a clear niche with low conflict risk, though it could still overlap with the broader Azure Monitor / Log Analytics SDK family.

4 / 5

Total

12

/

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.