azure-containerregistry-py
Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-containerregistry-py74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 adequately identifies its domain (Azure Container Registry SDK for Python) and provides a reasonable scope of capabilities, but lacks the specificity of concrete actions and comprehensive trigger terms that would help Claude confidently select this skill. The 'Use for...' clause is present but could be strengthened with explicit user-facing trigger scenarios.
Suggestions
Add specific concrete actions like 'push and pull container images, manage tags, delete artifacts, list and configure repositories'
Include common trigger term variations such as 'ACR', 'docker registry', 'Azure docker', '.azurecr.io'
Expand the 'Use for...' clause to 'Use when the user mentions ACR, Azure Container Registry, or needs to manage container images in Azure'
| 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 provide comprehensive specific actions like 'push images', 'delete tags', 'list repositories'. | 2 / 3 |
Completeness | Has a 'Use for...' clause which partially addresses when to use it, but lacks explicit trigger guidance like 'Use when the user mentions ACR, Azure container registry, or needs to manage Docker images in Azure'. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'container images', 'artifacts', 'repositories', and 'Azure Container Registry', but misses common variations users might say like 'ACR', 'docker registry', 'container repo', or 'push/pull images'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Azure Container Registry SDK for Python specifically, which is a distinct niche unlikely to conflict with other skills. The Azure-specific and Python SDK focus creates clear boundaries. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted SDK reference skill with excellent conciseness and actionability. The code examples are complete and cover the full API surface. However, it lacks validation checkpoints for destructive operations (deletes) and could benefit from better progressive disclosure by splitting the reference table and advanced patterns into separate files.
Suggestions
Add explicit validation steps before destructive operations (e.g., 'Verify manifest exists and check tags before deleting')
Include error handling examples for common failure scenarios (authentication failures, missing resources)
Consider splitting the operations table and best practices into a separate REFERENCE.md file to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | All code examples are complete and executable with proper imports shown. The examples cover authentication, CRUD operations, and common workflows with copy-paste ready code. | 3 / 3 |
Workflow Clarity | The 'Clean Up Old Images' section shows a workflow but lacks explicit validation steps. For destructive operations like delete_manifest and delete_repository, there are no verification checkpoints or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document. The operations table and best practices could be split into separate reference files, and there are no links to external documentation for advanced topics. | 2 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.