Name: azure-resource-manager-postgresql-dotnet
Rating: 48.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-postgresql-dotnet

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

Quality

53%

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

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

Quality

Content

57%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 comprehensive executable C# examples, but it functions as an inlined ~430-line API reference rather than a lean overview pointing to deeper materials, and its destructive/database workflows omit the validation checkpoints the rubric requires. Conciseness and progressive disclosure are the main drag on an otherwise strong skill body.

Suggestions

Add explicit validation/verification checkpoints to destructive and database workflows — e.g. confirm the resource exists and prompt/verify before 'Delete Server', and check server State after Stop/Start/Scale/Restore before proceeding.

Externalize reference material into one-level-deep bundle files (e.g. references/types.md, references/skus.md, references/workflows.md) and keep SKILL.md a concise overview with clearly signaled links, rather than inlining all eleven workflows and the type/SKU/version/HA tables.

Move time-sensitive version info ('Current Version', 'API Version', version enum table) into a versioned/deprecated section or a separate reference file so it does not penalize conciseness and is easy to update.

Dimension	Reasoning	Score
Conciseness	The body is code-dense with little concept over-explanation, but it is very long and inlines reference tables plus time-sensitive version info ('Current Version: v1.2.0', 'API Version: 2023-12-01-preview', the version enum table) outside any deprecated/old-patterns section.	3 / 5
Actionability	Eleven full, mostly copy-paste-ready C# workflows plus install commands and concrete error handling give strong executable guidance; minor gaps remain from placeholders ('<tenant-id>', '<entra-object-id>') and type names that may not compile verbatim against the real SDK.	4 / 5
Workflow Clarity	Workflows are clearly numbered and sequenced, but destructive and database operations (notably 'Delete Server', 'Stop and Start Server', scale, point-in-time restore) lack validation/verification checkpoints and feedback loops, which caps workflow_clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Section headers provide reasonable structure, but no bundle files exist and all reference material (Key Types, SKU Tiers, PostgreSQL Versions, HA Modes tables, and the eleven detailed workflows) is inlined into SKILL.md rather than split into one-level-deep referenced files.	3 / 5
	Total	13 / 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 names its niche clearly but offers only a generic action ('Database management') and omits any explicit 'Use when...' trigger guidance, leaving both completeness and specificity middling. It is distinguishable from other skills but would benefit from concrete verbs and a trigger clause.

Suggestions

Replace the generic 'Database management' with concrete verbs, e.g. 'Create and scale PostgreSQL Flexible Servers, configure firewalls and Entra ID admins, manage databases, backups, and read replicas.'

Add an explicit 'Use when...' trigger clause naming natural user phrases such as 'Azure PostgreSQL', 'PostgreSQL Flexible Server', 'managed Postgres on Azure', or '.NET/C# Azure database management'.

Include synonyms and the language qualifier users actually say (e.g. 'C#' alongside '.NET') to improve trigger-term coverage and reduce overlap with the deprecated Single Server variant.

Dimension	Reasoning	Score
Specificity	The phrase 'Database management' is a generic action category rather than concrete operations like 'create servers, configure firewalls, manage replicas'; the domain is named but actions remain minimal.	2 / 5
Completeness	The 'what' is clear (an SDK for managing PostgreSQL Flexible Server deployments), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'Azure PostgreSQL Flexible Server', 'PostgreSQL Flexible Server', and '.NET' are relevant product keywords a developer would say, but common synonyms/variants ('managed Postgres', 'Azure Database for PostgreSQL', 'C#') are missing and the term is reused rather than broadened.	3 / 5
Distinctiveness Conflict Risk	'Azure PostgreSQL Flexible Server SDK for .NET' is a mostly distinct niche with minor overlap risk against closely related Azure ResourceManager skills; the absence of an explicit trigger phrase keeps it just below a 5.	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-claude/skills/azure-resource-manager-postgresql-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.