skills.rest
beclab
beclabOFFICIAL
Explore all skills by this author →
GitHub

olares-publish

Publish locally running Olares apps to the public Olares Market via beclab/apps PRs.

5.2k|321|Updated Apr 29, 2024
Search Tags:#icon generation#publish#github pr#olares#helm chart#app market#listing images
One-click install
npx skills add https://github.com/beclab/Olares --skill olares-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: olares-publish
Source: https://github.com/beclab/Olares/tree/main/cli/skills/olares-publish
Command: npx skills add https://github.com/beclab/Olares --skill olares-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Pillow, numpy, scipy, cairosvg, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Getting an app that already runs on your own Olares into the public Olares Market requires market-ready metadata, correctly sized listing assets, multi-arch image support, and a properly formatted PR to beclab/apps that survives GitBot validation — this Skill walks through that entire submission path.

Core Features & Use Cases

  • Market-readiness gating: Sorts requirements into hard gates (lint, categories, icon URL), functional reach (multi-arch images, supportArch), and listing quality tiers so you know exactly what blocks a merge.
  • Listing asset production: Generates the required 256x256 app icon from the project's real logo and composes 1440x900 featured/promote images around authentic screenshots using deterministic Pillow pipelines plus an optional image-model render tier.
  • Submission and lifecycle management: Guides the fork-and-PR flow to beclab/apps, PR title format, owners file, GitBot label interpretation, and UPDATE/SUSPEND/REMOVE lifecycle PRs, including paid listings via price.yaml and VERIFIABLE_CREDENTIAL.
  • Use Case: You have a Helm-style Olares chart running locally and want it listed publicly — use this Skill to produce the icon and screenshots, validate the chart, and open a compliant [NEW][myapp][0.0.1] PR.

Quick Start

Use the olares-publish skill to prepare my locally running app for the public Olares Market and walk me through opening the beclab/apps submission PR.

Frequently Asked Questions about olares-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an app to the Olares Market?▼

Confirm the app installs and reaches running on your own Olares first, then add market-ready metadata and assets, re-run olares-cli chart lint, fork beclab/apps, add your chart folder with an owners file, and open a PR titled like [NEW][myapp][0.0.1]. GitBot validates the PR before merge.

How do I create the required 256x256 Olares app icon?▼

Fetch the project's real logo from its repo or official site, then run scripts/generate_icon.py to composite it onto a 256x256 canvas. The script classifies the background, removes white via edge flood-fill, and verifies size, mode, and the 512 KB limit.

What image requirements does an Olares Market listing have?▼

The icon must be PNG or WEBP at 256x256 and under 512 KB, and it is lint-required. Featured and promote images are optional but recommended at 1440x900 in JPEG, PNG, or WEBP, each under 8 MB, with two to six images suggested.

Why did GitBot reject my beclab/apps PR?▼

Common causes are invalid metadata.categories values, a PR title whose folder or version segment mismatches Chart.yaml, files changed outside the chart folder, a duplicate open PR, or a reserved folder name. Fix the issue and push to the same draft PR, or open a new one if closed.

Can I sell a paid app on the Olares Market?▼

Yes, pay-to-download is supported by adding a price.yaml at the chart root and exposing the VERIFIABLE_CREDENTIAL env var for license checks. It requires approved developer status, Olares OS 1.12.3 or later, and a one-time on-chain RSA key registration with did-cli.

Does my Olares app need multi-architecture images to publish?▼

Multi-arch images are not a merge gate, but spec.supportArch must honestly list every architecture your image actually supports. Declaring an unbuilt arch fails installs for those users, while omitting a built arch hides the app from them.

Related Skills

Explore More Software Engineering Skills→
RHEcosystemAppEngRHEcosystemAppEng
48

helm-deploy

Deploy OpenShift applications using Helm charts with install, upgrade, and rollback.

Official
Intermediate
onlypfachionlypfachi

ship

Automate merging, testing, version bumping, changelog updates, and PR creation.

Community
Advanced
pantheon-orgpantheon-org
9

helm-validator

Validate Helm charts with linting, template rendering, and security checks.

Official
Advanced
beclabbeclab
5.2k

olares-market

Manage app lifecycles across multiple Olares market sources.

Official
Advanced