adventureworks
Skill1 starsChanged 12 days agoMITView on GitHub
Import or prepare the AdventureWorksLT2025 sample database using the bundled BACPAC. Use when working with examples/adventureworks, importing AdventureWorksLT into Azure SQL, or preparing sample data for SQL demos.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- inside-transaction-logSkill
- polybaseSkill
- powerapps-sqlSkill
- secure-scalable-db-appSkill
- sql-by-exampleSkill
- sql-linuxSkill
- sqlserver2022Skill
- sqlserver2025Skill
- sql-versioning-appsSkill
- sql-versioningSkill
- tempdb-growthSkill
- waits-latches-spinlocksSkill
- waits-latches-spinlocks-workshopSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 10
Read the collection README and inspect importadwlt.cmd.
- Distinctive: line 13
Verify SQLPackage is available, the target Azure SQL server/database exists, and the operator can authenticate with the script's Entra/MFA …
- Distinctive: line 15
Do not install tools or change authentication without approval.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
AdventureWorksLT sample import
Procedure
- Read the collection README and inspect importadwlt.cmd. Confirm the user wants the LT sample, not the full AdventureWorks schema.
- Verify SQLPackage is available, the target Azure SQL server/database exists, and the operator can authenticate with the script's Entra/MFA flow. Do not install tools or change authentication without approval.
- Review the bundled BACPAC's provenance and the destination's current data. Confirm the target and import impact before executing; never overwrite a production database or place authentication material in the command file.
- Adapt only the necessary target parameters and run the documented import. Capture failures explicitly. Evaluate documented compatibility warnings separately from an actual failed import.
- Connect to the destination and verify expected
SalesLTtables/data. Report the target and observed result, not just the process exit code.
Boundaries
The package is sample data, not a backup/restore strategy or the full AdventureWorks database required by every other collection. Do not delete the destination as automatic cleanup. Follow secret checks before publishing modified scripts or database packages.
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.

