What problem does it solve? Harbor container registry work spans three distinct toolchains — REST API calls, Helm deployments, and Terraform infrastructure-as-code — and choosing the wrong approach wastes time. This Skill acts as a router that directs your request to the correct Harbor sub-skill based on what you need to accomplish. ## Core Features & Use Cases - Task Routing: Maps user requests to the right sub-skill: harbor-api for REST API operations, harbor-helm for Kubernetes deployments, and harbor-terraform for infrastructure as code. - Quick Task Map: Provides a lookup table covering common tasks like creating projects, robot accounts, replication rules, retention policies, OIDC auth, and Trivy scanner configuration. - Use Case: You ask to "set up a robot account for CI" — the router identifies this as an API task and loads harbor-api, while "deploy Harbor on Kubernetes" routes to harbor-helm. ## Quick Start Ask the agent to create a Harbor project via the API, and it will route your request to the appropriate Harbor sub-skill.