Skip to content
TrustedSkillsbeta
Back to all skills

1K Pkg Upgrade Review

Checked
onekeyhq·vlatest·backend

Reviews OneKey's automated 1,000+ package upgrade proposals, flagging potential risks and optimizing cost savings.

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 onekeyhq/app-monorepo --skill 1k-pkg-upgrade-review -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

onekeyhq

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 onekeyhq/app-monorepo at eba5185761.

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

Scanned
5 files, 636 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 scans a monorepo containing over 1,000 packages to identify outdated dependencies. It automatically generates upgrade plans and executes version bumps across the entire codebase to maintain security and compatibility.

When to use it

  • You need to audit a large-scale monorepo for deprecated or vulnerable library versions.
  • Your development team requires an automated workflow to keep thousands of packages synchronized with latest stable releases.
  • You want to reduce manual effort in reviewing changelogs before applying dependency updates.
  • You are preparing for a major release and need to ensure all internal packages are up-to-date.

Key capabilities

  • Scans monorepos with 1,000+ packages efficiently.
  • Identifies outdated dependencies automatically.
  • Generates comprehensive upgrade plans.
  • Executes version bumps across the entire repository.

Example prompts

  • "Run a full dependency audit on my app-monorepo and list all packages needing updates."
  • "Generate an upgrade plan for all outdated libraries in the 1k-pkg-upgrade-review scope."
  • "Execute the generated upgrade plan to bump versions of identified dependencies."

Tips & gotchas

Ensure your monorepo structure is properly configured before running the skill, as it relies on specific directory layouts to function correctly. Always review the generated upgrade plans in a staging environment before applying changes to production systems to prevent potential breaking changes.