CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-ml-py

Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.

60

Quality

70%

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 ./skills/azure-ai-ml-py/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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

This is a solid API reference skill with excellent actionability—nearly every section provides executable, import-complete Python code. However, it reads more like a comprehensive cheat sheet than a well-structured skill, lacking validation checkpoints for multi-step workflows and progressive disclosure to manage its length. The boilerplate sections at the end and some generic best practices dilute the otherwise efficient content.

Suggestions

Add validation/error-handling steps for multi-step workflows, e.g., check job status before registering a model: `if returned_job.status == 'Completed': ml_client.models.create_or_update(...)`

Split detailed sections (pipelines, environments, compute) into separate referenced files to reduce the main skill's token footprint and improve progressive disclosure

Remove the generic 'When to Use' and 'Limitations' boilerplate sections, and trim 'Best Practices' to only non-obvious, SDK-specific guidance

DimensionReasoningScore

Conciseness

The content is mostly efficient with executable code examples, but includes some unnecessary sections like 'Best Practices' with generic advice Claude already knows (e.g., 'use versioning', 'tag resources'), and the boilerplate 'When to Use' and 'Limitations' sections add no value. The operations table is useful but the overall document could be tightened.

2 / 3

Actionability

Nearly all guidance is concrete, executable Python code with proper imports, realistic parameters, and copy-paste ready examples. The code covers authentication, CRUD operations across all major resource types, job submission, and pipeline creation with specific class names and method calls.

3 / 3

Workflow Clarity

Individual operations are clear, but multi-step workflows like the pipeline example lack validation checkpoints. There's no guidance on error handling, verifying job completion before model registration, or checking if resources were created successfully. The job monitoring section mentions streaming but doesn't show a validate-then-proceed pattern.

2 / 3

Progressive Disclosure

The content is a long monolithic document (~200 lines of code examples) with no references to external files for detailed topics like pipelines, environments, or advanced configurations. The operations summary table helps with navigation, but topics like pipeline component definitions and environment YAML specs could be split into separate references.

2 / 3

Total

9

/

12

Passed

Description

75%Scale 1-3

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 concise and well-structured with a clear 'Use for' clause and a distinct niche (Azure ML SDK v2). Its main weakness is that it lists resource categories rather than concrete actions, and it could benefit from additional natural trigger terms like 'AzureML', 'AML', 'training', or 'deployment'.

Suggestions

Replace or augment the noun list with concrete actions, e.g., 'Create and manage ML workspaces, submit training jobs, register models, deploy endpoints, configure compute resources, and build pipelines.'

Add common trigger term variations such as 'AzureML', 'AML', 'azure ml', 'training', 'deployment', 'endpoints', and 'experiments' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (Azure Machine Learning SDK v2) and lists several resource types (workspaces, jobs, models, datasets, compute, pipelines), but these are more like nouns/categories than concrete actions (e.g., 'create workspace', 'submit training job', 'register model').

2 / 3

Completeness

Clearly answers both 'what' (Azure Machine Learning SDK v2 for Python) and 'when' ('Use for ML workspaces, jobs, models, datasets, compute, and pipelines') with an explicit 'Use for' clause that provides trigger guidance.

3 / 3

Trigger Term Quality

Includes relevant keywords like 'Azure Machine Learning', 'SDK v2', 'ML workspaces', 'jobs', 'models', 'datasets', 'compute', 'pipelines' which are terms users might use. However, it misses common variations like 'AzureML', 'AML', 'training', 'deployment', 'endpoint', 'experiment', or 'Python SDK'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific mention of 'Azure Machine Learning SDK v2 for Python', which clearly differentiates it from generic ML skills, other cloud provider skills, or general Python skills. Unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-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.