publish-external

Publish tested release zips to an external oracle-quickstart/oci-ai-blueprints pre-release.

3|2|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill publish-external
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-external
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/publish-external
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill publish-external

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of publishing tested release zips to an external Oracle Quickstart pre-release, including renaming, scanning for PII/secrets, and uploading assets in a deterministic, batched manner.

Core Features & Use Cases

  • Uploads five required release zips to the external pre-release under the correct naming conventions.
  • Performs a swap workaround to align with OCI Console link behavior, and validates assets before upload.
  • Scans zips for sensitive data and enforces safety checks prior to publishing to production or staging environments.

Quick Start

Publish a new release by providing the version tag to publish-external and let the skill perform the end-to-end upload.

Frequently Asked Questions about publish-external

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

FAQPage Schema
How do I publish release zips to a GitHub pre-release safely?

Publishing release zips to a GitHub pre-release safely requires validating all five required zips, enforcing PII and secret scans to stop on detected risks, applying console swap workarounds, and uploading assets using gh release upload --clobber.

What does a PII and secret scan check before uploading GitHub release assets?

A PII and secret scan checks release zips for sensitive data prior to publishing, enforcing safety checks that halt the upload process immediately upon detecting any security risks to ensure an auditable pre-release state.

How do I overwrite existing assets in a GitHub pre-release upload?

To overwrite existing assets in a GitHub pre-release upload, use the gh release upload command with the --clobber flag, which deterministically replaces existing files during the batched asset upload process.

How many release zips are required for an external Oracle Quickstart pre-release?

An external Oracle Quickstart pre-release requires exactly five release zips. The publishing process validates the presence of all five zips before applying the console swap workaround and uploading the assets.

Why does my GitHub release upload fail when publishing to an external pre-release?

Your GitHub release upload fails if PII or secret scans detect sensitive data within the zips, or if the required five release zips are missing. The process stops on any detected risk to ensure an auditable state.