agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/power-cat-skills/Power Platform Migration Factory/Access to Dataverse Migration/SKILL.md

powercat-accessmigration

Skill70 starsChanged 2 days agoMITView on GitHub

Migrate a Microsoft Access database (.mdb/.accdb) into Microsoft Dataverse with an optional model-driven app. USE WHEN the user wants to modernize an Access database, reverse-engineer Access tables into Dataverse, or run the PowerCAT Access Migration workflow.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use this skill when the user wants to migrate a .mdb or .accdb Access database to Microsoft Dataverse, with an optional model-driven app.

    line 15
  2. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/Access to Dataverse Migration/README.md and ${CLAUDE_PLUGIN_ROOT}/Access to Dataverse Migration/mapping.yaml …

    line 20
  3. Distinctive:

    Create a migration plan covering source inventory, proposed Dataverse tables, columns, relationships, publisher prefix, solution name, app …

    line 21
  4. Distinctive:

    Ask the user to approve or adjust the plan before running any command that writes to Dataverse.

    line 22
  5. Distinctive:

    If the user approves execution, use the included mapping as a starting point and update it for the actual Access database schema.

    line 23
  6. Distinctive:

    Prefer a dry run or preview first.

    line 24
  7. Distinctive:

    Never commit local environment files, credentials, Access databases, exported CSV data, or generated run artifacts.

    line 28
  8. Very specific:

    If the Access ODBC driver is unavailable, ask the user to export each table to CSV and set source.type: csv in the mapping.

    line 30
  9. Distinctive:

    Treat PII, payment, and sensitive source columns as review items before migration.

    line 31

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

PowerCAT Access Migration

Migrate the Microsoft Access database described below into Dataverse:

$ARGUMENTS

Use this skill when the user wants to migrate a .mdb or .accdb Access database to Microsoft Dataverse, with an optional model-driven app.

Workflow

  1. Resolve the source Access database path from $ARGUMENTS. If the user provided a folder, search for .mdb and .accdb files and ask which one to use if there are multiple.
  2. Read ${CLAUDE_PLUGIN_ROOT}/Access to Dataverse Migration/README.md and ${CLAUDE_PLUGIN_ROOT}/Access to Dataverse Migration/mapping.yaml before planning the migration.
  3. Create a migration plan covering source inventory, proposed Dataverse tables, columns, relationships, publisher prefix, solution name, app name, risks, and prerequisites.
  4. Ask the user to approve or adjust the plan before running any command that writes to Dataverse.
  5. If the user approves execution, use the included mapping as a starting point and update it for the actual Access database schema.
  6. Prefer a dry run or preview first. Only run live Dataverse writes after explicit user confirmation.

Important safeguards

  • Never commit local environment files, credentials, Access databases, exported CSV data, or generated run artifacts.
  • Confirm the target Dataverse environment before provisioning.
  • If the Access ODBC driver is unavailable, ask the user to export each table to CSV and set source.type: csv in the mapping.
  • Treat PII, payment, and sensitive source columns as review items before migration.

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.

Check your setup, free