agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/copilot-agentic-business-process/.github/skills/deploy-order-processing/SKILL.md

deploy-order-processing

Skill1 starsChanged 52 days agoMITView on GitHub

Deploy OrderProcessing or check an existing installation

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

    Before executing any PowerShell, resolve the folder containing this SKILL.md to $skillFolder.

    line 8
  2. Distinctive:

    Ask for an existing Dataverse environment ID, not its name or organization ID.

    line 13
  3. Distinctive:

    Read roles/licensing; run OrderProcessing readiness.

    line 15
  4. Distinctive:

    Follow the deployment guide

    line 17

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Order Processing

Before executing any PowerShell, resolve the folder containing this SKILL.md to $skillFolder; do not hardcode its location.

Deploy

  1. Ask for an existing Dataverse environment ID, not its name or organization ID. If none exists, stop and run deploy-business-process-core skill first. If an existing environment is available, use deploy-order-processing skill to check for existing business process core installation.
  2. Complete technical prerequisites from the repository root.
  3. Read roles/licensing; run OrderProcessing readiness. Resolve failures and document unverified requirements.
  4. Summarize applicable requirements; require explicit user confirmation of understanding and availability of access, licenses, Copilot Credits, and delegated support.
  5. Follow the deployment guide
  6. Provide the deployment summary. Hand over the environment/organization IDs, solution and package versions, application-user/connection IDs, role verification, Workflow Console URL, sharedmailbox to use to send orders, a recap of allowed users and their teams and roles.

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.

Check your setup, free