deploy-business-process-core
Skill1 starsChanged 52 days agoMITView on GitHub
Deploy BusinessProcessCore or check and validate an existing installation, including the Core prerequisite for OrderProcessing.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- business-processes/AGENTS.mdAGENTS.md
- business-processes/order-processing/AGENTS.mdAGENTS.md
- core/AGENTS.mdAGENTS.md
- core/codeapps/workflow-console/AGENTS.mdAGENTS.md
- core/plugins/business-process-api/AGENTS.mdAGENTS.md
- evaluate-order-discounts-promotionsSkill
- validate-order-product-identitySkill
- validate-order-product-availabilitySkill
- sap-order-jsonSkill
- sap-order-excelSkill
- deploy-order-processingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Before executing any PowerShell, resolve the folder containing this SKILL.md to $skillFolder.
- Very specific: line 10
Use Installation Check for check/verify/validate requests and OrderProcessing prerequisite checks.
- Distinctive: line 14
Ask whether a Dataverse environment exists.
- Distinctive: line 16
Read roles/licensing; run Core readiness.
- Distinctive: line 18
Follow the deployment guide.
- Distinctive: line 19
Run Installation Check after the final import.
- Distinctive: line 27
Follow installation verification.
≈ “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.
Files
Deploy Business Process Core
Before executing any PowerShell, resolve the folder containing this SKILL.md to $skillFolder; do not hardcode its location.
Use Installation Check for check/verify/validate requests and OrderProcessing prerequisite checks. Otherwise use Deploy. Ask which workflow when unclear.
Deploy
- Ask whether a Dataverse environment exists. If yes, request its environment ID, not its name or organization ID. Wait for the answer.
- Complete technical prerequisites from the repository root.
- Read roles/licensing; run Core readiness. Resolve failures and document unverified requirements.
- Summarize applicable requirements; require explicit user confirmation of understanding and availability of access, licenses, Copilot Credits, and delegated support.
- Follow the deployment guide. For new environments, verify active tenant-wide Power Platform Administrator and obtain provisioning approval; confirm the new ID and rerun readiness.
- Run Installation Check after the final import. Require every check to pass
- Provide the deployment summary. Hand over the environment/organization IDs, solution and package versions, application-user/connection IDs, role verification, Workflow Console URL, and credential expiry/secure storage reference. Do not include secrets.
Installation Check
- Require an existing environment ID, tenant ID, organization ID/URL, and approved package/version and managed/unmanaged state. Do not provision an environment.
- Complete technical prerequisites from the repository root.
- Follow installation verification; run the bundled script and evaluate every criterion, including runtime privileges and all 13 tool associations.
- Report Pass, Fail, or Not verified per criterion with brief evidence. Overall Pass requires all criteria to pass. Stop on failures/unknowns; obtain separate approval for repairs and rerun after repair. Do not import, publish, activate, or run business actions in this workflow.
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
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.

