Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/beclab/olares --skill olares-publishAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Publish an Olares app to the public Market
Shared front door: load `../olares-shared/SKILL.md` for suite routing and platform entry points. Publishing itself does not require an Olares login; apply the shared auth gate only when returning to local upload/install validation.
This skill is the public-distribution step, not the authoring step. Turning a repo / compose / Helm chart into an Olares app, refining it, and proving it installs and reaches running on your own Olares all live in `../olares-chart/SKILL.md`. Come here after the app already runs locally and you want it in the public Olares Market.Use olares-cli chart lint --help and `olares-chart` for chart syntax and authoring.
When to use
- Publish / publicly list / submit / distribute / 上架 an app to the public Olares Market
- Open or fix a PR to `beclab/apps`
- Sell an app (pay-to-download / paid listing)
- Produce the listing assets themselves — app icon, Market screenshots / 宣传图
- Write, revise, translate, or review the public Market copy in
OlaresManifest.yamland localized manifests - Keywords: publish to Market, submit to beclab/apps, app store listing, app description,
fullDescription,upgradeDescription, i18n, locale, app icon,metadata.icon,featuredImage/promoteImage,spec.supportArch, multi-arch, GitBot,ownersfile,price.yaml, paid app
Prerequisite — the app must already run on your Olares. Public submission without a working local install wastes GitBot cycles and reviewer time. Do the deploy loop in the `olares-chart` skill (its Deploy step) first.
Mental model
Publishing is a one-way contribution to beclab/apps, not an olares-cli publish lifecycle. Start from a locally proven chart, establish accurate English listing copy, localize only the declared and maintained locales, add public-listing assets and matching multi-arch support, re-lint, then submit through GitHub and GitBot.
GitBot checks mechanical policy; it does not validate product quality, screenshot truthfulness, or security claims. The submitter owns those claims.
Workflow index
| Current intent / state | Read |
|---|---|
| Decide what blocks submission, what can be deferred, metadata depth, architectures | release targets |
| Research, draft, or review English Manifest listing copy | Manifest copy |
| Translate or review localized Manifest copy | Manifest localization |
| Produce the required 256×256 icon from upstream material | icon workflow |
| Capture/source 1440×900 Market images | listing images |
| Compose listing-image headlines and image layout | listing layout |
| Prepare folder, owners, PR title, and respond to GitBot state | submission workflow |
| Add pay-to-download | paid apps |
Release decisions
- The icon is on the critical path because
metadata.iconis lint-required. Hero/screenshots are optional and may follow in anUPDATE. - Build images for the architectures declared by
spec.supportArch; a local single-node success does not prove public multi-arch availability. - Assets must come from the upstream project, its site, or the user's running instance. Do not invent logos, screenshots, testimonials, or capabilities.
- Market copy must be factual, neutral, and written for app users. Do not turn chart implementation details into features or upgrade notes.
upgradeDescriptionis conditional: omit it for a first listing or update with no reliable user-facing upgrade information; never addInitial releasemerely to fill the field. When approved English contains a meaningful upgrade notice, keep every declared locale in sync.- Public chart credentials must come from install-time inputs, middleware, or chart generation; never commit live secrets.
- Paid distribution adds
price.yamland application-sideVERIFIABLE_CREDENTIALenforcement; it does not replace the normal public-listing requirements.
Validation and asynchronous semantics
- Re-run chart lint after every manifest or asset-path change.
- Before localization or submission, resolve any copy drift between the root Manifest and the English locale Manifest; do not silently select or combine them.
- Local install and
runningvalidation belong to Chart/Market and can be asynchronous; do not infer that a successful upload ACK proves installability. - GitBot processing is asynchronous. Interpret its current label/check state using the submission reference; do not repeatedly open duplicate PRs.
Safety and escalation
- Do NOT fork, push, or open PRs on the developer's behalf without explicit consent — these write to their GitHub account.
- The fork here is legitimate and required. Submitting to the public Market is the standard open-source contribution flow: fork `beclab/apps`, push a branch, open a PR. This is the public app catalog, a different repo from the beclab dev repos the workspace "no-fork, push to
origin" rule covers — that rule does not apply tobeclab/appssubmissions. - Do NOT run
did-cli rsa set(an on-chain, gas-costing write), touch the wallet mnemonic, or handlersa-private.pemfor paid apps — guide the user to run those themselves. - Do verify the chart against the market-ready checklist, author
price.yaml, wire the manifest, and interpret GitBot labels. - Stop on unclear upstream licensing, asset provenance, architecture support, owner identity, pricing, wallet actions, or permission to use GitHub.
- Upload/install verbs for local validation belong to `olares-market`.
