Manage Harness Artifact Registry (AR) via MCP. Configure private registries for Docker, Helm, Maven, npm, and PyPI artifacts, set up upstream proxies for caching public images, configure RBAC and cross-region replication, and define security scanning policies with CVE thresholds and license compliance checks. Use when asked to set up an artifact registry, configure Docker or Helm repositories, manage artifact security scanning, or set up replication. Do NOT use for creating connectors to external registries (use create-connector instead). Trigger phrases: artifact registry, docker registry, helm repository, artifact security, image scanning, private registry, artifact replication, CVE threshold, license compliance, SBOM.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Configure private artifact registries, security scanning policies, and cross-region replication in Harness Artifact Registry.
Confirm the user's org, project, and artifact format requirements.
Call MCP tool: harness_list
Parameters:
resource_type: "project"
org_id: "<organization>"Determine which workflow the user needs:
Gather from the user:
Docker Registry:
Helm Chart Repository:
Additional Formats (Maven, npm, PyPI):
Access Controls:
Replication:
Gather from the user:
Configure scanning policies:
Call MCP tool: harness_create
Parameters:
resource_type: "pipeline"
org_id: "<organization>"
project_id: "<project>"
body:
pipeline:
name: "artifact-security-scan"
identifier: "artifact_security_scan"
stages:
- stage:
name: Scan
type: SecurityTests
spec:
# vulnerability scanning step
- stage:
name: Policy Gate
type: Approval
spec:
# block if thresholds exceededharness/harness-ai
ca2ab81
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.