Capawesome Cloud

Guides the agent through setting up and using Capawesome Cloud for Capacitor apps. Covers three core workflows: (1) Native Builds — cloud builds for iOS and...

Security Scan

The skill's commands, references, and runtime instructions are consistent with its stated purpose (setting up Capawesome Cloud for Capacitor apps) and request only the credentials and files you'd expect for that work (certificates, keystores, Apple/Google auth).

Purpose & Capability

The name/description (native builds, live updates, app store publishing) match the included SKILL.md and reference files. All CLI commands and file types (.p12, .mobileprovision, .jks, Apple .p8 keys, Google service account JSON, etc.) are relevant to building, signing, uploading bundles, and publishing mobile apps.

Instruction Scope

Instructions tell the agent to run standard tooling (npx @capawesome/cli, asc, keytool, openssl, npm, cap sync) and to read or upload signing artifacts and API keys. These actions are appropriate for the workflows described, but they involve sensitive local files (private keys, keystores, provisioning profiles) and CLI authentication steps — the user should understand they must supply and manage these secrets locally or in their CI. The skill does not instruct the agent to read unrelated system files or secrets.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. No packages are automatically downloaded or written to disk by the skill itself — the risk surface is limited to the CLIs the user elects to run.

Credentials

The skill declares no required environment variables, which is reasonable for an instruction-only guide. The procedures, however, legitimately reference environment variables and secrets used by Capawesome Cloud builds and CI (NPM tokens, JAVA_VERSION, certificate passwords, Apple API keys, Google service account keys). Requesting these artifacts is proportionate to the described tasks, but users should be aware they will need to provide sensitive credentials/secrets to the Capawesome CLI or Capawesome Cloud per the documented commands.

Persistence & Privilege

The skill does not request persistent privileges (always:false). It does not modify other skills or system-wide agent settings; it only provides procedural instructions for interacting with external services and local files.

Assessment

This skill is a procedural guide for Capawesome Cloud and appears coherent with that purpose. It will instruct you to run CLIs and to create/provide sensitive artifacts (Apple .p8/.p12, provisioning profiles, Android keystores, Google service-account JSON, CI tokens, and keystore/passwords). Before proceeding: (1) Verify you trust the skill source (the SKILL.md includes a GitHub URL; consider inspecting that repo yourself). (2) Do not paste secrets into chat; use the official Capawesome Cloud console or CI secret stores. (3) When you run any CLI commands (npx @capawesome/cli, asc, openssl, keytool), ensure you install those CLIs from their official sources (npm or upstream repos) and review their help output. (4) Be careful with ad-hoc environment variables (they warned these may appear in build logs) and prefer encrypted secrets for CI. (5) If you have doubts about a particular step (for example uploading a private key to an unfamiliar endpoint), confirm the official Capawesome Cloud console domain (console.cloud.capawesome.io) and verify you're interacting with that service before uploading credentials.

Set up and manage native builds, live updates, and app store publishing for Capacitor apps using Capawesome Cloud.

Prerequisites

1. A Capawesome Cloud account and organization.
2. A Capacitor 6, 7, or 8 app.
3. Node.js and npm installed.
4. For Native Builds: The app must be in a Git repository (GitHub, GitLab, Bitbucket, or Azure DevOps).
5. For Apple App Store Publishing: An active Apple Developer Program membership and an app created in App Store Connect.
6. For Google Play Store Publishing: A Google Play Developer account and an app created in Google Play Console with at least one version uploaded manually.

General Rules

Before running any @capawesome/cli command for the first time, run it with the --help flag to review all available options.

Procedures

Step 1: Authenticate with Capawesome Cloud

npx @capawesome/cli login

For CI/CD, use token-based auth:

npx @capawesome/cli login --token <token>

Step 2: Create an App in Capawesome Cloud

Skip if the user already has an app ID.

npx @capawesome/cli apps:create

The CLI prompts for organization and app name, then outputs the app ID (UUID). Save for subsequent steps.

Step 3: Identify Required Feature(s)

