get-migration-assessment
Skill0 starsChanged 53 days agoMITView on GitHub
Retrieve existing SQL Server migration assessment data from Azure Resource Graph using required instance-level and database-level queries.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- microsoft/microsoft-sqledited, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- microsoft/microsoft-sql★ 2267% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- biomedical-evidence-review-v2Skill
- analyze-readiness-at-scaleSkill
- evaluate-azure-migration-assessmentSkill
- evaluate-offline-migration-readinessSkill
- generate-migration-prerequisite-planSkill
- recommend-migration-pathSkill
- recommend-sku-sizingSkill
- run-migration-assessmentSkill
- sql-backup-restore-to-azure-sql-vm-migrationSkill
- sql-bacpac-to-azure-sql-db-migrationSkill
- sql-server-to-sql-mi-lrs-migrationSkill
- validate-post-migration-dataSkill
- build-caldova-evidence-agentSkill
- demo-caldova-evidence-agentSkill
- run-caldova-evidence-agentSkill
- run-handsfree-indexingSkill
- run-keynote-demo-1Skill
- keynote-demo-appSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use for existing Azure SQL Server assessment, readiness, blocker, SKU, and cost data.
- Distinctive: line 18
Use ARM resource identification.
- Very specific: line 32
Use references/response-schema.md.
- Very specific: line 35
If assessment data or assessmentUploadTime is missing, state that no migration assessment data is available and identify likely causes: it …
- Distinctive: line 42
Use assessment output to render the combined readiness and SKU recommendation.
- Very specific: line 53
Every NotReady result has a cause or data-gap note.
- Distinctive: line 58
Use ARG as the assessment read transport.
- Distinctive: line 63
Follow the output template exactly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Get Migration Assessment
When to Use
Use for existing Azure SQL Server assessment, readiness, blocker, SKU, and cost data. This skill does not trigger a new assessment.
Workflow
Step 1: Resolve Inputs
Use ARM resource identification. Reuse identifiers already in context. Confirm a defaulted subscription by display name and ID.
Step 2: Query Instance Data
Build and execute the instance query from references/arg-queries.md.
Step 3: Query Database Data
Build and execute the database query from references/arg-queries.md for every
returned instance.
Step 4: Interpret Results
Use references/response-schema.md. For every NotReady target, identify the
server or database blocker. If blocker details are unavailable, report a data gap.
If assessment data or assessmentUploadTime is missing, state that no migration
assessment data is available and identify likely causes: it has not been enabled
or run, results have not uploaded, the agent is not configured, or permissions are
insufficient.
Step 5: Render Results
Use assessment output to render the combined readiness and SKU recommendation.
- Multiple instances -> show a summary table, then render each instance.
For multiple instances, include aggregate readiness, cost, and common blocker insights when the returned data supports them.
Completion Check
- Both query phases completed for every instance.
- Pagination completed.
- Every
NotReadyresult has a cause or data-gap note. - Missing settings or readiness are stated explicitly.
Notes
- Use ARG as the assessment read transport.
- Execute queries through the
curladapter inreferences/arg-queries.md. - Exclude
master,model,msdb, andtempdb. - Show subscription display name with its ID.
- Follow the output template exactly.
Error Handling
- 401/403 -> verify Azure CLI login and read permission on the target scope.
- 429 -> honor
Retry-After; report persistent throttling. - Invalid resource URI -> show the expected Azure SQL Server instance resource-ID format.
- Empty result -> show the subscription display name/ID and resource group that were searched.
References
references/arg-queries.mdreferences/response-schema.md- ARM resource identification
- Assessment output
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

