Skip to content
TrustedSkillsbeta
Back to all skills

Upgrading To Prisma 6

Checked
djankies·vlatest·database·MIT

Migrates existing databases to Prisma 6, ensuring compatibility and leveraging its enhanced features for improved performance.

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 djankies/claude-configs --skill upgrading-to-prisma-6 -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

djankies

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 djankies/claude-configs at a82763a6e7.

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

Scanned
5 files, 624 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 assists in upgrading existing Prisma projects to version 6. It provides guidance and automated steps to ensure a smooth transition, handling changes in data source configuration and schema definition. The upgrade process includes updating dependencies and migrating any custom code that may be affected by the new version.

When to use it

  • You have a Prisma project using an older version (e.g., 1.x, 2.x, or 3.x).
  • You need to leverage new features and improvements introduced in Prisma 6.
  • Your team is facing compatibility issues with existing tools or libraries due to the outdated Prisma version.
  • You want to benefit from performance enhancements and bug fixes present in Prisma 6.

Key capabilities

  • Automated dependency updates
  • Data source configuration migration
  • Schema definition adjustments
  • Compatibility checks for custom code

Example prompts

  • "Upgrade my existing Prisma project to version 6."
  • "What are the key changes I need to be aware of when upgrading to Prisma 6?"
  • "Help me migrate my data source configuration from Prisma 2.x to Prisma 6."

Tips & gotchas

  • Ensure you have a recent backup of your project before initiating the upgrade process.
  • Prisma 6 introduces significant changes; thoroughly review the migration guide for potential breaking changes and necessary adjustments.