Name: azure-resource-manager-mysql-dotnet
Rating: 51.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-mysql-dotnet

Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments.

Quality

56%

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-mysql-dotnet/SKILL.md

The canonical home for this skill is azure-resource-manager-mysql-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 body is highly actionable with executable code across the full management surface, but it is a monolithic single-file reference that inlines bulk lookup material and embeds version/date data without a deprecated section. Destructive workflows lack validation checkpoints, capping workflow clarity.

Suggestions

Add validation/confirmation checkpoints to destructive and batch workflows (e.g., confirm resource identity before delete, verify restore target before point-in-time restore).

Move time-sensitive version/API/date values into a clearly labeled version or 'deprecated/old patterns' section so they do not penalize conciseness.

Split the large reference tables (Key Types, SKU Tiers, HA Modes, Related SDKs, Reference Links) into separate bundle files under references/ and link to them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and tables without over-explaining known concepts, but it embeds time-sensitive values ('Current Version v1.2.0', 'API Version 2023-12-30', date_added) outside any deprecated/old-patterns section, which penalizes token efficiency.	3 / 5
Actionability	Ten numbered workflows supply copy-paste-ready, executable C# covering create, firewall, configuration, Entra ID admin, backup/restore, scale, and delete, plus reference tables that cover the common cases.	5 / 5
Workflow Clarity	Workflows are clearly sequenced, but destructive and batch operations (notably 'Delete Server', scale, stop/start, point-in-time restore) lack validation/verification checkpoints, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers provide reasonable structure, but with no bundle files present all reference material (Key Types, SKU Tiers, HA Modes, Related SDKs, Reference Links) is inlined in one monolithic document rather than split into separate referenced files.	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 clearly identifies a specific niche but stops at a single generic action verb and omits any 'Use when...' trigger guidance. It is distinguishable yet incomplete and only moderately specific.

Suggestions

Replace the generic 'Database management' with concrete actions, e.g. 'Create servers, configure firewalls, manage databases, and restore backups for Azure MySQL Flexible Server.'

Add an explicit 'Use when...' clause naming natural trigger phrases such as 'Azure MySQL', 'Flexible Server', or provisioning/scaling MySQL on Azure.

Include synonyms or .NET-specific terms (e.g. 'Azure.ResourceManager.MySql', 'ARM') users are likely to say.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure MySQL Flexible Server SDK for .NET') but the only action stated is the generic phrase 'Database management', which is minimal and not concrete rather than listing specific actions like create/firewall/backup.	2 / 5
Completeness	A clear 'what' is present but there is no 'Use when...' trigger clause, so per the cap a missing explicit trigger guidance limits completeness to 3.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('Azure MySQL', 'MySQL Flexible Server', '.NET', 'Database management') but misses common variations, synonyms, or file extensions a user might say.	3 / 5
Distinctiveness Conflict Risk	The 'Azure MySQL Flexible Server SDK for .NET' niche is mostly distinct with only minor overlap risk against closely related Azure database SDKs.	4 / 5
	Total	12 / 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-mysql-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 18 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.