sqlmigration-security-review SKILL.md skillB
sqlmigration-security-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-security-review@git:20261006.2c73ad2Pins git:20261006.2c73ad2 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-security-review/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261006.2c73ad2, committed Oct 6, 2026
- First version recorded
- Jun 21, 2026
- Size
- 16,118 bytes
- Repository stars
- 12
- License
- MIT
Audits the security-object migration plan for a SQL Server move with 15 checks (J1-J15) — logins, server and database permissions, credentials, certificates/keys ownership, and Central Management Server registrations. Use this skill when a user is migrating a SQL Server database or instance and needs to carry over logins, permissions, credentials, or certificates, or asks "will my logins still work after migration" or "how do I migrate permissions." Trigger whenever security-object portability…
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-security-review ## Purpose Reviews the security-object family of a SQL Server migration — the slice `sqlmigration-review` dispatches here rather than checking itself. This skill owns 15 checks (J1–J15) covering whether logins, server/database permissions, credentials, certificate/key ownership, and Central Management Server (CMS) registrations will survive a backup/restore or log shipping/Always On AG seeding migration, and what breaks if they don't. - **Login Portability (J1–J5)** — orphaned users after restore, SID mismatch, login type unsupported on target platform, password policy differences, default database missing - **Permission Fidelity (J6–J9)** — server-level role membership, database-level role membership, explicit GRANT/DENY statements, ownership chains crossing the migration boundary - **Credentials & Secrets (J10–J12)** — SQL Server Credential objects, proxy account mapping, linked server stored logins - **Certificates & Keys (J13–J14)** — certificate/key migration for objects that depend on them (excluding TDE, which is `sqlencryption-review`'s domain), backup of certificates before cutover …
Read the whole file at its exact version.
How to install
mdr add vanterx/mssql-performance-skills/sqlmigration-security-review@sha256:b7a790f3ef043189The line at the top of this page pins the label git:20261006.2c73ad2, 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_odz6b2yiuai5zdil)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 21, 2026 and Oct 6, 2026, about one every 36 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.2c73ad2 latest | 2026-10-06 | 2c73ad2 | 16,118 B | B | view · diff |
| git:20260622.55f8c85 | 2026-06-22 | 55f8c85 | 14,924 B | A | view · diff |
| git:20260621.95d2441 | 2026-06-21 | 95d2441 | 14,644 B | A | view · diff |
| git:20260621.d1ce43d | 2026-06-21 | d1ce43d | 14,620 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 (16118 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_odz6b2yiuai5zdil GET https://markdownregistry.com/api/v1/resolve?ref=vanterx/mssql-performance-skills/sqlmigration-security-review GET https://markdownregistry.com/api/v1/blob/b7a790f3ef043189a0eff679fcfca54b8be8f860c3fad8366a4a7b26f7266f4c
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.