# Build Bazel Mobile Apps on Limrun

Mobile Bazel builds require compatible workers, toolchains, and reliable authentication. This skill guides Limrun setup, remote builds, CI authentication, and installation on cloud simulators or emulators.

## Install

```bash
npx skillstore add limrun-inc/limrun-bazel
```

## Metadata

- Status: approved
- Slug: limrun-inc-limrun-bazel
- Skillstore revision: r1
- Version status: missing
- Tree hash: 219f0053d36544e9b1078d6de0c3dd4c1201c1c22ed0a100b887cb3c243fd640
- Author: limrun-inc
- GitHub username: limrun-inc
- License: MIT
- Repository: https://github.com/limrun-inc/skills/tree/1ed3b6bfb7272c8a4799f5ce724affaa93dc3132/skills/limrun-bazel
- Ref: 7f17813fb6af1acc7d8fd3fb5f05480f5be52783
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/limrun-inc-limrun-bazel
- Manifest: https://skillstore.pages.dev/api/skills/limrun-inc-limrun-bazel/manifest

## Capabilities

- Guide npm CLI installation and authentication through lim login or LIM\_API\_KEY.
- Configure eligible Bazel workspaces with lim bazel setup and identify missing Android module dependencies.
- Guide remote target builds using the Limrun configuration and persistent user build flags.
- Describe noninteractive CI setup using secret authentication and accepted dependency additions.
- Guide installation of built apps on Limrun iOS simulators and Android emulators.
- Troubleshoot credential helpers, worker capacity, toolchain dependencies, and regional cache behavior.

## Use Cases

- Build an iOS target remotely: Configure an existing Bazel Apple workspace for Limrun workers and install the simulator build on a Limrun iOS instance.
- Configure Android builds in CI: Prepare module dependencies, secret authentication, and noninteractive setup for Android Bazel builds on Limrun.
- Diagnose shared build failures: Check credential helper availability, worker capacity errors, missing toolchains, and regional cache behavior across team builds.

## Prompt Templates

### Check workspace readiness

```
Check whether this Bazel mobile workspace meets Limrun prerequisites. Report missing requirements and propose setup steps before making changes.
```

### Build and install an app

```
Configure Limrun for my Bazel target [target]. Build for [iOS simulator or Android emulator], then install the output on the matching Limrun instance.
```

### Prepare CI setup

```
Prepare Limrun CI steps for [target]. Use secret authentication, review proposed module additions, and explain noninteractive setup without exposing credentials.
```

### Diagnose a remote build failure

```
Diagnose this Limrun Bazel error: [error]. Check helper availability, authentication presence, dependencies, worker capacity, and regional cache behavior without printing secrets.
```

## Limitations

- Requires Bazel 8 or later, a root MODULE.bazel, and rules\_apple or rules\_android.
- Requires Limrun access and the npm CLI installation, version 0.44.0 or later, for the credential helper.
- Provides instructions only; external CLI, worker, and credential helper implementations are not included.
- Does not cover non-Bazel Android builds, legacy Xcode remote execution, or interactive app control.

## Best Practices

- Keep API keys in CI secret storage and check authentication presence without printing credential values.
- Review dependency additions before using noninteractive setup; inspect workspace changes after setup.
- Store custom flags in user.limrun.bazelrc and rerun setup after CLI upgrades or mobile rule changes.

## Anti Patterns

- Hand-editing generated files in .limrun instead of using setup or the user configuration file.
- Assuming a standalone CLI installation or an API key flag provides Bazel helper authentication.
- Assuming remote cache contents are shared across regions or omitting the Limrun build configuration.

## Security Audit

- Audited at: 2026-10-13T15:30:59.173\+00:00
- Summary: All 49 static findings are false positives from Markdown formatting, documented service authentication, or platform descriptions. No evidence found of credential exfiltration, malicious reconnaissance, or prompt injection. The workflow intentionally uses external packages, remote build workers, and cloud app installation; their implementations are not included for review.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0