SKILLEMALL.ai
GitHub ↗ RU Sign in

AD asc-xcode-build

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.

The skillemall take

Promises to automate Xcode builds, archiving, and iOS app export to App Store Connect and TestFlight with version management. Two modules in the files, no critical errors, code quality at 88, safety perfect. Process score drops to 48 though—commands either need tweaking or don't cover all scenarios end-to-end. No model runs, no sandbox tests, so behavior across Xcode versions stays opaque. Install if you already know asc-cli and your release pipeline; iOS newcomers should read Apple's docs first.

rorkai/app-store-connect-cli-skills Agent Skills author: rorkai 2 files body ≈ 2 046 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Build, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging.

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 96): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 48/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2046 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 227: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 11 items
    • +4Has examples (16 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.