Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-containerregistry-py/SKILL.mdQuality
Discovery
57%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 identifies a clear domain and provides some useful keywords, but it remains at a moderate level of specificity by using the generic term 'managing' rather than listing concrete operations. It would benefit from an explicit 'Use when...' clause with natural trigger terms and common abbreviations like 'ACR'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with Azure Container Registry, ACR, or manage Docker images in Azure.'
Include common trigger term variations such as 'ACR', 'docker registry', 'push/pull images', and '.azurecr.io'.
List more specific concrete actions like 'list, tag, delete, push, and pull container images' instead of the generic 'managing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Container Registry SDK for Python) and lists some actions ('managing container images, artifacts, and repositories'), but doesn't enumerate specific concrete actions like pushing, pulling, tagging, deleting, or listing images. | 2 / 3 |
Completeness | Has a 'what' (Azure Container Registry SDK for Python) and a partial 'when' ('Use for managing container images, artifacts, and repositories'), but lacks an explicit 'Use when...' clause with trigger scenarios like 'when the user asks about ACR or Azure container registries'. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure Container Registry', 'container images', 'artifacts', and 'repositories', but misses common variations users might say such as 'ACR', 'docker registry', 'push image', 'pull image', or '.azurecr.io'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Azure Container Registry SDK for Python, which is a distinct niche unlikely to conflict with other skills. The combination of Azure, container registry, and Python SDK makes it highly distinguishable. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%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 operation has a concrete, executable Python example. The main weaknesses are the lack of validation/verification steps for destructive operations (delete repository, delete manifest, batch cleanup) and the monolithic structure that could benefit from progressive disclosure. Some minor verbosity exists in boilerplate sections and redundant content.
Suggestions
Add a dry-run or verification step to the 'Clean Up Old Images' workflow (e.g., collect digests first, print count, then confirm before deleting) and add verification after delete operations.
Split the detailed API reference table and advanced operations (async, upload/download) into separate referenced files to improve progressive disclosure.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary sections like the boilerplate 'When to Use' and 'Limitations' sections that add no value. The summary table at the end partially duplicates what's already shown in the code examples above it. Some code blocks re-declare the client unnecessarily. | 2 / 3 |
Actionability | All code examples are concrete, executable Python with proper imports and realistic usage patterns. Operations like listing repos, deleting manifests, cleaning up old images, and async usage are all copy-paste ready with specific method calls and parameters. | 3 / 3 |
Workflow Clarity | The 'Clean Up Old Images' section involves destructive batch deletion but lacks explicit validation checkpoints or a dry-run step before actual deletion. The delete operations throughout have no confirmation or verification steps. Per rubric guidelines, missing feedback loops for destructive/batch operations caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic file (~180 lines of content) that could benefit from splitting the API reference table and detailed operations into separate files. There are no references to external files for advanced topics. However, the sections are well-organized with clear headers. | 2 / 3 |
Total | 9 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
76cbde3
Table of Contents
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.