agentleFS
MicrosoftKnown publishermicrosoft/sqlcon-eu-2026-demos/corenote/migration/skills/get-migration-assessment/SKILL.md

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

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
  1. Distinctive:

    Use for existing Azure SQL Server assessment, readiness, blocker, SKU, and cost data.

    line 11
  2. Distinctive:

    Use ARM resource identification.

    line 18
  3. Very specific:

    Use references/response-schema.md.

    line 32
  4. Very specific:

    If assessment data or assessmentUploadTime is missing, state that no migration assessment data is available and identify likely causes: it …

    line 35
  5. Distinctive:

    Use assessment output to render the combined readiness and SKU recommendation.

    line 42
  6. Very specific:

    Every NotReady result has a cause or data-gap note.

    line 53
  7. Distinctive:

    Use ARG as the assessment read transport.

    line 58
  8. Distinctive:

    Follow the output template exactly.

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 NotReady result 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 curl adapter in references/arg-queries.md.
  • Exclude master, model, msdb, and tempdb.
  • 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.md
  • references/response-schema.md
  • ARM resource identification
  • Assessment output

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.