MicrosoftKnown publishermicrosoft/sqlcon-eu-2026-demos/corenote/migration/skills/run-migration-assessment/SKILL.mdrun-migration-assessment
Skill0 starsChanged 53 days agoMITView on GitHub
Route generic or unresolved SQL Server assessment, readiness, compatibility, cost, and SKU recommendation requests. Use for bare server names or whenever Azure versus local/on-premises is not explicit; ask which source applies, then delegate.
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★ 2278% 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
- get-migration-assessmentSkill
- recommend-migration-pathSkill
- recommend-sku-sizingSkill
- 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
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use as the entry point for migration assessment requests when Azure versus Local, or readiness versus SKU, still needs to be determined.
- Distinctive: line 27
Wait for the answer when the path is ambiguous.
- Distinctive: line 50
Ask only whether the source is Azure or Local when that choice is ambiguous.
- Distinctive: line 51
Do not duplicate delegated-skill prerequisites or workflows here.
≈ “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
Run Migration Assessment
When to Use
Use as the entry point for migration assessment requests when Azure versus Local, or readiness versus SKU, still needs to be determined.
Workflow
Step 1: Identify the Server
Reuse known inputs. Determine only whether the source is Azure or Local:
- Azure identifiers or an Azure SQL Server resource URI -> Azure.
- IP, connection string, config file, or explicit on-premises/local wording -> Local.
- Bare server or instance name -> ask:
"Is
{serverName}a Local/on-premises SQL Server or an Azure SQL Server?"
Wait for the answer when the path is ambiguous. Do not resolve Azure resources, check Local prerequisites, request credentials, select output folders, inspect existing results, or run commands in this skill.
Step 2: Route Azure
Delegate to evaluate-azure-migration-assessment with all known context and the
user's original intent. That skill owns resource resolution, existing-result
handling, fresh execution, and output.
Step 3: Route Local
- Readiness or general assessment request -> delegate to
evaluate-offline-migration-readiness. - Explicit performance collection or SKU-sizing request -> delegate to
recommend-sku-sizing.
Pass all known context and the user's original intent. The delegated skill owns host checks, prerequisites, connection details, output-folder selection, existing-result handling, execution, and output.
Notes
- Ask only whether the source is Azure or Local when that choice is ambiguous.
- Do not duplicate delegated-skill prerequisites or workflows here.
- Delegated skills own commands, errors, follow-up choices, and output formatting.
Error Handling
- Cannot determine Azure versus Local -> ask the user to select Azure or Local.
- Missing details after routing -> let the delegated skill request them.
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.