Skip to content
TrustedSkillsbeta
Back to all skills

Asc Metadata Sync

Checked
rudrankriyam·vlatest·other·MIT

Asc Metadata Sync automatically synchronizes metadata across different platforms, ensuring consistency and streamlining workflows for seamless data management.

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-metadata-sync -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.

Scanned
1 file, 142 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

The asc-metadata-sync skill automates the synchronization of metadata between an application and App Store Connect. It ensures that app details, such as descriptions, icons, and other relevant data, remain consistent across platforms.

When to use it

  • When updating app information on multiple platforms simultaneously.
  • Before submitting a new version of an app for review to ensure metadata is up-to-date.
  • When maintaining consistency between local development environments and App Store Connect.

Key capabilities

  • Synchronizes app metadata with App Store Connect.
  • Automates repetitive tasks related to metadata management.
  • Reduces the risk of human error during updates.

Example prompts

  • "Sync my app's metadata with App Store Connect."
  • "Update the app description and icon in App Store Connect based on local files."
  • "Ensure all metadata fields are consistent between my development environment and App Store Connect."

Tips & gotchas

  • Ensure you have valid credentials for App Store Connect before using this skill.
  • Metadata conflicts may arise if changes are made manually on both ends; always verify synchronization results.