New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Triage Asc Issue

by rorkai in rorkai/App-Store-Connect-CLI

Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support.

MITAuto-check passedMobile

Install Triage Asc Issue

skills CLI
$ npx skills add rorkai/App-Store-Connect-CLI --skill triage-asc-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rorkai/App-Store-Connect-CLI triage-asc-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rorkai/App-Store-Connect-CLI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-asc-issue .claude/skills/triage-asc-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-asc-issue
GitHub stars
7.7k
Token cost
~831 tokens
SKILL.md length
407 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support.

  • Works in 5 steps: Fetch the live issue body, comments,… → Resolve the affected command through… → Reproduce reported behavior with the… → …
  • The user asks to audit
  • SKILL.md covers Read current evidence, Classify the outcome, Recommend or apply labels and Define implementation readiness, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Triage Asc Issue is an agent skill from rorkai/App-Store-Connect-CLI. Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support. Use when the user asks to audit, reproduce, classify, label, scope, prioritize, or decide whether an ASC CLI issue should be fixed or implemented.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Mobile, covering App store release. It works with App Store Connect and GitHub. The repository describes itself as: Fast, scriptable CLI for the App Store Connect API. Automate TestFlight, builds, submissions, signing, analytics, screenshots, subscriptions, and more. The licence is MIT.

When your agent uses it

  • The user asks to audit
  • Decide whether an ASC CLI issue should be fixed

Example prompts

  • “/triage-asc-issue”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Fetch the live issue body, comments, labels, linked PRs, and referenced documentation.
  2. Resolve the affected command through current --help, source, tests, and recent history. Do not infer support from an old command name.
  3. Reproduce reported behavior with the current built or installed CLI when safe.
  4. For API claims, verify the exact method and endpoint in docs/openapi/latest.json; use the sosumi.ai documentation mirror for explanatory…
  5. Check whether the report is already fixed on current origin/main, duplicated, unsupported by the public API, or blocked by Apple/platform…

What it can do on your machine

Read from SKILL.md and the folder at commit 6d32f41. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage Asc Issue loads about 831 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 407 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~831

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rorkai/App-Store-Connect-CLI at commit 6d32f41, republished under its MIT licence (© rorkai). 407 words, ~831 tokens.

Download SKILL.mdSave it as .claude/skills/triage-asc-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
triage-asc-issue
description
Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support. Use when the user asks to audit, reproduce, classify, label, scope, prioritize, or decide whether an ASC CLI issue should be fixed or implemented.

Triage an ASC CLI issue

Produce a current, evidence-backed verdict and proposed repository labels. Apply label changes only when authorized under AGENTS.md; a read-only triage ends with recommendations.

Read current evidence

  1. Fetch the live issue body, comments, labels, linked PRs, and referenced documentation.
  2. Resolve the affected command through current --help, source, tests, and recent history. Do not infer support from an old command name.
  3. Reproduce reported behavior with the current built or installed CLI when safe.
  4. For API claims, verify the exact method and endpoint in docs/openapi/latest.json; use the sosumi.ai documentation mirror for explanatory context.
  5. Check whether the report is already fixed on current origin/main, duplicated, unsupported by the public API, or blocked by Apple/platform behavior.

Follow AGENTS.md for parallel reads and serialized writes. Live reproductions require authority for mutations and cleanup, even on disposable resources; confirm dry runs are side-effect-free.

Classify the outcome

Choose one primary verdict:

  • Confirmed bug with a reproducible expected-versus-actual mismatch.
  • Valid enhancement with a supported and coherent API or client-side design.
  • Question requiring clarification or support guidance.
  • Already fixed, duplicate, not reproducible, unsupported, or platform-limited.

Separate urgency from implementation size. Explain user impact, blast radius, workaround, compatibility risk, and the smallest proof needed for completion.

Recommend or apply labels

Recommend one type, priority, and difficulty from AGENTS.md's buckets using the meanings in CONTRIBUTING.md. Apply them only when authorized.

For authorized label updates, remove conflicting labels and add the selected replacements, then verify the resulting buckets. If evidence is incomplete, mark the recommendation provisional and identify the missing evidence; uncertainty alone does not establish low urgency or easy implementation.

Show full SKILL.md (139 more words)Show less

Define implementation readiness

When the issue is actionable, provide:

  1. Proposed command and UX shape.
  2. API endpoint or explicit client-side behavior.
  3. Files and shared surfaces likely affected.
  4. RED-GREEN test plan and black-box exit/output cases.
  5. Safe live verification and cleanup plan.
  6. Compatibility or deprecation requirements.

If implementation is requested, continue with $develop-asc-change in an isolated branch or worktree. Report the requested implementation and validation as complete when finished, with PR and merge gates separately. Do not close the issue or claim it resolved until merged and verified; closure still requires authority.

Automation contract

A recurring issue-triage automation may classify new or incompletely labeled issues and report actionable findings. Apply labels or post comments only within its persisted write authority. It must not implement code or close issues without explicit authorization, and labels must follow evidence.

© rorkai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/triage-asc-issue of rorkai/App-Store-Connect-CLI.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 6d32f41

Compare with similar skills

