📦

limrun-gradle

Name: limrun-gradle
Author: limrun-inc

Revisión del contenido r1 Riesgo alto ⚙️ Comandos externos🌐 Acceso a red🔑 Variables de entorno

Build Android Apps with Remote Gradle

Local Android builds require large toolchains and can vary across machines. This skill runs Gradle remotely, signs artifacts, and supports Play Store delivery.

Compatible con: Claude Codex Code(CC)

⚠️ 38 Deficiente

Maintain this Skill? Claim it ⚠️ 38 Deficiente

Detente y solicita confirmación antes de instalar.

Revisa el plan y obtén el consentimiento explícito del usuario antes de modificar archivos.

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

Review the Skillstore skill "limrun-gradle" from https://skillstore.io/skills/limrun-inc-limrun-gradle.md and its manifest at https://skillstore.io/api/skills/limrun-inc-limrun-gradle/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/limrun-inc-limrun-gradle.md Manifest firmado GET /api/skills/limrun-inc-limrun-gradle/manifest Lockfile firmado GET /api/skills/limrun-inc-limrun-gradle/lockfile

Pruébalo

Usando "limrun-gradle". Build the current Android project as a debug APK.

Resultado esperado:

The remote build succeeded. The debug APK was uploaded as mobile-debug.apk and is ready for installation.

Usando "limrun-gradle". Create a signed release bundle for the existing Play listing.

Resultado esperado:

The release bundle was signed with the approved upload key. The artifact is available as mobile-release.aab.

Usando "limrun-gradle". Publish the approved Expo Android release.

Resultado esperado:

The package and next version code were resolved. Publication is awaiting confirmation with the selected artifact and signing identity.

Auditoría de seguridad

Riesgo alto

v1 • 9/9/2026 Abrir el informe versionado

Of 104 static findings, 102 are false positives caused by Markdown backticks, ordinary documentation, or defensive secret references. Two credential-handling findings are confirmed, and semantic review identified remote source transfer, signing-key escrow, password exposure, and direct Play Store publication.

Archivos escaneados

232

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (6)

Alto

SKILL.md:170

Credential JSON file

lim gradle build . --sign --upload-to-playstore --playstore-service-account sa.json --auto-version-c

The documented command sends a service-account JSON credential to Limrun for Play Store publishing. Uploading a reusable cloud credential to a third-party service is a real high-impact secret-handling risk.

Alto

SKILL.md:131

Java keystore files

--keystore upload.jks --keystore-password "$KS_PASS" \

The documented command sends an upload keystore and both passwords to Limrun, with passwords supplied through process arguments. This exposes signing material remotely and may expose passwords locally.

Alto

SKILL.md:105-107 SKILL.md:136-140

Signing Keys May Be Escrowed by the Provider

Default signing creates an organization key on Limrun, while the save-key option escrows a user-provided key. This transfers long-lived signing authority.

The instructions explicitly describe generated and user-provided signing keys being escrowed for later builds.

Alto

SKILL.md:129-133

Signing Passwords Are Passed Through Command Arguments

The example places keystore and key passwords in process arguments. Other local users, process monitors, or command logs may capture these secrets.

The command directly includes password variables as argument values, a known exposure channel despite the later environment-variable alternative.

Alto

SKILL.md:162-170

Workflow Can Publish Directly to Google Play

The documented command performs a production marketplace upload without requiring a separate confirmation step. A mistaken invocation can release an unintended artifact.

The source states that the build publishes the signed release directly and shows a command that performs the upload.

Medio

SKILL.md:10-12

Project Source Is Sent to a Remote Service

The workflow syncs the current project to Limrun infrastructure. Proprietary code or unintentionally included files therefore leave the local environment.

The source explicitly states that the command syncs project sources to a remote Gradle sandbox.

Factores de riesgo

⚙️ Comandos externos (50)

🌐 Acceso a red (1)

SKILL.md:187

🔑 Variables de entorno (1)

SKILL.md:26

Auditado por: codex

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

https://skillstore.io/skills/limrun-inc-limrun-gradle/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/limrun-inc-limrun-gradle/security.svg)](https://skillstore.io/skills/limrun-inc-limrun-gradle?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/limrun-inc-limrun-gradle?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/limrun-inc-limrun-gradle/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/limrun-inc-limrun-gradle.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citas académicas (APA · BibTeX · CFF)

Cita APA

limrun-inc. (2026). limrun-gradle security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/limrun-inc-limrun-gradle/audits/1

Cita BibTeX

@techreport{limrun-inc-limrun-inc-limrun-gradle-2026,
  author = {limrun-inc},
  title = {limrun-gradle security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/limrun-inc-limrun-gradle/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "limrun-gradle security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "limrun-inc"
date-released: "2026-09-09"
url: "https://skillstore.io/skills/limrun-inc-limrun-gradle/audits/1"
identifiers:
  - type: other
    value: "skillstore:limrun-inc-limrun-gradle:audit:1"
    description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

Build Without Android Studio

Produce a debug APK from a development machine, container, or CI environment without installing the Android SDK.

Test Cross-Platform Android Builds

Build React Native or Expo Android projects remotely and deliver an APK for emulator testing.

Prepare a Store Release

Create a signed AAB, manage version codes, and publish an approved artifact to Google Play.

Prueba estos prompts

Build a Debug APK

Build the Android project in {project_path} remotely. Return the artifact location and summarize any build errors.

Run a Specific Gradle Task

Build {project_path} with Gradle task {task}. Use project root {gradle_root}, fix failures, and rebuild until successful.

Create a Signed Release

Create a signed release AAB for {application_id}. Use the approved signing key and upload the artifact as {asset_name}.

Publish an Approved Release

Publish {project_path} using {credential_method}. Select a free version code, report the package and artifact, then request confirmation before publishing.

Mejores prácticas

Review the upload scope before syncing proprietary projects or force-including ignored files.
Use protected environment variables or a credential manager for passwords and access tokens.
Confirm the package, version code, track, artifact, and signing identity before publishing.

Evitar

Do not commit keystores, service-account files, passwords, or access tokens to the project.
Do not publish a release before verifying the intended application identifier and version code.
Do not force-sync ignored files without checking them for secrets and unnecessary artifacts.

Preguntas frecuentes

Does this require Android Studio?

No. The Gradle wrapper and Android toolchain run in a remote Limrun sandbox.

Which project types are supported?

The workflow supports native Android, React Native, and Expo projects that can produce Android artifacts.

Can it build both APK and AAB files?

Yes. Choose the appropriate Gradle task or use signing options for a release AAB.

Where does the source code go?

Selected project files are synchronized to Limrun infrastructure for the remote build.

How are signing keys handled?

Limrun can generate an organization key or receive a user-provided key. Key escrow requires careful approval and governance.

Can it publish directly to Google Play?

Yes. Publishing requires approved Play credentials, an existing listing, a unique version code, and explicit release confirmation.

Detalles del desarrollador

Autor

limrun-inc

Licencia

MIT

Revisión de Skillstore

Aviso de versión

El autor no declaró una versión.

Repositorio

https://github.com/limrun-inc/skills/tree/6f7e4c48f6b0c36a6c75b62dac9082df3b844e79/skills/limrun-gradle

Ref.

367c7bb3962eb92a1b87fc08b2947aeda00cd51d

Actualidad del mantenimiento

9/9/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📄 SKILL.md