capgo-release-workflows
Guides the agent through setting up Capgo-centered release workflows for Capacitor apps. Use when the user needs a unified path for live updates, native builds, and app store publishing using Capgo plus repository-owned CI/CD. Do not use for non-Capacitor frameworks or for Ionic Enterprise plugin migration.
What this skill does
# Capgo Release Workflows Set up release workflows for Capacitor apps using Capgo live updates plus repository-owned build and publishing automation. ## When to Use This Skill - User wants one release workflow covering live updates, builds, and store publishing - User is replacing a hosted release service with repo-owned automation - User wants Capgo for OTA updates and standard CI/CD for native artifacts ## Scope This skill coordinates three workflow areas: - live updates -> `capgo-live-updates` - native builds -> `capacitor-ci-cd` - app store publishing -> `capacitor-app-store` Use this skill as the top-level router when the user asks for the whole release system, not just one piece. ## Procedures ### Step 1: Identify Release Requirements Determine whether the app needs: - OTA web updates - signed iOS and Android builds - TestFlight or Google Play publishing - staged channels or phased rollout Record which parts already exist in the repository. ### Step 2: Set Up Live Updates If OTA updates are required, use the `capgo-live-updates` skill. Preserve the app's release channel structure and define the rollback strategy before enabling automatic rollout. ### Step 3: Set Up Native Build Automation If the team needs reproducible native builds, use the `capacitor-ci-cd` skill. Keep signing, build environment variables, and version bumping under repository control. ### Step 4: Set Up Store Publishing If automated publishing is required, use the `capacitor-app-store` skill. Keep credentials, track selection, and release gating aligned with the current release policy. ### Step 5: Verify the End-to-End Release Flow Verify the workflow in order: 1. native build succeeds 2. store artifact is valid 3. live update upload works for the matching app version 4. rollback and channel targeting behave as expected ## Error Handling - For OTA setup issues, validate the Capgo plugin startup and rollback path before enabling broad rollout. - For CI/CD failures, fix signing and environment inputs before changing release logic. - For store publishing failures, isolate Apple and Google pipelines so one platform does not block diagnosis of the other.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.