azure-mgmt-fabric-dotnet

Azure Resource Manager SDK for Fabric in .NET.

Quality

44%

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 ./skills/azure-mgmt-fabric-dotnet/SKILL.md

Quality

Content

61%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides highly actionable, executable C# code covering all major operations for Azure.ResourceManager.Fabric. However, it suffers from being overly long with reference material (SKU tables, state enumerations, type listings) that should be in separate files, and its workflows lack explicit validation checkpoints for destructive or long-running operations.

Suggestions

Move the SKU reference table, Key Types Reference, and Provisioning/Resource States sections into separate bundle files (e.g., SKU_REFERENCE.md, TYPES.md) and reference them from the main skill.

Add explicit validation steps to workflows: check provisioning state before operations, verify state after create/update, and add a confirmation pattern before delete.

Remove the vacuous 'When to Use' section and trim the 'Related SDKs' table which Claude can infer from context.

Add a state-check step before suspend/resume/delete operations (e.g., verify capacity is Active before suspending) to create proper feedback loops.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~300 lines) with some unnecessary content like the SKU reference table, provisioning state enumerations, and the 'Related SDKs' table that Claude could look up. The 'When to Use' section at the end is vacuous. However, the code examples themselves are reasonably tight.	3 / 5
Actionability	All code examples are fully executable, copy-paste ready C# with proper using statements, complete method calls, and realistic parameters. The skill covers all CRUD operations plus suspend/resume, name availability checks, and error handling with specific status codes.	5 / 5
Workflow Clarity	The workflows are presented as numbered sections but lack validation checkpoints. For destructive operations like Delete (section 5) there's no confirmation or state-checking step. Create operations don't verify provisioning state after completion. The best practices mention checking provisioning state but this isn't integrated into the workflows themselves.	3 / 5
Progressive Disclosure	All content is inlined in a single monolithic file with no bundle files. The SKU reference table, key types reference, provisioning states, and common pitfalls could all be in separate referenced files. The document is over 300 lines with no external references for detailed content, making it a wall of information.	2 / 5
	Total	13 / 20 Passed

Description

27%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.

This description is essentially just a technology label with no actionable detail. It fails to describe what the skill does (no verbs or concrete actions) and provides no guidance on when Claude should select it. While the technology stack mentioned is somewhat distinctive, the lack of specificity and completeness severely limits its usefulness for skill selection.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Creates, updates, and manages Microsoft Fabric resources (capacities, workspaces) using the Azure Resource Manager .NET SDK.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user needs to provision, configure, or manage Fabric resources programmatically via ARM in C#/.NET.'

Include common synonyms and abbreviations like 'ARM', 'C#', 'Microsoft Fabric', 'Fabric capacity management' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure Resource Manager SDK for Fabric in .NET) but provides no concrete actions—no verbs describing what the skill actually does.	2 / 5
Completeness	There is no clear 'what does this do' beyond naming a technology stack, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing.	1 / 5
Trigger Term Quality	Includes relevant technical keywords like 'Azure Resource Manager', 'SDK', 'Fabric', and '.NET' that users might search for, but lacks natural phrases users would say (e.g., 'deploy Fabric resources', 'manage workspaces', 'provision capacity') and common synonyms or abbreviations like 'ARM'.	3 / 5
Distinctiveness Conflict Risk	The combination of Azure Resource Manager + Fabric + .NET is somewhat specific, but without concrete actions it could overlap with general Azure SDK skills or general Fabric skills.	3 / 5
	Total	9 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-mgmt-fabric-dotnet/SKILL.md
Commit: 57c135b

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