Skip to content
TrustedSkillsbeta
Back to all skills

Auditing Appstore Readiness

Checked
tristanmanchester·vlatest·other

This skill audits your app’s readiness for the Apple App Store, ensuring compliance and minimizing potential rejection issues.

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 tristanmanchester/agent-skills --skill auditing-appstore-readiness -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

tristanmanchester

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 tristanmanchester/agent-skills at 3323bc919a.

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

Commit
3323bc919a
Manifest
auditing-appstore-readiness/SKILL.md
Scanned
5 files, 493 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 assesses an app's readiness for submission to the Apple App Store. It identifies potential issues related to metadata, screenshots, build settings, and compliance with App Store guidelines. The tool provides a detailed report outlining areas needing attention before submitting your application.

When to use it

  • Before submitting a new app to the App Store.
  • When preparing an update for an existing app.
  • To proactively identify potential rejection reasons from Apple.
  • As part of a quality assurance process for mobile applications.

Key capabilities

  • Metadata validation (app name, description, keywords)
  • Screenshot compliance check
  • Build settings verification
  • App Store guideline adherence assessment

Example prompts

  • "Audit my app's App Store readiness."
  • "Check the metadata for my iOS application and identify any issues."
  • "Can you review my app's build settings to ensure they meet Apple’s requirements?"

Tips & gotchas

The skill requires access to your app project files or a detailed description of its configuration. Results should be interpreted as suggestions; always refer to the official Apple App Store guidelines for definitive compliance.