agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/microsoft-sql/plugins/microsoft-sql/skills/dev-container-templates/SKILL.md

dev-container-templates

Skill22 starsChanged 53 days agoLicence not identifiedView on GitHub

Sets up local development from the Azure SQL Database dev container templates in microsoft/azuresql-devcontainers (.NET, .NET Aspire, Node.js, Python), each with a sample database and schema loaded. Use for "start from the Azure SQL Database dev container template", "which Azure SQL Database devcontainer should I pick", or "add a dev container with a database already in it", and for what these templates do: an empty database, a schema project that never deploys, a saved profile prompting for a password, a database at localhost not a service name, a vector index refused, a port on the app service refused, or the local database in a template not behaving the way the Azure SQL Database documentation describes, because it is SQL Server. Covers the SQL Database project whose target platform, not the engine, decides what Azure SQL Database accepts, and the create-time build and publish.

  • Reads credentials

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.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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.

Check your setup, free