Agent skill · Audited from source
asc-xcode-build
skill · rudrankriyam/app-store-connect-cli-skillsMIT licenceAudited 14 Nov 2026 · source 4f485fc425b4
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 4f485fc425b4 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Build, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release…
Cite
Cite this page
ModelsAtlas. “asc-xcode-build (rudrankriyam/app-store-connect-cli-skills)”. Retrieved 14 Nov 2026. https://modelsatlas.com/skills/rudrankriyam/asc-xcode-build
Trust audit
Audit 0.4.1 · source read 14 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 4f485fc425b4 · 14 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherrudrankriyam GitHub organizationOwner of the repository this skill is read from
- Source folderrudrankriyam/app-store-connect-cli-skills/skills/asc-xcode-buildThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict4f485fc425b4A new audit runs when the source changes
- Repository statusNot archivedLast push 7 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Build, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release…
--- name: asc-xcode-build description: Build, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing. --- # Xcode build and export Use this skill when you need to build an app from source and prepare it for App Store Connect. Prefer `asc xcode archive` and `asc xcode export` over raw `xcodebuild` recipes when they fit the project. ## Preconditions For a prepared xtool package on Linux, use [portable iOS builds](references/portable-ios.md) instead of the Xcode commands below. That workflow has a narrower project and signing contract. - Xcode and command line tools are installed. - Signing identity and provisioning profiles are available, or automatic signing is enabled. - App Store Connect auth is configured when upload or build lookup is needed. ## Manage version and build numbers ```bash asc xcode version view asc xcode version edit --version "1.3.0" --build-number "42" asc xcode version edit --next-build-number --app "APP_ID" --platform IOS asc xcode version bump --type build asc xcode version bump --type patch asc xcode version bump --type build --next-build-number --app "APP_ID" --platform IOS ``` Use `--project-dir "./MyApp"` when not running from the project root. Use `--project "./MyApp/App.xcodeproj"` when the directory contains multiple projects. Use `--target "App"` and `--configuration "Release"` for deterministic reads and writes in multi-target or multi-configuration projects. To avoid low build-number rejects, resolve and apply the remote-safe build number in one command: ```bash asc xcode version edit --next-build-number --app "APP_ID" --platform IOS --output json ``` Version mutations validate the full change before writing and return structured output identifying the configurations and files changed. The editor follows recursive xcconfig includes and preserves unrelated project and xcconfig content. Use `asc builds next-build-number` separately when you only want to inspect the remote-safe value without changing the project. Version commands read project and xcconfig settings without launching Xcode. When those settings cannot resolve the version values, the default `--xcodebuild-settings-lookup auto` falls back to `xcodebuild -showBuildSettings` and warns on stderr. Use `--xcodebuild-settings-lookup never` in automation that must not launch Xcode implicitly. ## Compile without archiving Use `asc xcode build` for an ordinary simulator, device, or CI validation build. Provide exactly one project or workspace and a scheme. ```bash asc xcode build \ --project "App.xcodeproj" \ --scheme "App" \ --destination "platform=iOS Simulator,name=iPhone 17 Pro Max,OS=27.0" \ --no-code-signing \ --result-bundle-path ".asc/artifacts/App.xcresult" \ --output json ``` When `--derived-data-path` is omitted, asc uses a stable cache outside the source checkout. The result-bundle destination must not already exist. Xcode logs go to stderr and the structured result goes to stdout. ## Preferred iOS/tvOS/visionOS build flow ### 1. Archive with asc ```bash asc xcode archive \ --workspace "App.xcworkspace" \ --scheme "App" \ --configuration Release \ --clean \ --archive-path ".asc/artifacts/App.xcarchive" \ --xcodebuild-flag=-destination \ --xcodebuild-flag=generic/platform=iOS \ --output json ``` Use `--project "App.xcodeproj"` instead of `--workspace` for project-only apps. ### 2. Export with asc By default, `asc xcode export` generates App Store Connect export options with automatic signing. It uses a local export destination unless `--wait` is set, in which case it uses direct upload: ```bash asc xcode export \ --archive-path ".asc/artifacts/App.xcarchive" \ --ipa-path ".asc/artifacts/App.ipa" \ --xcodebuild-flag=-allowProvisioningUpdates \ --output json ``` Generate a plist separately when it needs review, reuse, or manual signing: ```bash asc xcode export-options generate \ --archive-path ".asc/artifacts/App.xcarchive" \ --output-path ".asc/ExportOptions.plist" \ --output json ``` For manual signing, add `--signing-style manual` and optionally `--team-id "TEAM_ID"`. Existing files require `--overwrite`. For an IPA installable on registered devices, use Xcode's current `release-testing` method. The older `ad-hoc` spelling is deprecated by Xcode and is not accepted by `asc`: ```bash asc xcode export \ --archive-path ".asc/artifacts/App.xcarchive" \ --ipa-path ".asc/artifacts/App.ipa" \ --method release-testing \ --signing-style manual \ --team-id "TEAM_ID" \ --output json ``` Generate the release-testing plist separately when it needs review or reuse: ```bash asc xcode export-options generate \ --archive-path ".asc/artifacts/App.xcarchive" \ --method release-testing \ --signing-style manual \ --team-id "TEAM_ID" \ --output-path ".asc/ExportOptions.release-testing.plist" \ --output json ``` `release-testing` always exports locally and cannot be combined with `--wait`. An explicit `--export-options` plist cannot be combined with `--method`, `--signing-style`, or `--team-id`. For device/profile reconciliation, isolated signing, private publication, resumability, and live verification, use the `asc-ad-hoc-distribution` skill instead of assembling those stages manually. To upload directly through Xcode and wait for App Store Connect processing, omit `--export-options` and add `--wait`: ```bash asc xcode export \ --archive-path ".asc/artifacts/App.xcarchive" \ --ipa-path ".asc/artifacts/App.ipa" \ --wait \ --output json ``` ### 3. Upload or publish Upload an exported IPA: ```bash asc builds upload --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --wait ``` Distribute to TestFlight: ```bash asc publish testflight --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --group "GROUP_ID" --wait ``` Publish to the App Store: ```bash asc publ
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 4f485fc
git clone https://github.com/rudrankriyam/app-store-connect-cli-skills git -C app-store-connect-cli-skills checkout 4f485fc425b4
The author documents no install command, so this uses the repository directly. Our verdict covers commit 4f485fc425b4 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
4f485fc425b4
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/rudrankriyam/asc-xcode-build/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All automation skills →rorkai/app-store-connect-cli-skills
Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using `asc apps wall submit`. Use when the user says "submit to wall of apps", "add my app to the wall", or "wall-of-apps".
rorkai/app-store-connect-cli-skills
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.
rudrankriyam/app-store-connect-cli-skills
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.
rorkai/app-store-connect-cli-skills
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
rudrankriyam/app-store-connect-cli-skills
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
rorkai/app-store-connect-cli-skills
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names…
Add this badge to your README
[](https://modelsatlas.com/skills/rudrankriyam/asc-xcode-build/)
<a href="https://modelsatlas.com/skills/rudrankriyam/asc-xcode-build/"><img src="https://modelsatlas.com/skills/rudrankriyam/asc-xcode-build/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about asc-xcode-build
What does the asc-xcode-build skill do?
Is asc-xcode-build safe to install?
What can asc-xcode-build access on my machine?
How current is this page?
Sources
- github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/s — the audited source at commit 4f485fc425b4 and every finding aboveObserved · 14 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the asc-xcode-build skill do?
- Is asc-xcode-build safe to install?
- What can asc-xcode-build access on my machine?