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

powerapps-sql

Skill1 starsChanged 12 days agoMITView on GitHub

Build the Power Apps orders canvas app backed by Azure SQL AdventureWorksLT. Use when working with examples/powerappssql, SalesLT order galleries, customer/product lookups, order-detail filtering, or the editable order form.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Very specific:

    Verify an Azure SQL database with the required SalesLT tables and access to a Power Platform environment.

    line 11
  2. Distinctive:

    Follow the walkthrough to create the SQL connection and canvas app, then build the order gallery and customer-name lookup.

    line 17
  3. Distinctive:

    Add the selected-order form, order-detail gallery, and product-name lookup.

    line 19
  4. Distinctive:

    Verify actual control names before adapting formulas.

    line 20
  5. Distinctive:

    Add sorting and save behavior.

    line 22
  6. Distinctive:

    Do not delete shared connections, apps, or databases as automatic cleanup.

    line 25
  7. Distinctive:

    Use synthetic sample orders and the repository publishing checks.

    line 27

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

Power Apps with Azure SQL

Procedure

  1. Read the walkthrough. Verify an Azure SQL database with the required SalesLT tables and access to a Power Platform environment.
  2. Confirm connection and authentication prerequisites. The inherited example uses SQL authentication; enter credentials only in the supported private connection UI, never in source or chat. Explain any firewall/authentication change and obtain approval before applying it.
  3. Follow the walkthrough to create the SQL connection and canvas app, then build the order gallery and customer-name lookup.
  4. Add the selected-order form, order-detail gallery, and product-name lookup. Verify actual control names before adapting formulas; template-generated names may differ from the walkthrough.
  5. Add sorting and save behavior. Test selection/context changes before writes. Obtain approval before updating order data, then verify the change in SQL.
  6. Save the app and report the tested behavior and remaining configuration. Do not delete shared connections, apps, or databases as automatic cleanup.

Use synthetic sample orders and the repository publishing checks.

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.