agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/secure-scalable-db-app/SKILL.md

secure-scalable-db-app

Skill1 starsChanged 12 days agoMITView on GitHub

Guide Azure SQL application security, parameter-sensitive-plan performance, and SqlClient retry/failover demonstrations. Use when working with examples/securescaleabledbapp and its demo1_secure, demo2_perf, or demo3_availability walkthroughs.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 overview and select security, performance, or availability.

    line 10
  2. Distinctive:

    Verify Azure SQL targets, identities, Visual Studio/.NET and SqlClient requirements.

    line 12
  3. Very specific:

    Keep credentials private. Confirm actual filenames before running inherited instructions.

    line 16
  4. Distinctive:

    Follow secret checks before publishing.

    line 32

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

Secure, scalable, available Azure SQL application

Procedure

  1. Read the collection overview and select security, performance, or availability.
  2. Verify Azure SQL targets, identities, Visual Studio/.NET and SqlClient requirements. The collection supplies source/configuration snippets, not a complete solution/project; use the walkthrough's project setup.
  3. Inspect App.config and scripts for endpoint/authentication assumptions. Keep credentials private. Confirm actual filenames before running inherited instructions; the bundled availability helpers include failovergp1.ps1 and failovergp3.ps1, not every filename named in the old prose.
  4. For security, use only an isolated, user-owned sample database. Inspect the intentionally unsafe query example and its parameterized alternative; never expose the unsafe path or test destructive input against real data.
  5. For performance, follow the local PSP walkthrough after verifying feature/build requirements instead of relying on the inherited preview-era external link.
  6. For availability, review retry configuration and observe a bounded probe. Obtain explicit approval before failover and verify the intended database and resource group. Distinguish observed retries/recovery from an SLA claim.
  7. Restore the safe query path and close lab processes. Confirm scope before cleanup; do not delete shared cloud resources or weaken firewall rules.

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.