Triage Asc Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage Asc Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Asc Issue this skillrorkai/App-Store-Connect-CLI7.7k—~831Automated safety check: PassMIT
iOS App Store SubmitZestfulPulse/ios-app-store-submit142—~4.7kAutomated safety check: PassMIT
Release MapleMaplePrivacyLabs/Maple102—~5.5kAutomated safety check: PassMIT
App Store Release Flowrorkai/app-store-connect-cli-skills1.1k2 repos~2kAutomated safety check: PassMIT
App Store Submission Healthrorkai/app-store-connect-cli-skills1.1k2 repos~2.2kAutomated safety check: PassMIT
App Store Preflight Skillstruongduy2611/app-store-preflight-skills1.4k—~1.4kAutomated safety check: PassMIT

Similar skills

  • iOS App Store Submit

    ZestfulPulse/ios-app-store-submit

    Build, sign, and submit a Flutter/iOS app to the App Store Connect — covers Xcode archive/export, code signing (including headless-Mac keychain workarounds), the asc CLI for App Store Connect…

    142 GitHub stars~4.7k tokensUpdated 9 days ago
    MobileAuto-check passed

  • Release Maple

    MaplePrivacyLabs/Maple

    Prepare, publish, monitor, and verify a Maple release from current master.

    102 GitHub stars~5.5k tokensUpdated yesterday
    MobileAuto-check passed

  • App Store Release Flow

    rorkai/app-store-connect-cli-skills

    Orchestrates App Store releases with the asc CLI: staging a version, uploading or building, publishing and submitting for review, with dry-run and confirmation gates.

    1.1k GitHub starsUsed in 2 repos~2k tokens
    MobileAuto-check passed

  • App Store Submission Health

    rorkai/app-store-connect-cli-skills

    Diagnoses why an App Store version cannot be submitted or is stuck in review, using the asc CLI for validation, repair routing, status checks and retry decisions.

    1.1k GitHub starsUsed in 2 repos~2.2k tokens
    MobileAuto-check passed

  • App Store Preflight Skills

    truongduy2611/app-store-preflight-skills

    Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission.

    1.4k GitHub stars~1.4k tokensUpdated 4 mo ago
    MobileAuto-check passed

  • Asc Localize Metadata

    CamilleScholtz/swmpc

    Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI.

    239 GitHub starsUsed in 5 repos~2.8k tokens
    MobileAuto-check passed

More from rorkai/App-Store-Connect-CLI

  • Release Asc CLI

    rorkai/App-Store-Connect-CLI

    Publish and verify a new release of the App-Store-Connect-CLI repository.

    7.7k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Develop Asc Change

    rorkai/App-Store-Connect-CLI

    Design, implement, and verify behavior changes in App-Store-Connect-CLI.

    7.7k GitHub stars~832 tokensUpdated yesterday
    Auto-check passed

  • Audit Asc PR

    rorkai/App-Store-Connect-CLI

    Audit App-Store-Connect-CLI pull requests end to end and fix concrete defects when authorized.

    7.7k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Review Wall Of Apps PRs

    rorkai/App-Store-Connect-CLI

    Audit maintainer-side Wall of Apps pull requests in App-Store-Connect-CLI.

    7.7k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Sync Asc Skills

    rorkai/App-Store-Connect-CLI

    Check rorkai/app-store-connect-cli-skills against the current ASC CLI surface and correct proven drift when authorized.

    7.7k GitHub stars~782 tokensUpdated yesterday
    Auto-check passed

  • Watch Asc PR

    rorkai/App-Store-Connect-CLI

    Recheck an in-progress App-Store-Connect-CLI pull request for new review feedback, CI results, head changes, and merge readiness.

    7.7k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Triage Asc Issue

What does Triage Asc Issue do?

Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support. Triage Asc Issue is an agent skill from rorkai/App-Store-Connect-CLI. Triage App-Store-Connect-CLI GitHub issues against current code, CLI behavior, and App Store Connect API support.

When should I use Triage Asc Issue?

Triage Asc Issue fits situations like: the user asks to audit; decide whether an ASC CLI issue should be fixed.

How do I install Triage Asc Issue in Claude Code?

Run `npx skills add rorkai/App-Store-Connect-CLI --skill triage-asc-issue -a claude-code`. Or copy the skill folder (.agents/skills/triage-asc-issue in rorkai/App-Store-Connect-CLI) into .claude/skills/triage-asc-issue in your project. Claude Code loads it when a task matches its description.

How do I install Triage Asc Issue in Codex?

Run `npx skills add rorkai/App-Store-Connect-CLI --skill triage-asc-issue -a codex`. Or copy the skill folder (.agents/skills/triage-asc-issue in rorkai/App-Store-Connect-CLI) into .agents/skills/triage-asc-issue in your project. Codex loads it when a task matches its description.

Can I use Triage Asc Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rorkai/App-Store-Connect-CLI --skill triage-asc-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-asc-issue, .gemini/skills/triage-asc-issue, .github/skills/triage-asc-issue and .opencode/skills/triage-asc-issue in your project.

What does Triage Asc Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Triage Asc Issue is instructions for the agent only.

Does Triage Asc Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Triage Asc Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Triage Asc Issue use?

Triage Asc Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage Asc Issue use?

About 831 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triage Asc Issue?

Skills that share tags, products or a category with Triage Asc Issue: iOS App Store Submit (ZestfulPulse/ios-app-store-submit, 142 stars), Release Maple (MaplePrivacyLabs/Maple, 102 stars), App Store Release Flow (rorkai/app-store-connect-cli-skills, 1.1k stars) and App Store Submission Health (rorkai/app-store-connect-cli-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Asc Issue?

rorkai (a GitHub organization) maintains it in rorkai/App-Store-Connect-CLI, which has 7,715 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.

Source: rorkai/App-Store-Connect-CLI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.