Name: microsoft-azure-sql-database
Rating: 59.2 (1 reviews)
Author: membranedev

microsoft-azure-sql-database

Microsoft Azure SQL Database integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Azure SQL Database data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-azure-sql-database/SKILL.md

Quality

Content

68%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 concrete, executable Membrane CLI commands and a strong connection-readiness feedback loop, undermined mainly by an unnecessary introductory paragraph and a lack of validation guidance for destructive database operations.

Suggestions

Delete or trim the opening "Azure SQL Database is a fully managed PaaS database engine..." paragraph; Claude already knows this and it adds no skill-specific value.

Add a validation/verification checkpoint before destructive actions, e.g. confirm scope or run a read query first and verify affected rows before DELETE/UPDATE via `membrane action run`.

Consider moving the detailed clientAction state reference and the proxy flags table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Azure SQL Database is a fully managed platform as a service (PaaS) database engine...") explains a product Claude already knows, which is padding; the rest is mostly efficient CLI commands, so it is mostly efficient with some unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a thorough proxy flags table, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection-readiness flow is well sequenced with a poll feedback loop and explicit state handling (READY / CLIENT_ACTION_REQUIRED / ERROR), but for a skill that runs database operations the action-execution workflow lacks validation/verification steps before destructive operations, which caps this dimension per the database-operations guideline.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and no bundle files; minor gaps are the detailed clientAction states and proxy flag table that could live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

70%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 well-formed with explicit third-person voice and a clear "Use when" trigger covering both what and when. Its main weakness is generic action verbs ("manage data") that under-specify the actual capabilities of an Azure SQL Database integration.

Suggestions

Replace generic verbs with concrete operations, e.g. "run SQL queries, insert and update records, manage firewall rules and database/server resources, automate workflows".

Broaden trigger terms to include natural synonyms users say, such as "Azure SQL", "SQL database", or "query an Azure SQL database".

Make the "Use when" clause less circular by naming concrete scenarios, e.g. "Use when the user wants to query, read, or modify data in an Azure SQL Database".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and a few actions, but the actions are generic ("manage data" is near-tautological for a database) rather than concrete operations like "run queries" or "insert rows", matching the 1-2 concrete-but-not-comprehensive anchor.	3 / 5
Completeness	It states what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Microsoft Azure SQL Database data"), but the trigger clause is somewhat circular and could be more specific, fitting the both-present-but-when-could-be-sharper anchor.	4 / 5
Trigger Term Quality	"Microsoft Azure SQL Database" and "interact with Microsoft Azure SQL Database data" give good coverage of the natural product name a user would say, though synonyms like "Azure SQL", "SQL Server", or "SQL database" are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product "Microsoft Azure SQL Database" carves a distinct niche with minimal conflict risk, though it could still overlap with generic SQL/database or other Azure skills, fitting mostly-distinct with minor overlap.	4 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/microsoft-azure-sql-database/SKILL.md
Commit: f484c82

Reviewed: 6 days 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.