Skip to content

Add Business Applications guidance to workiq-preview skill - #194

Closed
Viraj Malkar (virajmalkar) wants to merge 6 commits into
microsoft:mainfrom
virajmalkar:add-businessapps-skills-to-preview
Closed

Add Business Applications guidance to workiq-preview skill#194
Viraj Malkar (virajmalkar) wants to merge 6 commits into
microsoft:mainfrom
virajmalkar:add-businessapps-skills-to-preview

Conversation

@virajmalkar

Copy link
Copy Markdown

Adds guidance for the Business Applications (/businessapps) path space to the workiq-preview skill.

Changes

  • SKILL.md (+26) — routing-table entries for structured records/workflows in CRM, ERP, and Power Apps; /businessapps/me in the entity-tools table; new "Business Applications" section; authorization-failure guidance for writes.
  • references/business-applications.md (new, 152 lines) — discovery and path-grounding rules, tool/path selection table, business skills, approval and privilege boundaries, execute-work guidance, and app-scoped operation conventions.

Notes

  • Documentation only — no code or configuration changes.
  • Ported from thejeffand/work-iq branch user/jeffand/bizapps (tip bae1211) via cherry-pick, so original authorship is preserved.
  • Content is byte-identical to the source branch for both files.

jeffandms and others added 6 commits August 24, 2026 18:15
…business skills

Updates the WorkIQ plugin instructions for the Business Applications provider:

- Rename every Business Applications path from /applications/* to
  /businessapps/* across SKILL.md and references/business-applications.md
  (32 occurrences). Microsoft Graph application-registration URLs elsewhere in
  the repo are deliberately untouched.
- Remove the "List environments/default" guidance and its
  fetch /applications/environments/ path. Discovery is now stated as a general
  rule: every Business Applications resource -- environments, apps, tables,
  records, skills, APIs and operations -- is resolved through do_action on
  /businessapps/me or search_paths, taking each identifier from the returned
  paths.
- Document business skills as first-class resources: fetch on
  /businessapps/environments/{environmentId}/skills[/{skillName}], and
  create_entity / update_entity / delete_entity following the same collection
  and item convention used for records.

Co-authored-by: Copilot <[email protected]>
Use the canonical WorkIQ path and operation shapes, and avoid substituting a different capability when a requested named skill is absent.

Co-authored-by: Copilot <[email protected]>
Copilot-Session: af51c104-57ac-4290-8c40-ca6ef92d4638
Stop unapproved and privilege-denied mutations instead of relying on server rejection or attempting alternate-resource workarounds.

Co-authored-by: Copilot <[email protected]>
Copilot-Session: af51c104-57ac-4290-8c40-ca6ef92d4638
Require exact accessible environments and governed terminology before reading or acting, without redirecting or inferring nearby fields.

Co-authored-by: Copilot <[email protected]>
Copilot-Session: af51c104-57ac-4290-8c40-ca6ef92d4638
Revert the second Ralph candidate because the full parallel signal regressed despite isolated gains. Retain only the validated write-boundary improvement.

Co-authored-by: Copilot <[email protected]>
Copilot-Session: af51c104-57ac-4290-8c40-ca6ef92d4638
@virajmalkar

Copy link
Copy Markdown
Author

Closing in favor of #195, which adds the same Business Applications guidance to the workiq plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants