Skills prisma-mongodb-upgrade

📦

prisma-mongodb-upgrade

Name: prisma-mongodb-upgrade
Author: prisma

v0.1.0 Content revision r2 Safe 🔑 Env variables⚙️ External commands🌐 Network access

Plan Your Prisma MongoDB Upgrade

Prisma ORM v7 does not support MongoDB, so standard upgrade advice fails. This skill evaluates Prisma Next and provides a staged migration path.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "prisma-mongodb-upgrade" from https://skillstore.io/skills/prisma-prisma-mongodb-upgrade.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-mongodb-upgrade/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/prisma-prisma-mongodb-upgrade.md Signed manifest GET /api/skills/prisma-prisma-mongodb-upgrade/manifest Signed lockfile GET /api/skills/prisma-prisma-mongodb-upgrade/lockfile

Test it

Using "prisma-mongodb-upgrade". Can I upgrade my Prisma v6 MongoDB project to Prisma v7?

Expected outcome:

No. Prisma ORM v7 has no MongoDB connector. Remain on the latest v6 release or evaluate Prisma Next after checking its Early Access constraints.

Using "prisma-mongodb-upgrade". What should I check before trying Prisma Next?

Expected outcome:

Confirm MongoDB 8.0 or newer and compatible package versions.
Inventory transactions and raw database calls.
Validate contracts, indexes, and document shapes on a staging copy.
Keep the v6 deployment available until verification passes.

Using "prisma-mongodb-upgrade". How should production cutover work?

Expected outcome:

Compare read-only results first, enable Prisma Next writes only after validation, and retain the v6 branch as the rollback path.

Security Audit

Safe

v9 • 7/23/2026 Open versioned report

All 24 static findings are false positives caused by documentation links, inline code, and command names in Markdown. No executable scripts, credential access, unsafe network behavior, or prompt injection was found.

Files scanned

423

Lines analyzed

Review items

False positives ignored

Risk Factors

🔑 Env variables (2)

references/decision-stay-or-migrate.md:80 SKILL.md:63

⚙️ External commands (19)

references/migrations-mapping.md:50-52 references/migrations-mapping.md:58-59 references/migrations-mapping.md:59-60 SKILL.md:22 SKILL.md:30 SKILL.md:50 SKILL.md:52 SKILL.md:54 SKILL.md:63 SKILL.md:64 SKILL.md:71 SKILL.md:72 SKILL.md:73 SKILL.md:74 SKILL.md:75 SKILL.md:81 SKILL.md:83 SKILL.md:85 SKILL.md:90

🌐 Network access (2)

SKILL.md:14 SKILL.md:80

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/prisma-prisma-mongodb-upgrade/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/prisma-prisma-mongodb-upgrade/security.svg)](https://skillstore.io/skills/prisma-prisma-mongodb-upgrade?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/prisma-prisma-mongodb-upgrade?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-mongodb-upgrade/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/prisma-prisma-mongodb-upgrade.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

prisma. (2026). prisma-mongodb-upgrade security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/prisma-prisma-mongodb-upgrade/audits/9

BibTeX citation

@techreport{prisma-prisma-prisma-mongodb-upgrade-2026,
  author = {prisma},
  title = {prisma-mongodb-upgrade security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/prisma-prisma-mongodb-upgrade/audits/9},
  note = {Author version 0.1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "prisma-mongodb-upgrade security audit report (audit version 9)"
version: "0.1.0"
type: report
authors:
  - name: "prisma"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/prisma-prisma-mongodb-upgrade/audits/9"
identifiers:
  - type: other
    value: "skillstore:prisma-prisma-mongodb-upgrade:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Choose an upgrade path

Determine whether a MongoDB application should remain on Prisma ORM v6 or evaluate Prisma Next.

Assess migration readiness

Inventory transactions, raw calls, server requirements, indexes, and schema contracts before committing to migration.

Plan a controlled cutover

Prepare staging verification, read-only comparison, production cutover, and rollback steps for an existing service.

Try These Prompts

Check my upgrade options

My project uses Prisma ORM v6 with MongoDB. Explain my supported upgrade options and the main tradeoffs.

Assess project blockers

Review this repository for Prisma MongoDB migration blockers. Check transactions, raw queries, MongoDB version assumptions, and package versions.

Create a migration plan

Create a staged Prisma Next migration plan for this application. Include schema mapping, API changes, migration verification, and rollback gates.

Audit a production cutover

Audit this proposed Prisma Next cutover. Identify data, index, validator, transaction, deployment, and rollback risks with actionable corrections.

Best Practices

Verify Prisma Next behavior against the exact installed version before changing the application.
Run contract, index, validator, and query checks against a staging copy before production.
Keep Prisma ORM v6 deployable until Prisma Next verification and read-only comparison pass.

Avoid

Do not attempt a Prisma ORM v7 upgrade because it has no MongoDB connector.
Do not change the application to SQL as an implicit solution to the version problem.
Do not apply push-style production changes without migration history, verification, and rollback planning.