sql-linux
Skill1 starsChanged 12 days agoMITView on GitHub
Guide the SQL Server on Linux collection: install/explore SQL Server 2017, automatic tuning, cross-platform availability groups, and Docker demonstrations. Use when working with examples/sqllinux and its Linux shell, SQL, and Windows Docker helper scripts.
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-by-exampleSkill
- 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
5 rules. About 0 are common, 5 are distinctive, and 0 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.
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 the selected installation, exploration, automatic-tuning, availability-group, or Docker walkthrough.
- Distinctive: line 13
Verify Linux distribution, SQL version/build, tools, sample database, and permissions.
- Distinctive: line 22
Follow the selected sequence, verifying service state, SQL connectivity, plans/tuning recommendations, container state, or replica behavior …
- Distinctive: line 25
Stop workloads and follow the area-specific cleanup.
- Distinctive: line 29
Follow secret checks and runtime credential setup.
≈ “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 on Linux
Procedure
- Read the collection README and the selected installation, exploration, automatic-tuning, availability-group, or Docker walkthrough.
- Verify Linux distribution, SQL version/build, tools, sample database, and permissions. The inherited instructions reference SQL Server 2017 and older distribution/package URLs; check supported combinations before installation.
- Inspect hostnames, file paths, service commands, credentials, certificates,
and container settings. Distinguish commands for Linux from Windows
.cmdhelpers; do not run Linux service/package commands on the Windows host. - Obtain approval before package changes, service restarts, restoring data, certificate/login creation, availability-group changes, container deployment, or workload generation. Use a disposable lab and private credentials.
- Follow the selected sequence, verifying service state, SQL connectivity, plans/tuning recommendations, container state, or replica behavior as appropriate. Do not turn old screenshots or example paths into assumed facts.
- Stop workloads and follow the area-specific cleanup. Preserve original settings and confirm scope before removing databases, certificates, containers, or volumes.
Follow secret checks and runtime credential setup. Review database/certificate assets separately before publication.
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.

