Deploy your code or any project to your Olares

Shared front door: load ../olares-shared/SKILL.md for suite routing, active-profile selection, and platform entry points. Authoring — from-compose, lint, package — needs no Olares at all, so start it without one; apply the shared auth gate when the work reaches upload, install or any other deploy step. Load its auth reference only when login, profile switching, token storage, or auth recovery is actually needed.

Flags and syntax come from olares-cli chart <verb> --help. Read the shared Olares platform model before porting: chart decisions depend on its storage, uid-1000, namespace, middleware and version semantics.

Building for a specific Olares needs the target node architecture before the first image build, not at deploy time.

Porting targets Olares 1.12.6+; load versioning before writing manifest/chart version and dependency fields.

When to use

• Turn a repo / docker-compose / generic Helm chart into an Olares app, or validate an OlaresManifest; package its image; wire storage / middleware / entrances / env / GPU
• Deploy / run the app on your own Olares (market upload + install); after olares-doctor identifies a chart-owned root cause, edit, lint, and redeploy the chart
• Serve a generation/chat model with an official base app, integrate llm-init, or route an embedding app to the appropriate Market install

This skill owns changes to your chart. olares-doctor finds runtime root causes, olares-market manages published apps, olares-router configures and calls a model once its application is running, and olares-publish prepares a public listing.

The shape of the work — two axes