SKILLEMALL.ai
GitHub ↗ RU Sign in

BC asc-cli-usage

Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.

The skillemall take

The skill documents App Store Connect CLI flags, output formats, and authentication. Files contain 2446 tokens of instructions without scripts or execution examples. Grade B, quality 83%, but process score only 59%—documentation exists but hasn't run on models or in sandbox.

No critical errors, linter passes. Wide platform support from Claude to DeepSeek. The skill works if the agent already knows ASC basics and needs CLI syntax reference. For someone new to App Store Connect, it reads dry and context-free. Install if your workflow already uses ASC and you need a command syntax cheat sheet.

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

Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery).

As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationSoftware 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
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
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: 1. 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 33, 36, 88): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 59/100

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

    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)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 190: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 75 items
    • +3Output format is stated explicitly

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