agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/sql-by-example/SKILL.md

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.

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

    Read the collection overview and select ADR, containers, the data hub, Kubernetes, or performance.

    line 10
  2. Distinctive:

    Read the selected subfolder's README and actual scripts/notebooks.

    line 12
  3. Distinctive:

    Verify the historical SQL version/build, edition, sample database, tools, and connector requirements.

    line 13
  4. Distinctive:

    Stop lab processes, close transactions, and follow the selected teardown with approval before removing databases, containers, or persistent …

    line 25

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

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

SQL Server By Example

Procedure

  1. Read the collection overview and select ADR, containers, the data hub, Kubernetes, or performance. Read the selected subfolder's README and actual scripts/notebooks.
  2. 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.
  3. Inspect paths, targets, credentials, notebook outputs, and cleanup. Obtain approval before installing tools, provisioning resources, restoring data, changing configuration, or running stress/failure reproductions.
  4. 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.
  5. 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.
  6. 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.

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.