sql-by-example
Skill1 starsChanged 12 days agoMITView on GitHub
Guide the SQL Server By Example collection: SQL Server 2019 ADR, containers, Kubernetes, PolyBase data-hub connectors, query processing, and lightweight profiling. Use when working with examples/sqlbyexample or choosing one of its bundled walkthroughs.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- adventureworksSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- inside-transaction-logSkill
- polybaseSkill
- powerapps-sqlSkill
- secure-scalable-db-appSkill
- 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
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 10
Read the collection overview and select ADR, containers, the data hub, Kubernetes, or performance.
- Distinctive: line 12
Read the selected subfolder's README and actual scripts/notebooks.
- Distinctive: line 13
Verify the historical SQL version/build, edition, sample database, tools, and connector requirements.
- Distinctive: line 25
Stop lab processes, close transactions, and follow the selected teardown with approval before removing databases, containers, or persistent …
≈ “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
SQL Server By Example
Procedure
- Read the collection overview and select ADR, containers, the data hub, Kubernetes, or performance. Read the selected subfolder's README and actual scripts/notebooks.
- Verify the historical SQL version/build, edition, sample database, tools, and connector requirements. Check current compatibility before using an old container tag, Kubernetes manifest, driver, or external service endpoint.
- Inspect paths, targets, credentials, notebook outputs, and cleanup. Obtain approval before installing tools, provisioning resources, restoring data, changing configuration, or running stress/failure reproductions.
- Execute the chosen walkthrough in numeric/session order on a disposable lab. Validate its specific result: recovery, container state, external joins, query-plan behavior, or live profiling evidence.
- Distinguish captured notebook output from current measurements. Use synthetic data and privately supplied connection settings; inherited credential examples must not be published as working configuration.
- Stop lab processes, close transactions, and follow the selected teardown with approval before removing databases, containers, or persistent storage.
This collection retains its own sqlperf/iqp material. It does not import the
separate demos/sqlserver/iqp collection. Follow
secret checks before publishing.
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.

