Skip to content
TrustedSkillsbeta
Back to all skills

Asc Metadata Sync

Checked
rudrankriyam·vlatest·other·MIT

This skill automatically synchronizes Asc metadata across multiple platforms, ensuring consistent data and streamlining workflows.

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-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/asc-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-metadata-sync/SKILL.md
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

The asc-metadata-sync skill synchronizes metadata between AI agents and external systems, ensuring consistent data representation across platforms. It facilitates seamless integration by automatically updating agent profiles with relevant attributes from connected sources.

When to use it

  • Maintain up-to-date agent profiles when integrating multiple communication channels.
  • Ensure consistency of user data across different AI agent instances in a distributed system.
  • Automate metadata updates during periodic synchronization cycles with external databases.
  • Resolve data discrepancies between local agent states and remote service records.

Key capabilities

  • Automatic bidirectional metadata synchronization
  • Real-time profile attribute updates
  • Cross-platform data consistency enforcement
  • External system integration support

Example prompts

"Sync my current user profile metadata to the connected ASC database." "Update all linked AI agents with the latest contact information from our CRM." "Synchronize project metadata across three different agent instances to ensure uniformity."

Tips & gotchas

Ensure external systems have proper API access permissions before initiating synchronization. Verify data format compatibility between local agent schemas and remote metadata structures to prevent sync failures.