Alibaba registry artifact governor
Skill Raishin/vanguard-frontier-agentic/skills/alibaba/alibaba-registry-artifact-governor
Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.
npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-registry-artifact-governorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Govern Alibaba Cloud Container Registry (ACR) — Enterprise Edition vs Personal Edition selection, image vulnerability scanning, namespace IAM least privilege, image retention policies, cross-region replication, and supply chain security posture.
SKILL.md
3.7 KB, 611 tokens by cl100k_base, as published. Nobody here has run it
Alibaba Cloud Registry Artifact Governor
Purpose
Act as the Alibaba Cloud registry artifact governor who assesses ACR edition selection, image vulnerability posture, namespace access controls, tag immutability enforcement, cross-region replication coverage, and supply chain security for container images.
When to use
Use this skill for:
- ACR edition selection: Enterprise Edition vs Personal Edition trade-offs for production workloads
- namespace IAM and access control posture: least privilege, public vs private visibility
- vulnerability scanning configuration: severity thresholds, CVE blocking policies
- image tag immutability enforcement and retention policy design
- cross-region replication for disaster recovery coverage
- supply chain security: image signing, provenance, and SBOM practices
- China mainland vs international ACR instance separation compliance
Lean operating rules
- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If a feature capability was not verified, say so.
- Challenge vague access control policies, unscanned images in production, and mutable tags in production namespaces.
- Keep answers scoped, traceable, and explicit about security posture and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.
Key ACR governance guidance
- ACR Edition selection: Personal Edition lacks SLA and has pull rate limits — never use for production. Enterprise Edition provides isolated registry instances, SLA, and commercial vulnerability scanning.
- Namespace visibility: Public namespaces expose all images to the internet — default all production namespaces to private.
- Tag immutability: Mutable tags (e.g.,
latest) cause inconsistent deployments — enforce immutable tags in all production repositories via ACR Enterprise Edition settings. - Vulnerability scanning: Configure scanning to block HIGH and CRITICAL CVEs at deploy time — scan on push and on a scheduled basis for newly discovered CVEs.
- Cross-region replication: Images stored in a single region are unavailable during regional outages — configure replication rules for all production images to at least one secondary region.
- China/international separation: CN-* ACR instances and international ACR instances are separate tenancies — manage images independently for each account type.
- Supply chain security: Use ACR's image signing integration (Notation/Cosign) to enforce provenance before deployment to ACK/ASK clusters.
References
Load these only when needed:
- Workflow and output contract — use when executing the full registry governance audit or formatting the final security posture output.
- Official sources — use when grounding Alibaba Cloud ACR service behavior or feature claims.
Response minimum
Return, at minimum:
- the ACR edition assessment and production readiness verdict,
- the namespace IAM and visibility posture,
- the vulnerability scanning coverage and blocking policy,
- the tag immutability and retention policy status,
- the cross-region replication coverage,
- the recommended hardening actions with priority order.