More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Capacitor Deploy Ritual

    1

    Capacitor apps serve the WebView from cache; without `pm clear ` after installing, the phone happily shows the OLD build even when the APK is new.

    $11.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Capacitor Deploy Ritual

    Capacitor Deploy Ritual

    Example session with this skill installed

    An agent edits web code and is told 'deploy it'. Without the ritual it builds, installs, and the phone shows yesterday's app. With the ritual: bundle proof finds the telltale string missing in assets, refuses with the three typical causes, and the fix happens before any install.

    • Read your context and instructions
    • Compiled the capacitor deploy ritual

    Connects securely to your tools. The creator never sees your data.

    About this skill

    For web-technology apps wrapped natively with Capacitor, the deploy loop is deceptively small — and deceptively easy to get stale: edit code, run the build that succeeds anyway, install the APK, and see yesterday's app. The ritual makes that failure roar instead of hiding.

    The star is phase 4: pass one string that must exist in your new build — a label, a debug log token, any telltale — and the ritual refuses to install unless that string is literally inside assets/index-*.js. It converts "should have picked up my change" into a hard, mechanical check.

    Capacitor apps serve the WebView from cache; without pm clear <appId> after installing, the phone happily shows the OLD build even when the APK is new. The ritual clears and launches for you — and warns loudly if pm clear fails instead of pretending everything went green.

    • Toolchain in PATH-or-resolved locations: JDK 17+ (Java 21 preferred), Android SDK, Node.js for the web build, and a Capacitor-structured project (android/ at project root with app/build.gradle).
    • Network: none from the script itself. Phase 2/3 run your project's own build/sync commands (npm/npx), which may write to your project's build outputs; gradle and adb speak only to your local machine and the device connected over USB.
    • File I/O: removes the web dist/ intermediate folder inside your project, writes Android build outputs under android/app/build/…, and reads android/app/build.gradle for applicationId and version strings.
    • Device actions (only with a device connected): adb install of the APK it just built, pm clear of YOUR app's id, am start of your main activity.

    Ships the debug/install loop — release signing and Play Store upload are deliberately out of scope and documented as their own ceremony (keystore, signing configs, versionCode). Bundle proof is a literal grep: it works because Capacitor serves your web assets from a known folder; minification done before the check may rename tokens (the warning explains). Windows is supported through WSL only.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 15 days ago

    Requires

    Capacitor project
    JDK 17+
    Android SDK
    Node.js
    Linux
    macOS
    Windows
    cap

    Permissions

    Read Files
    Write Files
    Network Access

    Allowed Hosts

    127.0.0.1 (local device bridge via adb USB only)

    File Scopes

    removes
    the
    web
    dist/
    intermediate
    folder
    inside
    YOUR
    project
    writes
    Android
    build
    outputs
    under
    android/app/build/
    reads
    android/app/build.gradle
    for
    applicationId
    and
    version
    strings

    Endpoints and purpose: the script runs your project's own build and sync commands (npm/npx — network use is whatever your package workflow normally has), runs gradle and adb locally, and talks to the USB-connected device only to install the APK it just built, clear that app's cache (pm clear), and launch it (am start). It reads applicationId and version fields from your project's android/app/build.gradle. No other network access, no telemetry, no secrets read.

    Listed15 days ago
    Updated7 days ago

    What's inside

    Frequently Asked Questions

    After your web build and cap sync, the ritual greps your given telltale string inside android/app/src/main/assets/public/assets/index-*.js — the same files the WebView will serve. Not there? The install never happens and you get the three typical causes instead of a phone showing yesterday.

    Capacitor serves the WebView from cache. Without clearing your app's cache, the device happily keeps rendering the previous build even though the APK is new. The ritual clears it every time and warns if the clear fails rather than pretending green.

    Honestly no — and it says so. Debug builds are the daily loop where 'deployed but looks the same' burns hours. Release is a separate ceremony (keystore, signing, versionCode discipline) documented broadly; this skill keeps one job and does it without lying.

    It reads two fields from android/app/build.gradle, rebuilds your app's own dist folder, and touches the connected device for three actions it prints in full (install, cache clear, launch of your main activity). No network beyond your normal package workflow, no telemetry.

    New in LLM Ops