sqlmigration-review SKILL.md skillB
sqlmigration-review from vanterx/mssql-performance-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vanterx/mssql-performance-skills/sqlmigration-review@git:20261015.4b8976ePins git:20261015.4b8976e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vanterx/mssql-performance-skills
- Path
skills/sqlmigration-review/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261015.4b8976e, committed Oct 15, 2026
- First version recorded
- Jun 21, 2026
- Size
- 21,151 bytes
- Repository stars
- 12
- License
- MIT
Audits a SQL Server migration plan with 15 checks (Y1-Y15) for version, edition, platform, and source-topology compatibility, then dispatches to sqlmigration-security-review, sqlmigration-objects-review, and other specialised skills for overlap areas. Use this skill when a user is planning, mid-flight on, or validating a SQL Server migration via backup/restore or log shipping/Always On seeding, mentions moving databases between instances/editions/versions, off a Failover Cluster Instance, or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# sqlmigration-review ## Purpose Reviews a planned or in-progress SQL Server migration for version, edition, and platform compatibility risk, then dispatches to companion skills for the object families a migration touches. This skill owns 15 checks (Y1–Y15) covering exactly one slice of migration risk — **does the target SQL Server version/edition/platform support what the source actually uses, and does the cutover plan account for the source's own topology** — and routes everything else: - **Version & Edition Compatibility (Y1–Y6)** — edition-gated features, version downgrade risk, compatibility level ceiling, collation mismatch, discontinued features, In-Memory OLTP support - **Platform Compatibility — Azure SQL (Y7–Y9)** — instance-scoped object support, Windows Authentication migration path, SQL Server Agent availability - **Migration Mechanism Readiness (Y10–Y13)** — backup/restore chain integrity, recovery model, Always On AG edition limits for seeding - **Lifecycle (Y14)** — source version support-end urgency - **Source Topology Transition (Y15)** — Failover Cluster Instance client redirect planning …
Read the whole file at its exact version.
How to install
mdr add vanterx/mssql-performance-skills/sqlmigration-review@sha256:83204c37857f5992The line at the top of this page pins the label git:20261015.4b8976e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zfzaqon7w7ihd6ip)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 21, 2026 and Oct 15, 2026, about one every 19 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.4b8976e latest | 2026-10-15 | 4b8976e | 21,151 B | B | view · diff |
| git:20261006.2c73ad2 | 2026-10-06 | 2c73ad2 | 21,151 B | B | view · diff |
| git:20260701.321a668 | 2026-07-01 | 321a668 | 19,957 B | A | view · diff |
| git:20260623.4a7462d | 2026-06-23 | 4a7462d | 19,957 B | A | view · diff |
| git:20260622.55f8c85 | 2026-06-22 | 55f8c85 | 19,070 B | A | view · diff |
| git:20260621.95d2441 | 2026-06-21 | 95d2441 | 18,006 B | A | view · diff |
| git:20260621.d1ce43d | 2026-06-21 | d1ce43d | 17,982 B | A | view |
Audit of the latest version
- fail: No prompt-injection phrasing (matched: ignore the previous instructions)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (21151 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vanterx/mssql-performance-skills · 12 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zfzaqon7w7ihd6ip GET https://markdownregistry.com/api/v1/resolve?ref=vanterx/mssql-performance-skills/sqlmigration-review GET https://markdownregistry.com/api/v1/blob/83204c37857f59928ac556bfa6fe012a23d6058aeb3187a569dd62a4e1e3ee31
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.