A curated marketplace of plugins for Claude Code — practical skills and utilities we use at Premex every day, open-sourced so you can use them too.
⚡ Two commands and you're in:
/plugin marketplace add premex-ab/claude-marketplace
/plugin install <plugin-name>@premex-plugins| 🚀 | android-cli | Bootstrap Google's agent-first android CLI and keep it fresh on your laptop + CI. |
| 📱 | adb-connect | Pair an Android device to ADB over Wi-Fi by scanning a QR code — no cables, no fumbling with ip:port. |
| 🤖 | android-* | Every skill from android/skills, auto-mirrored as one plugin per skill. |
| 🤝 | github-utils | Talk to Dependabot in plain English — Claude translates and posts the commands. |
| 🧹 | gradle-dagp | Analyze and fix Gradle module dependencies with DAGP — investigative, not blind; batched, not mega-PR. |
One-liner: Installs Google's new
androidCLI, keeps it current, hands off to the bundled skill. Install:/plugin install android-cli@premex-pluginsFull README: plugins/android-cli/README.md
Google's new android CLI is an agent-first replacement for the old sdkmanager / avdmanager / adb toolchain — ~70% fewer tokens and ~3x faster. This plugin gets it onto your machine (and your CI runners), keeps it fresh forever, and hands off to Google's bundled skill once setup is done.
What's in the box
| Ships with | What you get |
|---|---|
| 🌱 android-cli-setup skill | One-time install of the android CLI into ~/.local/bin (no sudo needed), runs android init to deposit Google's official android-cli skill into ~/.claude/skills/, hands off. |
| 🔁 SessionStart hook | Background refresh throttled to once per 24h — your CLI and bundled skill stay current without you ever running android update manually. |
| ⚙️ android-cli-ci skill | Working reference workflows for GitHub Actions, GitLab CI, CircleCI, Bitrise, Jenkins, Buildkite, and self-hosted runners — plus a side-by-side migration guide from sdkmanager + cmdline-tools setups you probably have today. |
| 🛠️ Slash commands | /android-cli-status, /android-cli-update, /android-cli-reset for inspection and manual control. |
Ask Claude like this
💬 "set up the android CLI on my laptop" → plugin bootstraps, then Google's skill takes over. 💬 "migrate our GitHub Actions workflow away from sdkmanager" → CI skill with a ready-to-paste replacement.
One-liner: Android Studio's Pair devices using Wi-Fi flow, but from Claude Code — works on macOS, Linux, and Windows. Install:
/plugin install adb-connect@premex-pluginsFull README: plugins/adb-connect/README.md
Skip the USB cable. Run /adb-connect:pair, a browser tab opens with a QR code, scan it from your phone's Wireless debugging menu, and your laptop runs adb pair + adb connect automatically via mDNS. One slash command, paired and connected in seconds.
What's in the box
| Ships with | What you get |
|---|---|
📲 /adb-connect:pair command |
Opens a browser tab with the pairing QR, waits for the phone to scan, pairs + connects, exits with Connected to HOST:PORT. One blocking Bash call — no polling loops. |
| 🌐 Local HTTP server with live status | Serves the QR page and a /status endpoint. The page auto-updates as the flow progresses: waiting → pairing → paired → connected. |
| 🔎 Pure-JS mDNS | bonjour-service discovers your phone's _adb-tls-pairing._tcp / _adb-tls-connect._tcp advertisements. Identical codepath across macOS, Linux, and Windows — no dns-sd / avahi-browse / Bonjour forking. |
| 🧰 Zero global installs | Script self-bootstraps qrcode and bonjour-service into its own node_modules/ on first run. adb (Android platform-tools) is the only system prerequisite. |
Ask Claude like this
💬 "pair my phone over wifi" 💬 "connect android over wifi" 💬 "set up wireless adb" 💬 "scan QR to connect phone"
Or just run the slash command: /adb-connect:pair.
How it compares to adb pair / adb connect by hand
The manual flow is: enable Wireless debugging → tap "Pair device with pairing code" → read the 6-digit code + IP:port off the phone → type them into a terminal → run adb pair IP:PORT CODE → read yet another IP:port from the Wireless debugging screen → adb connect IP:PORT.
adb-connect collapses that into: run /adb-connect:pair, tap "Pair device with QR code", aim phone at screen. Your laptop discovers everything over mDNS.
One-liner: Every skill from android/skills, mirrored and split so you install only what you want. Install:
/plugin install <name>@premex-plugins(pick from the table)
Google publishes open-standard agent skills covering the hard parts of modern Android development. We mirror, split, and auto-update the catalog so each skill is an individually installable plugin.
Available plugins
| Plugin | What it does for you |
|---|---|
| 🛠️ android-agp-9-upgrade | Migrates your project to Android Gradle Plugin 9 — breaking changes, built-in Kotlin, KSP/KAPT, the works. |
| 🎨 android-migrate-xml-views-to-jetpack-compose | Step-by-step XML → Jetpack Compose migration, theme mapping and View interop included. |
| 🧭 android-navigation-3 | Jetpack Navigation 3 recipes: deep links, multiple backstacks, scenes, Hilt/ViewModel integration, returning results. |
| 🪓 android-r8-analyzer | Finds redundant R8/Proguard keep rules and overly broad package-wide rules. Slims your APK. |
| 💳 android-play-billing-library-version-upgrade | Any legacy Google Play Billing Library version → latest stable, with migration logic pre-mapped. |
| 📱 android-edge-to-edge | Fixes status/nav bar overlap, IME insets, and system bar legibility — all the adaptive UI gotchas. |
Install examples
/plugin install android-edge-to-edge@premex-plugins
/plugin install android-navigation-3@premex-plugins
# …or any other android-* plugin from the list above🔄 Why install ours instead of cloning upstream?
A GitHub Actions workflow in this repo pulls android/skills every day, splits each SKILL.md into its own plugin, regenerates the marketplace manifest, and opens an auto-merging PR if anything changed. Upstream ships a new skill → a new plugin lands in your next /plugin marketplace update. Zero maintenance on our side or yours.
Why split? Claude Code currently locks skill toggling to the plugin level — one-plugin-per-skill is the only way to let you activate skills individually.
Google's new android CLI is an agent-first replacement for the old sdkmanager / avdmanager / adb toolchain — ~70% fewer tokens and ~3x faster. This plugin gets it onto your machine (and your CI runners), keeps it fresh forever, and hands off to Google's bundled skill once setup is done.
| Ships with | What you get |
|---|---|
| 🌱 android-cli-setup skill | One-time install of the android CLI into ~/.local/bin (no sudo needed), runs android init to deposit Google's official android-cli skill into ~/.claude/skills/, hands off. |
| 🔁 SessionStart hook | Background refresh throttled to once per 24h — your CLI and bundled skill stay current without you ever running android update manually. |
| ⚙️ android-cli-ci skill | Working reference workflows for GitHub Actions, GitLab CI, CircleCI, Bitrise, Jenkins, Buildkite, and self-hosted runners — plus a side-by-side migration guide from sdkmanager + cmdline-tools setups you probably have today. |
| 🛠️ Slash commands | /android-cli-status, /android-cli-update, /android-cli-reset for inspection and manual control. |
/plugin install android-cli@premex-plugins💬 "set up the android CLI on my laptop" → plugin bootstraps, then Google's skill takes over. 💬 "migrate our GitHub Actions workflow away from sdkmanager" → CI skill with a ready-to-paste replacement.
One-liner: Talk to Claude like a human; it talks to Dependabot for you. Install:
/plugin install github-utils@premex-pluginsFull README: plugins/github-utils/README.md
Claude maps your intent to the right @dependabot command and posts it via the gh CLI. No more memorizing syntax, no more per-PR commenting.
Ask Claude like this
💬 "rebase all dependabot PRs" 💬 "ignore the major version on #123" 💬 "show ignore conditions for lodash"
One-liner: Analyze and fix Gradle module dependencies with the autonomousapps dependency-analysis-gradle-plugin — investigative, not blind. Install:
/plugin install gradle-dagp@premex-pluginsFull README: plugins/gradle-dagp/README.md
DAGP produces precise, structured advice about unused, misused, and misconfigured dependencies. But blindly piping that advice through fixDependencies can make a codebase worse, not better — promoting implementation to api leaks third-party types into every consumer, convention-plugin-sourced advice gets whack-a-moled into individual modules, and one mega-PR with 200 changes is unreviewable. This skill treats DAGP's output as a starting point for thinking.
What's in the box
| Ships with | What you get |
|---|---|
| 🧠 Investigative triage | Each advice category (unused remove, misused add, api promotion, demotion, redundant plugin, module advice) gets its own decision tree. implementation → api advice prompts a "should we actually be exposing this type?" conversation, not an auto-edit. |
| 🏗️ Convention-plugin awareness | Detects buildSrc / build-logic / namespaced local plugins. Groups repeated advice to spot convention plugins that are over-applying dependencies, and fixes upstream instead of per-consumer. |
| 📦 Batched PR plans | Splits fixes by advice type, module family, or blast radius. Keeps PRs small enough to review in ten minutes and small enough to bisect when something breaks. Convention-plugin changes are always isolated. |
| 🔼 Version guardrail | Checks the applied DAGP version against the latest stable and proposes the upgrade as its own PR before applying advice, so you're not fixing against outdated analysis. |
| 🐛 Upstream bug drafting | If advice is wrong and the build breaks, drafts a minimal-repro issue against autonomousapps/dependency-analysis-gradle-plugin — and shows it to you for approval before filing under your identity. |
Ask Claude like this
💬 "run DAGP on this repo and propose cleanup PRs" 💬 "
buildHealthis telling me to make okio api — should I?" 💬 "clean up unused dependencies across the feature modules" 💬 "fix our convention plugin — DAGP keeps flagging the same dep in every module"
Because good skills deserve distribution, and spinning up a Claude Code plugin marketplace is surprisingly cheap — a .claude-plugin/marketplace.json, a plugin.json per plugin, and you're in business. If you're building on top of Claude Code, consider publishing your own.
Open an issue. We're a small team with opinions, but useful suggestions land fast.
Marketplace wrapper and Premex-authored plugins are free to use. Third-party skills shipped here (e.g. android-skills) carry their own upstream licenses — see the plugin directory for details (Apache-2.0 for android-skills).
Built at Premex 🇸🇪.