CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-applicationinsights-dotnet

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

52

Quality

59%

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-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 complete, executable code examples and clear section structure, but it is monolithic (no bundle-file separation) and its destructive/batch operations lack validation checkpoints. Splitting reference tables and advanced workflows into referenced files and adding verify-before-delete steps would improve the weaker dimensions.

Suggestions

Add explicit validation checkpoints to risky operations: verify a component exists and confirm before DeleteAsync, and validate creation succeeded before proceeding to dependent steps.

Move the large reference tables (Web Test Locations, Application Types, Key Types) and the multi-step web-test/workbook workflows into separate files under references/ and link to them from SKILL.md, keeping the overview lean.

Remove the generic filler 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') and replace it with concrete trigger guidance.

DimensionReasoningScore

Conciseness

The body is mostly executable reference material (code and tables Claude would not already know) rather than padded concept explanation, but it is very long for a SKILL.md and includes filler such as the generic 'When to Use' line, placing it at the score-3 anchor of mostly efficient with some unnecessary content that could be tightened.

3 / 5

Actionability

It provides fully executable, copy-paste-ready C# code across ten workflows covering the common cases (create component, get connection string, API keys, web tests, workbooks, linked storage, list/update/delete, error handling), matching the score-5 anchor.

5 / 5

Workflow Clarity

Workflows are clearly numbered and sequenced, but the destructive delete workflow (section 10) and create/update operations lack explicit validation checkpoints before/after the risky action, so per the rubric's destructive-operation cap workflow clarity is held at 3.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the entire 480-line document — 10 full workflows plus web-test-location, application-type, and key-type tables — is inlined under section headers, so structure exists but content that belongs in separate detail files is not split out, fitting the score-3 anchor.

3 / 5

Total

14

/

20

Passed

Description

53%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 identifies the domain and uses appropriate third-person voice, but it lacks any explicit 'when to use' trigger guidance and only partially enumerates concrete capabilities. Adding a 'Use when...' clause with natural trigger terms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when managing Azure Application Insights resources, configuring availability web tests, or provisioning App Insights components for .NET applications.'

Replace generic phrases like 'observability resource management' with concrete actions such as 'create App Insights components, configure web tests and workbooks, and manage API keys and linked storage.'

Include common synonyms users say ('App Insights', 'telemetry', 'monitoring', 'APM') to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('Azure Application Insights SDK for .NET') and two action areas ('application performance monitoring and observability resource management'), but the actions stay generic and coverage is not comprehensive, matching the score-3 anchor rather than 2 (which has only minimal actions) or 4 (several specific actions).

3 / 5

Completeness

It gives a clear 'what' (the SDK and its APM/observability resource management purpose) but has no 'Use when...' clause or equivalent trigger guidance, so per the rubric's cap a missing explicit trigger clause holds completeness at 3 rather than 4.

3 / 5

Trigger Term Quality

It includes some natural terms a user would say ('Azure Application Insights', '.NET', 'application performance monitoring', 'observability') but misses common variations and synonyms like 'App Insights', 'telemetry', 'monitoring', or 'APM', fitting the score-3 anchor of some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

It targets a specific named Azure resource-management SDK with a distinct niche, with only minor overlap risk against other Azure ResourceManager skills, matching the score-4 anchor; it is not a 5 because 'observability resource management' could still overlap with broader monitoring skills.

4 / 5

Total

13

/

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.