Skip to content
TrustedSkillsbeta
Back to all skills

Asc Submission Health

Checked
rudrankriyam·vlatest·devops·MIT

Asc Submission Health analyzes submitted content for potential issues like formatting errors or policy violations, ensuring a smoother review process.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rudrankriyam

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rudrankriyam/app-store-connect-cli-skills at 9a093fa521.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9a093fa521
Manifest
skills/asc-submission-health/SKILL.md
Scanned
4 files, 573 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, asc-submission-health, leverages the App Store Connect CLI to provide detailed health status information about app submissions. It can check if a submission is in review, approved, or rejected and retrieve associated metadata like build number and submission notes. This allows for proactive monitoring of app store submission processes.

When to use it

  • Automated Status Checks: Integrate into CI/CD pipelines to automatically verify submission status after deployment.
  • Proactive Issue Identification: Regularly check submission health to identify potential issues before they impact release schedules.
  • Troubleshooting Rejected Submissions: Quickly retrieve rejection reasons and associated notes from App Store Connect.
  • Release Coordination: Keep stakeholders informed about the progress of app submissions in real-time.

Key capabilities

  • Retrieves submission status (in review, approved, rejected).
  • Fetches build number for a given submission.
  • Accesses submission notes and metadata.

Example prompts

  • "What is the health status of my latest iOS app submission?"
  • "Can you tell me the build number associated with submission ID 12345?"
  • "Retrieve the rejection reason for submission ABC-XYZ."

Tips & gotchas

  • Requires authentication credentials configured for the App Store Connect CLI.
  • Submission IDs are required to retrieve specific submission details.