Skip to content

adding retrieve skill to work-iq#163

Open
adrian05-ms wants to merge 3 commits into
mainfrom
users/christiano/adding-retrieve-skill
Open

adding retrieve skill to work-iq#163
adrian05-ms wants to merge 3 commits into
mainfrom
users/christiano/adding-retrieve-skill

Conversation

@adrian05-ms

Copy link
Copy Markdown

This pull request updates the WorkIQ skill documentation to introduce and emphasize the new retrieve tool as the default for Microsoft 365 (M365) search, find, and lookup operations. The changes clarify when to use retrieve, ask, or entity tools, and add comprehensive reference documentation for retrieve, including usage guidance, parameters, response structure, and examples.

Key documentation and guidance improvements:

1. Introduction and Emphasis on retrieve as Default Search Tool

  • The SKILL.md now instructs agents to use retrieve as the default for M365 search/find/lookup reads, reserving ask only for cases where synthesis is truly needed. The tool selection guidance and example table have been updated throughout to reflect this new default. [1] [2] [3]

2. Detailed retrieve Tool Reference

  • A new file, references/retrieve-work-iq.md, provides in-depth documentation for the retrieve tool, including parameter descriptions, supported strategies, response structure, metadata facets, runtime handling, error cases, and many usage examples.

3. Expanded Guidance on Tool Selection

  • The documentation now includes a clear workflow and scenario tables to help users choose between retrieve, ask, and entity tools, with latency expectations and escalation paths. [1] [2]

4. Documentation Cross-References Updated

  • The SKILL.md and reference lists now link to the new retrieve documentation for further details and troubleshooting.

5. Improved Clarity and Consistency

  • Language throughout SKILL.md has been revised for clarity, ensuring consistent messaging about when and why to use each tool, and highlighting best practices for grounding, latency, and error handling. [1] [2]

These changes ensure agents and developers are directed to use the most efficient and appropriate tool for their M365 data queries, improving both performance and result quality.

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