azure-containerregistry-py

Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.

1.44x

Quality

66%

Does it follow best practices?

Impact

97%

1.44x

Average score across 6 eval scenarios

Securityby

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-containerregistry-py/SKILL.md

The canonical home for this skill is azure-containerregistry-py in sickn33/agentic-awesome-skills

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 an actionable, well-organized reference with strong executable examples, but its destructive/batch workflows lack validation checkpoints and it carries a small amount of generic padding. Adding verification steps to destructive flows and trimming the boilerplate 'When to Use' line would raise the score.

Suggestions

Add explicit validation checkpoints to destructive/batch workflows: e.g., a dry-run/print-only pass and a confirmation before deleting manifests, and a 'verify remaining manifests' step after cleanup.

Remove or replace the generic 'When to Use' sentence with concrete trigger guidance consistent with the description.

Fix the minor execution gaps (import `os`, define or reuse `endpoint`) so snippets are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code with minimal prose and clear section headers, though the generic 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is padding that could be trimmed.	4 / 5
Actionability	Numerous concrete, mostly copy-paste-ready code snippets plus an operations table cover the common cases, with only minor gaps such as `os.environ` used before `import os` and an undefined `endpoint` variable in some snippets.	4 / 5
Workflow Clarity	Operations are well organized as a reference, but the batch/destructive 'Clean Up Old Images' workflow and the delete operations lack explicit validation checkpoints (dry-run, confirmation, or verify-before-delete), which caps this dimension at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	A single well-structured file with clear section headers and no nested references; no bundle files exist. It is well organized, though at ~256 lines the detailed per-operation reference could plausibly be split into a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

65%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 is distinctive and uses good domain keywords, but it leans on one generic verb and lacks an explicit trigger ('Use when...') clause, leaving the when-to-use guidance weak. Rewording to add concrete actions and a trigger condition would lift it into the top band.

Suggestions

Replace the single verb 'managing' with several distinct concrete actions (e.g., 'List, upload, download, tag, and delete container images and artifacts in Azure Container Registry').

Add an explicit 'Use when...' trigger clause citing natural user phrasing (e.g., 'Use when the user mentions ACR, pushing/pulling container images, or managing Azure container registries').

Include the 'ACR' synonym so the description matches how users commonly refer to the service.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure Container Registry SDK for Python') and lists objects ('container images, artifacts, and repositories'), but relies on a single generic verb ('managing') rather than multiple distinct concrete actions, so it is not comprehensive.	3 / 5
Completeness	The 'what' is clear, but the 'Use for managing container images, artifacts, and repositories' clause restates the what rather than giving an explicit 'Use when...' trigger condition, so the when is only weakly present (capped at 3 per the missing-trigger-guidance rule).	3 / 5
Trigger Term Quality	'Azure Container Registry', 'container images', 'artifacts', and 'repositories' are natural terms users would say, though synonyms like 'ACR' and 'push/pull images' are missing.	4 / 5
Distinctiveness Conflict Risk	'Azure Container Registry SDK for Python' is a clear, narrowly-scoped niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-containerregistry-py/SKILL.md
Commit: 57c135b

Reviewed: 3 minutes ago

Table of Contents

Discovery Implementation Validation

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.