Skills limrun-xcode
๐Ÿ“ฆ

limrun-xcode

Content revision r1 Critical โš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Build Apple Apps on Remote Xcode

Local Apple builds require macOS and Xcode infrastructure. This skill sends projects to Limrun for remote builds, simulator installation, signing, previews, and App Store uploads.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "limrun-xcode" from https://skillstore.io/skills/limrun-inc-limrun-xcode.md and its manifest at https://skillstore.io/api/skills/limrun-inc-limrun-xcode/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "limrun-xcode". Build the default project in Debug and install it on the attached simulator.

Expected outcome:

  • The remote Debug build completed for scheme MyApp.
  • The application was installed and relaunched on the attached simulator.

Using "limrun-xcode". Create a signed release IPA and keep the artifact for fourteen days.

Expected outcome:

  • Release IPA signing passed the server verification.
  • The artifact upload completed with a fourteen-day retention period.

Using "limrun-xcode". Upload the approved release to App Store Connect and wait for its status.

Expected outcome:

  • App Store Connect accepted the upload and is processing build 142.
  • No retry was started because delivery succeeded.

Security Audit

Critical
v1 โ€ข 8/21/2026 Open versioned report

Most static alerts are false positives caused by Markdown backticks, command fences, identifiers, and a documented URL. Confirmed risks involve soliciting an API key and transmitting Apple signing certificates and passwords to a remote build service. Semantic review also identified unpinned global package installation, source-code upload, and privileged App Store credential transfer.

1
Files scanned
333
Lines analyzed
1
Review items
0
False positives ignored

Confirmed security concerns (6)

Critical
Privileged Apple Credentials Sent to Remote Service
The cloud workflow supplies an App Store Connect private key to a third-party service with authority to sign and upload application releases.
The cited commands pass the private key path and identifiers to remote signing and App Store upload operations.
High
Certificate/key files
--certificate-p12 dist.p12 --certificate-password "$P12_PASSWORD" \
The remote build command supplies a signing certificate and its password to Limrun. Process-argument exposure or remote-service compromise could disclose signing credentials.
High
Certificate/key files
--certificate-p12 dist.p12 --certificate-password "$P12_PASSWORD" \
The remote build command supplies a signing certificate and its password to Limrun. Process-argument exposure or remote-service compromise could disclose signing credentials.
High
Certificate/key files
--certificate-p12 dist.p12 --certificate-password "$P12_PASSWORD" \
The remote build command supplies a signing certificate and its password to Limrun. Process-argument exposure or remote-service compromise could disclose signing credentials.
High
Project Source Uploaded to Third-Party Infrastructure
The skill directs the agent to sync project sources to Limrun infrastructure and continue remote execution until the application works.
Lines 10 through 15 explicitly state that sources are synced to remote Xcode and built there.
High
Unpinned Global Package Installation
The skill directs installation of the latest globally published lim npm package without version or integrity controls.
Line 23 gives a global npm installation command with no version pin, checksum, or package provenance check.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Generic API/secret keys
`LIM_API_KEY` is wrong; ask the user to run `lim login` or provide a key.
The instruction tells the agent to ask the user to provide LIM_API_KEY after an authentication error. This can cause disclosure of an API credential in chat.
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/limrun-inc-limrun-xcode.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

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

BibTeX citation

@techreport{limrun-inc-limrun-inc-limrun-xcode-2026, author = {limrun-inc}, title = {limrun-xcode security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/limrun-inc-limrun-xcode/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-xcode security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "limrun-inc" date-released: "2026-08-21" url: "https://skillstore.io/skills/limrun-inc-limrun-xcode/audits/1" identifiers: - type: other value: "skillstore:limrun-inc-limrun-xcode:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Low
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Build iOS Without Local Xcode

Compile and install an Apple application from Linux, Windows, macOS, a virtual machine, or a container.

Automate Remote Apple Builds

Run repeatable Debug or Release builds for projects, workspaces, XcodeGen, React Native, and Expo repositories.

Prepare and Deliver Signed IPAs

Create signed device artifacts and upload approved releases to storage or App Store Connect.

Try These Prompts

Build a Basic Xcode Project
Build the Apple project in [project path] with Limrun. Use the default scheme and report the build result and artifact location.
Build a Selected Workspace
Build [workspace] with scheme [scheme] and configuration [Debug or Release]. Attach a remote simulator only when installation or interaction is required.
Create a Signed Device IPA
Create a signed IPA for [bundle identifier] using [cloud or manual] signing. Ask before transmitting credentials, then report the secure download location.
Deliver an App Store Build
Build [project] for App Store Connect, increment the build number, and sign with least-privileged credentials. Upload after my explicit confirmation and report processing status.

Best Practices

  • Confirm the source path, scheme, workspace, configuration, and target before starting a remote build.
  • Use interactive login and least-privileged, short-lived signing credentials whenever possible.
  • Request explicit approval before source upload, credential transmission, artifact publication, or App Store delivery.

Avoid

  • Do not paste API keys, certificate passwords, private keys, or signed access URLs into conversation history.
  • Do not use this skill for Bazel workspaces or local simulator automation.
  • Do not retry an accepted App Store upload while Apple is still processing it.

Frequently Asked Questions

Do I need macOS or local Xcode?
No. The project is synchronized to Limrun and built on remote Xcode infrastructure.
Does this skill support Bazel workspaces?
No. Use the limrun-xcode-bazel skill for Bazel-based Apple projects.
Can it interact with the running simulator?
It can install and relaunch builds. Use limrun-ios-simulator for taps, typing, screenshots, recordings, and element inspection.
Which project types are supported?
It supports Xcode projects, workspaces, XcodeGen specifications, React Native native builds, and Expo native builds.
How are signed IPA files created?
The skill supports Apple cloud signing or manual signing with a certificate and matching provisioning profiles.
Can it upload directly to App Store Connect?
Yes. It can sign and upload an approved build using an App Store Connect API key.

Developer Details

Author

limrun-inc

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

4ec79c4a51e6b1df1b440d2b6ae810d3f433a601

Maintenance freshness

8/22/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from limrun-inc

View all
View all