SKILLEMALL.ai
GitHub ↗ RU Sign in

AC prisma-upgrade-v7

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".

prisma/skills Agent Skills author: prisma MIT 8 files body ≈ 1 921 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes.

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedurePostgreSQLMongoDBMySQLWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
94
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 33, 59, 84): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 8 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 35 steps, 2 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1921 tokens
    • low 13 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 283: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.