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

debugging-sql

Skill1 starsChanged 12 days agoMITView on GitHub

Guide SQL Server debugging labs with WinDbg: access violations, hangs, scheduler deadlocks, query aborts, latches, spinlocks, and unexplained CPU. Use when working with examples/debugging_sql or choosing one of its seven labs.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the collection map. Select the matching failure/observation lab.

    line 10
  2. Very specific:

    Read that lab's README and inspect command/SQL/native entry points.

    line 12
  3. Distinctive:

    Check local executable, dump, symbol-cache, database, and file paths.

    line 17
  4. Distinctive:

    Stop stress processes by their specific IDs, close lab transactions, follow the lab's cleanup, and detach without killing SQL Server unless …

    line 23
  5. Distinctive:

    Never attach these destructive reproductions to production.

    line 29

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

Procedure

  1. Read the collection map. Select the matching failure/observation lab; do not run all reproductions.
  2. Read that lab's README and inspect command/SQL/native entry points. Confirm Windows SQL Server build, instance, privileges, WinDbg, symbol availability, SQL client tools, and any required stress driver.
  3. Identify actions that attach, pause, crash, restart, or deliberately hang SQL Server. Require a disposable lab and explicit approval before them. Check local executable, dump, symbol-cache, database, and file paths.
  4. Capture baseline requests/waits/stacks. Run only the approved reproduction, keeping a separate diagnostic or DAC connection where the lab requires it.
  5. Correlate actual DMV, CPU, stack, exception, or dump evidence with the walkthrough. Symbol addresses and internal types are build-specific; distinguish unavailable symbols from proof of a different root cause.
  6. Stop stress processes by their specific IDs, close lab transactions, follow the lab's cleanup, and detach without killing SQL Server unless the approved reproduction requires termination.

Boundaries

Never attach these destructive reproductions to production. Preserve dumps privately; dumps/logs can contain sensitive data. Use secret checks before sharing source or captures.

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.