build-actions-generator

Generates ODC build action JSON files configuring Capacitor plugin builds for Android and iOS.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/involvex/ionic-everywhere --skill build-actions-generator-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-actions-generator
Source: https://github.com/involvex/ionic-everywhere/tree/main/.agents/skills/build-actions-generator
Command: npx skills add https://github.com/involvex/ionic-everywhere --skill build-actions-generator-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring native mobile builds for OutSystems Developer Cloud (ODC) plugins requires hand-writing complex buildAction.json files with platform-specific actions, variables, and conditions. This Skill automates that generation by scanning Capacitor or Cordova plugin sources and producing correct, validated JSON for Android and iOS builds via MABS 12+. ## Core Features & Use Cases - Automated JSON Generation: Scans plugin documentation, plugin.xml, package.json, and native source files to derive the correct Android (manifest, gradle, plist) and iOS (plist, entitlements, frameworks) build actions. - Variables and Conditions: Declares typed input variables (string, number, boolean) with defaults and conditional logic so consuming apps can supply values through ODC extensibility configurations. - Documentation Output: Writes a companion README.md alongside buildAction.json summarizing what was configured, ODC setup steps, and any hooks or elements that could not be mapped. - Use Case: A developer migrating a Cordova push-notification plugin to ODC runs this Skill in the plugin directory; it parses plugin.xml, maps hooks and config-file elements to build actions, and outputs build-actions/buildAction.json plus setup documentation. ## Quick Start Ask the assistant to generate an ODC build action JSON for the Capacitor or Cordova plugin in the current directory.

Frequently Asked Questions about build-actions-generator

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

FAQPage Schema
How do I create a buildAction.json file for an ODC plugin?

Run this Skill from the Capacitor or Cordova plugin root directory. It scans plugin documentation, plugin.xml, and native sources, then writes build-actions/buildAction.json with the required Android and iOS actions plus a README documenting ODC setup steps.

What native configurations can ODC build actions automate?

Build actions cover AndroidManifest.xml changes, Gradle file patches, XML resources, Info.plist entries, entitlements, Xcode build settings, frameworks, and file copies. Script-type logic like code generation cannot be expressed and requires a Capacitor hook instead.

Do build actions work with Cordova apps or MABS versions before 12?

No. Build actions only apply to Capacitor-based apps on OutSystems Developer Cloud built with MABS 12 or later. They have no effect in standalone Capacitor apps, Cordova apps, O11, or earlier MABS versions.

How do I pass variable values to a build action in ODC?

Declare typed variables with defaults in buildAction.json, then supply values through the parameters block of the extensibility configuration in ODC Studio. Values can reference extensibility settings so they are managed in ODC Portal without editing JSON.

Why are some plugin hooks not converted to build actions?

Hooks performing script-type operations like code generation, dependency installs, or complex branching have no build action equivalent. These are documented in the generated README with a recommendation to implement them as Capacitor hooks instead.