More screenshots
Works with the AI Agents you already use
Capacitor Deploy Ritual
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
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 withapp/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 underandroid/app/build/…, and readsandroid/app/build.gradlefor applicationId and version strings. - Device actions (only with a device connected):
adb installof the APK it just built,pm clearof YOUR app's id,am startof 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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Permissions
Allowed Hosts
File Scopes
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.