Name: azure-resource-manager-redis-dotnet
Rating: 52.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-redis-dotnet

Azure Resource Manager SDK for Redis in .NET.

Quality

58%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-resource-manager-redis-dotnet/SKILL.md

The canonical home for this skill is azure-resource-manager-redis-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

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 skill is highly actionable with comprehensive executable examples and clear workflow sequencing, but it is a long monolithic file with no progressive disclosure, and destructive operations lack validation checkpoints.

Suggestions

Add validation/verification before destructive operations (e.g. confirm cache exists and check provisioning state before DeleteAsync/ForceRebootAsync/RegenerateKeyAsync) to lift the workflow clarity cap.

Move the SKU capacity tables and full Key Types Reference into a separate reference file and link to it from SKILL.md to improve progressive disclosure and conciseness.

Replace the generic "When to Use" placeholder with a concrete trigger statement, and trim the duplicated StackExchange.Redis connection guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly code and reference tables with little concept padding, but at ~360 lines it is long; the placeholder "When to Use" line and a partly duplicated StackExchange.Redis connection section could be tightened, fitting the "mostly efficient but could be tighter" anchor.	3 / 5
Actionability	Ten numbered workflows ship copy-paste-ready, fully executable C# covering create/get/update/delete, access keys, firewall rules, patch schedules, import/export, and reboot, matching the anchor for fully executable examples covering common cases.	5 / 5
Workflow Clarity	Workflows are clearly sequenced and an error-handling section exists, but destructive operations (delete cache, force reboot, regenerate keys) show no validation/verification steps, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers give reasonable internal structure, but all content is inlined in a single ~360-line file with no bundle files or external references; reference material like the SKU and key-type tables that would benefit from separation is inline, fitting the "some structure but could be better organized" anchor.	3 / 5
	Total	14 / 20 Passed

Description

52%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 distinct and names its niche precisely, but it is too terse: it omits concrete actions and any explicit use-when trigger guidance, which limits specificity and completeness.

Suggestions

Add 2-3 concrete actions, e.g. "Provision and manage Azure Cache for Redis resources, configure firewall rules, and rotate access keys."

Append an explicit "Use when…" trigger clause such as "Use when provisioning or managing Azure Cache for Redis via Azure Resource Manager in .NET."

Include natural synonyms (e.g. Azure Cache for Redis, ARM) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description "Azure Resource Manager SDK for Redis in .NET." names the domain clearly but states no concrete actions (e.g. provision, configure, manage), matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It gives a clear "what" (an ARM SDK for Redis in .NET) but provides no "Use when…" trigger clause; per the judging guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say (Azure, Redis, .NET) are present, but there are no synonyms or common variations (e.g. cache, ARM, Azure Cache for Redis), fitting the anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	It targets a very specific niche (Azure Resource Manager Redis SDK for .NET) with minimal overlap risk against other skills, matching the anchor for a clear niche with distinct triggers.	5 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/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.