Fastlane
Analysis
This Fastlane skill is mostly purpose-aligned, but it asks agents to handle Apple/App Store credentials and run commands that can upload, submit, release, or modify apps and testers.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
fastlane deliver --ipa "/path/to/App.ipa" --submit_for_review ... `--automatic_release` | Release automatically after approval | `--force` | Skip HTML preview verification | `--reject_if_possible` | Reject current version before uploading
The skill documents direct CLI actions and flags that can submit, release, force, or replace App Store versions, but the visible instructions do not add explicit user-confirmation or safety checks before those high-impact actions.
brew install fastlane ... sudo gem install fastlane -NV
The documented install paths pull an external Fastlane package, and the RubyGems option uses sudo. This is expected for a Fastlane CLI skill, but it is still a supply-chain and privilege point users should notice.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
export APP_STORE_CONNECT_API_KEY_KEY_FILEPATH="/path/to/AuthKey_XXXXXXXXXX.p8" ... export FASTLANE_PASSWORD="app-specific-password" ... `MATCH_PASSWORD` | Encryption password for match certificates repo
The skill instructs users to configure App Store Connect private keys, Apple ID/app-specific passwords, and signing repository secrets. These are powerful credentials, and the registry metadata declares no required credentials or environment variables.
