CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-fabric-dotnet

Azure Resource Manager SDK for Fabric in .NET.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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

The canonical home for this skill is azure-mgmt-fabric-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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 executable code for every common operation, but it bloats the SKILL.md with reference material (SKU table, type list, enum values) that should live in separate files, and its destructive workflows lack explicit validation checkpoints.

Suggestions

Move the SKU reference table, Key Types reference, and Provisioning/Resource State enums into dedicated reference files (e.g. references/skus.md, references/types.md) and link to them from SKILL.md to reduce the monolithic body.

Add explicit validation checkpoints to destructive/batch workflows — e.g. after Delete/Suspend/Update, check `capacity.Data.Properties.ProvisioningState` and confirm the operation succeeded before proceeding.

Tighten the generic 'When to Use' section into a concrete trigger clause, or remove it if the frontmatter description will carry that guidance.

DimensionReasoningScore

Conciseness

The body is largely efficient with executable C# and minimal padding; only minor stretches (the intro restatement, the generic 'When to Use' line) could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides complete, copy-paste-ready C# across installation, auth, and all eight core workflows (create, get, update, suspend/resume, delete, list, name availability, SKUs), matching 'fully executable; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Workflows are sequenced but lack validation checkpoints for destructive/batch operations (delete, suspend, scale); the rubric caps workflow_clarity at 3 when validation/verification steps are missing for such operations.

3 / 5

Progressive Disclosure

The SKILL.md is a ~343-line monolith with the SKU table, key-type reference, and full state enums inlined, and no bundle files exist to offload this material — content that clearly belongs in separate reference files is inlined, matching the 'minimal structure; inlined' anchor.

2 / 5

Total

14

/

20

Passed

Description

41%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 frontmatter description identifies the skill's niche clearly but is a bare domain label with no concrete capabilities and no 'Use when' trigger guidance. Per the rubric's completeness cap, the missing explicit trigger clause limits the score.

Suggestions

Add concrete actions to the description, e.g. 'Provision and manage Microsoft Fabric capacity resources (create, scale, suspend, resume, delete) via Azure Resource Manager in .NET.'

Append an explicit 'Use when...' trigger clause, e.g. 'Use when provisioning or managing Fabric capacities in .NET, or when the user mentions Fabric capacity, ARM, or Azure.ResourceManager.Fabric.'

Include natural-language synonyms users would say ('Fabric capacity', 'Azure Fabric SDK', 'Fabric ARM') rather than only the technical product name.

DimensionReasoningScore

Specificity

The description 'Azure Resource Manager SDK for Fabric in .NET.' names the domain but states no concrete actions — it identifies what the SDK is, not what it does, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It gives a reasonably clear 'what' (an ARM SDK for Fabric in .NET) but has no 'when'/'Use when' guidance; per the rubric, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Azure Resource Manager SDK', 'Fabric', and '.NET' are technical jargon rather than natural phrases a user would say when needing the skill; it lacks common natural-language variations.

2 / 5

Distinctiveness Conflict Risk

The scope is a fairly distinct niche (Fabric management-plane SDK in .NET) with only minor overlap risk against the broad family of Azure ARM SDK skills.

4 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.