azure-resource-manager-redis-dotnet

Azure Resource Manager SDK for Redis in .NET.

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-resource-manager-redis-dotnet/SKILL.md

Quality

Content

61%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides highly actionable, executable C# code covering the full Azure Redis management SDK surface area, which is its primary strength. However, it suffers from being overly long and monolithic—reference tables and advanced workflows should be split into separate files. Critical gaps include missing validation/verification steps for destructive operations like cache deletion, force reboot, and data import/export.

Suggestions

Add explicit validation and confirmation steps for destructive operations (Delete, ForceReboot, Import/Export) — e.g., verify cache state before deletion, check provisioning state after import.

Extract SKU reference tables, Key Types Reference, and Related SDKs into a separate REFERENCE.md file, keeping only the most essential info inline.

Remove or condense content Claude already knows: the 'Best Practices' list could be trimmed to items specific to this SDK rather than general security advice.

Add a verification step after cache creation that checks ProvisioningState before proceeding to data plane operations.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~300 lines) with some unnecessary content. The SKU reference tables, Related SDKs table, and 'When to Use' section add bulk. The 'Best Practices' list includes items Claude would already know (e.g., 'never hardcode keys'). The management vs data plane callout at the top is somewhat useful but borderline. However, the code examples themselves are reasonably tight.	3 / 5
Actionability	Excellent actionability with fully executable, copy-paste ready C# code for all major operations: create, read, update, delete, firewall rules, patch schedules, import/export, key management, and error handling. The code includes proper using statements, realistic parameters, and covers the complete lifecycle.	5 / 5
Workflow Clarity	The workflows are presented as numbered sections but lack validation checkpoints. Destructive operations like Delete (section 4), Force Reboot (section 10), and Import/Export (section 9) have no confirmation or validation steps. The Import/Export workflow doesn't verify success. Per rubric rules, missing validation for destructive/batch operations caps this at 3.	3 / 5
Progressive Disclosure	All content is inlined in a single monolithic file with no references to supporting files. The SKU reference tables, key types reference, and detailed code examples for 10+ workflows could be split into separate reference files. For a skill this long, the lack of any file decomposition is a notable weakness.	2 / 5
	Total	13 / 20 Passed

Description

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

This description is essentially a technology label rather than a functional skill description. It names the domain (Azure Resource Manager SDK for Redis in .NET) but fails to describe any concrete actions the skill performs or when it should be selected. Without a 'what it does' or 'when to use it' clause, Claude would struggle to reliably choose this skill from a list of alternatives.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Creates, configures, and manages Azure Cache for Redis instances using the Azure Resource Manager .NET SDK.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user needs to provision, update, or delete Redis cache resources in Azure using .NET, or mentions Azure.ResourceManager.Redis.'

Include natural synonyms and variations such as 'Azure Cache for Redis', 'ARM SDK', 'Redis cache management', and relevant NuGet package names to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure Resource Manager SDK for Redis in .NET) but provides no concrete actions—no verbs describing what the skill actually does (e.g., create, configure, manage cache instances).	2 / 5
Completeness	There is no 'what does this do' beyond naming the technology stack, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing.	1 / 5
Trigger Term Quality	Includes relevant keywords like 'Azure', 'Redis', '.NET', and 'Resource Manager SDK', which are terms a user might mention. However, it misses natural synonyms and variations like 'Azure Cache for Redis', 'ARM', 'cache management', or 'NuGet package'.	3 / 5
Distinctiveness Conflict Risk	The combination of Azure, Redis, Resource Manager SDK, and .NET is somewhat specific, but without concrete actions it could overlap with other Azure SDK skills or Redis-related skills. The niche is identifiable but not sharply delineated.	3 / 5
	Total	9 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-resource-manager-redis-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 19 hours ago

Table of Contents

Discovery Implementation Validation

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.