Skip to content
TrustedSkillsbeta
Back to all skills

Unistyles V2 To V3 Migration

Checked
jpudysz·vlatest·database

Converts UniStyles v2 configurations to the latest v3 format, streamlining workflows and ensuring compatibility.

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 jpudysz/react-native-unistyles --skill unistyles-v2-to-v3-migration -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

jpudysz

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 jpudysz/react-native-unistyles at 759f374723.

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

Commit
759f374723
Manifest
skills/unistyles-v2-to-v3-migration/SKILL.md
Scanned
4 files, 1,860 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 automates the migration of projects from unistyles v2 to v3. It handles the necessary code transformations and updates required for compatibility with the newer version, reducing manual effort and potential errors during the upgrade process. The tool ensures a smooth transition by addressing changes in syntax and functionality between versions.

When to use it

  • You have a React Native project using unistyles v2.
  • You need to update your project to unistyles v3 for access to new features or bug fixes.
  • You want to avoid the tedious manual process of refactoring unistyles code.
  • Your team is facing challenges in upgrading an existing unistyles v2 codebase.

Key capabilities

  • Automated migration from v2 to v3
  • Code transformation and updates
  • Compatibility with newer unistyles versions

Example prompts

  • "Migrate my project's unistyles code from version 2 to version 3."
  • "Run the unistyles-v2-to-v3-migration tool on this codebase."
  • “Update all unistyles components in this directory to be compatible with v3.”

Tips & gotchas

  • Ensure your project has a valid unistyles v2 configuration before running the migration.
  • Review the migrated code carefully, as automated migrations may require manual adjustments for complex scenarios.