agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/auto-index-compaction/SKILL.md

auto-index-compaction

Skill1 starsChanged 12 days agoMITView on GitHub

Demonstrate automatic index compaction in Azure SQL Hyperscale. Use when working with examples/auto_index_compaction, page density after scatter deletes, AIC background cleanup, or scan IO comparisons.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Run setup and record baseline row count, density, pages, logical reads, and scan timing using the supplied measurement script.

    line 16

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

Automatic index compaction

Procedure

  1. Read the walkthrough and the numbered scripts. Verify the target is an Azure SQL Hyperscale lab with the required feature available; do not assume other service tiers work.
  2. Confirm database identity, permissions, available space, and approval for data creation/deletion, configuration changes, and cold-cache measurement. Capture the starting configuration before modifying it.
  3. Run setup and record baseline row count, density, pages, logical reads, and scan timing using the supplied measurement script.
  4. Review the timing warning before degrading data. Enable AIC immediately after the DML workload as documented, without an unplanned pause that lets version cleanup finish first. Do not promise compaction on a fixed timer.
  5. Monitor progress and version-store observations, then repeat the same scan measurement. Distinguish observed results from the README's example numbers.
  6. With approval, follow the cleanup script and verify the lab table/configuration state. Do not disable a pre-existing setting without reviewing its ownership.

Evidence

Compare the same workload and cache conditions. Explain unsuccessful observations in terms of actual feature/timing evidence rather than inventing a speedup. Use 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.