CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-fabric-py

Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.

57

Quality

66%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable, well-structured SDK reference with executable code for every common operation. Its main weaknesses are the absence of validation around destructive operations and minor redundancy/filler that could be trimmed or moved to reference files.

Suggestions

Add a verification step before destructive operations, e.g. confirm the capacity name/state via .get() and print a confirmation before begin_delete()/begin_suspend().

De-duplicate the credential/client setup: instantiate the client once in the Authentication section and reference it, rather than re-importing and re-creating it in 'Create Fabric Capacity'.

Replace the boilerplate 'When to Use' line with concrete trigger guidance, or move the SKU/states reference tables into a separate reference file to tighten SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly lean code blocks and tables that assume Claude's competence and skip explaining what Fabric is, but it repeats the credential/client setup in the 'Create Fabric Capacity' section and ends with a boilerplate 'When to Use' line that adds little.

4 / 5

Actionability

It provides copy-paste-ready, fully executable Python for the common operations (create, get, list, update, suspend, resume, delete, check-name, list-SKUs) with concrete parameter values and result access patterns.

5 / 5

Workflow Clarity

Operations are individually clear and the LRO section explains waiting with .result(), but destructive operations (delete, suspend) include no validation or verification checkpoint before/after execution, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The file is well-organized into clear sections with no nested references and no broken/missing bundle files, though the SKU and capacity-state tables plus full CRUD reference are all inlined in a single ~250-line file that could be partially split out.

4 / 5

Total

16

/

20

Passed

Description

57%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 clearly identifies a distinct niche and includes a use-case clause, but it is light on concrete actions and natural trigger phrases, leaning on the generic verb 'managing'. Adding specific operations and user-style triggers would lift the lower dimensions.

Suggestions

Replace the generic 'managing' with concrete actions, e.g. 'create, update, suspend, resume, and delete Microsoft Fabric capacities'.

Add natural user-facing trigger phrases, e.g. 'Use when the user asks to provision, scale, pause, or remove Azure/Fabric capacities'.

Mention package or resource identifiers (e.g. azure-mgmt-fabric, Microsoft.Fabric/capacities) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Azure Fabric Management SDK for Python') but the only action stated is the generic verb 'managing Microsoft Fabric capacities and resources', with no concrete CRUD or administrative actions enumerated.

2 / 5

Completeness

It states both what the skill does ('Azure Fabric Management SDK for Python') and when to use it ('Use for managing Microsoft Fabric capacities and resources'), though the 'when' clause largely restates the 'what' and could be more explicit with concrete user triggers.

4 / 5

Trigger Term Quality

It includes relevant keywords a user might say ('Microsoft Fabric', 'capacities', 'Azure'), but offers few natural variations, synonyms, or file/package-name triggers beyond the SDK title.

3 / 5

Distinctiveness Conflict Risk

The 'Microsoft Fabric capacities' niche is specific and unlikely to trigger for unrelated skills, with only minor overlap risk against other Azure management SDK skills.

4 / 5

Total

13

/

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.