Name: azure-resource-manager-sql-dotnet
Rating: 48 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-sql-dotnet

Azure Resource Manager SDK for Azure SQL in .NET.

Quality

52%

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-claude/skills/azure-resource-manager-sql-dotnet/SKILL.md

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

Quality

Content

72%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 core provisioning workflow and is mostly token-efficient. Its main weaknesses are missing validation/feedback checkpoints for destructive database operations and reference-file links that point to nonexistent bundle files.

Suggestions

Add explicit validation checkpoints to the workflow (e.g. verify the server exists via GetAsync before creating dependent resources, and confirm firewall rules before building connection strings).

Create the referenced bundle files (references/server-management.md, database-operations.md, elastic-pools.md) or remove the Reference Files table so signaled links resolve to real files.

Move the bulk Database/Elastic Pool SKU tables and Key Types Reference into a reference file, keeping only the most common SKUs inline, to tighten the overview and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable code and tables with little concept explanation, but inline version pins ("Stable v1.3.0, Preview v1.4.0-beta.3") and some redundant reference tables keep it just below fully lean, matching the score-4 anchor of efficient with minor trims possible.	4 / 5
Actionability	It provides copy-paste-ready C# for installation, auth, server/database/elastic-pool/firewall creation, listing, and connection-string building, covering the common cases with executable specifics, matching the score-5 anchor.	5 / 5
Workflow Clarity	The seven-step core workflow is clearly sequenced and numbered, but these are database provisioning (destructive/batch) operations with no validation or verify checkpoints, which per the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Sections are well organized and a Reference Files table signals one-level-deep pointers, but the referenced files (references/server-management.md, database-operations.md, elastic-pools.md) do not exist in the bundle, and large SKU/Key-Type tables that could live in references are inlined, matching the score-3 anchor.	3 / 5
	Total	15 / 20 Passed

Description

32%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 correctly identifies the SDK's domain but is a static noun phrase rather than an action-oriented, trigger-rich summary. It lacks concrete verbs and any "Use when..." guidance, so it underperforms on completeness and trigger quality.

Suggestions

Rewrite as action-oriented third person, e.g. "Provisions and manages Azure SQL servers, databases, elastic pools, and firewall rules via the Azure Resource Manager SDK for .NET."

Add an explicit trigger clause such as "Use when provisioning or managing Azure SQL resources, configuring firewall rules, or setting up elastic pools in .NET."

Include natural user phrasing and file/SDK synonyms (e.g. "Azure SQL", "ARM", "SqlClient") to improve trigger-term coverage and reduce conflict with the data-plane SDK.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Azure Resource Manager SDK for Azure SQL in .NET") but lists no concrete actions, matching the score-2 anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It gives only a vague "what" (an SDK exists) and provides no "when" guidance at all, matching the score-2 anchor of a vague what with no when.	2 / 5
Trigger Term Quality	It surfaces a couple of relevant domain keywords ("Azure SQL", ".NET", "Azure Resource Manager") but lacks the natural phrases a user would say and has no "Use when..." trigger, falling between the score-1 (jargon only) and score-3 (some relevant keywords) anchors.	2 / 5
Distinctiveness Conflict Risk	The combination of ARM, Azure SQL, and .NET carves a fairly distinct niche with only minor overlap risk against the data-plane SqlClient SDK, fitting the score-4 anchor of mostly distinct with minor overlap.	4 / 5
	Total	10 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-resource-manager-sql-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.