Ask the user which Capawesome Cloud feature(s) to set up:

1. Native Builds — Build iOS and Android apps in the cloud.
2. Live Updates — Push OTA web updates to deployed apps.
3. App Store Publishing — Automate submissions to Apple App Store or Google Play Store.

The user may select one or more features. Proceed to the corresponding sections below.

Native Builds

Read references/native-builds.md for the full native builds setup and usage procedure. This covers:

• Connecting a Git repository
• Uploading signing certificates (Android keystores, iOS .p12 + provisioning profiles)
• Configuring environments and secrets
• Configuring build settings (monorepos, custom build commands)
• Triggering builds
• Monitoring and downloading build artifacts
• Configuring native configuration overwriting with Trapeze
• Setting up CI/CD pipelines

Live Updates

Read references/live-updates.md for the full live updates setup and usage procedure. This covers:

• Installing the @capawesome/capacitor-live-update plugin
• Configuring the plugin in Capacitor config
• Adding rollback protection
• Adding update logic (Always Latest, Manual Sync, Force Update)
• Configuring iOS Privacy Manifest
• Configuring version handling (versioned channels, versioned bundles)
• Testing the setup

App Store Publishing

Read references/app-store-publishing.md for the full app store publishing setup and usage procedure. This covers:

• Creating Apple App Store destinations (API Key or Apple ID auth)
• Creating Google Play Store destinations
• Deploying builds to destinations
• Building and deploying in one step

Error Handling

Native Builds

• invalid source release: 21 → Set JAVA_VERSION env var to 17 or 21. Read references/build-troubleshooting.md.
• JavaScript heap out of memory → Set NODE_OPTIONS env var to --max-old-space-size=4096. Read references/build-troubleshooting.md.
• Authentication errors → Re-run npx @capawesome/cli login. For CI/CD, verify the token.
• Missing signing certificate → Upload via apps:certificates:create. Read references/certificates-android.md or references/certificates-ios.md.
• Expired provisioning profile → Regenerate in Apple Developer Portal and re-upload. Read references/certificates-ios.md.
• Web build step fails → Ensure package.json has capawesome:build or build script. Read references/build-configuration.md.

Live Updates

• npx cap sync fails → Verify plugin version matches Capacitor version in package.json.
• Bundles not applied → Ensure LiveUpdate.ready() is called before readyTimeout expires.
• App reverts to default bundle after restart → ready() likely not called. Add it early in app init.
• Upload auth errors → Re-run npx @capawesome/cli login.
• Updates not detected with autoUpdateStrategy: "background" → Updates only checked if last check was >15 min ago. Force-close and restart.
• Read references/live-update-plugin-api.md for the full SDK API reference.
• Read references/live-update-faq.md for compliance, billing, and limitations.

App Store Publishing

• Authentication errors → Re-run npx @capawesome/cli login.
• Destination creation fails → Verify credentials. Read references/apple-app-store-credentials.md or references/google-play-store-credentials.md.
• iOS build not appearing in TestFlight → Build processing may take time. Common causes: build number not incremented, missing Privacy Descriptions in Info.plist, insufficient permissions.
• Google Play deployment fails → Ensure first version was uploaded manually. Verify service account has Release permissions.
• Deployment timeout → Use --detached flag and check logs with apps:deployments:logs.
• apps:deployments:create fails with "build not found" → Ensure the build completed successfully.
• Cancel a stuck deployment → npx @capawesome/cli apps:deployments:cancel --app-id <APP_ID> --deployment-id <DEPLOYMENT_ID>.

Related Skills

• capacitor-app-development — For general Capacitor development topics, CI/CD patterns, and troubleshooting.
• capawesome-cli — For the full Capawesome CLI command reference, project configuration, and CI/CD integration details.
• capacitor-plugins — For installing and configuring Capacitor plugins, including the @capawesome/capacitor-live-update plugin.
• ionic-appflow-migration — For migrating existing Ionic Appflow projects to Capawesome Cloud.
• capacitor-in-app-purchases — For setting up in-app purchases and subscriptions before publishing to app stores.