Skip to content

Add Copilot Studio describer agent - #173

Open
Giorgio Ughini (GiorgioUghini) wants to merge 3 commits into
release/2026-W21from
giorgioughini/agent-describer
Open

Add Copilot Studio describer agent#173
Giorgio Ughini (GiorgioUghini) wants to merge 3 commits into
release/2026-W21from
giorgioughini/agent-describer

Conversation

@GiorgioUghini

@GiorgioUghini Giorgio Ughini (GiorgioUghini) commented May 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add a directly invoked, read-only copilot-studio-describer sub-agent for explaining what an existing Copilot Studio agent does.
  • Require the report to include functional user stories when useful, grounded only in local files or clarification answers.
  • Require richer evidence for knowledge sources, explicit SearchAndSummarizeContent presence/absence, and a dedicated active settings/capabilities explanation that separates agent-level settings from topic usage.
  • Update docs and issue template options, add an agent-description eval scenario, and fix eval HTML report writing on Windows by using UTF-8.

What I'm doing

This PR introduces a detached description-only agent for users who want to understand a cloned Copilot Studio agent without authoring, testing, deployment, troubleshooting, or pattern-recommendation behavior. It is intentionally not wired into hooks/system-prompt.md, so it only appears when invoked directly.

The describer now goes beyond a simple summary: it explains active settings and capabilities with YAML/file evidence, calls out whether capabilities are merely configured or actually used by topics, identifies knowledge-source names/types/visible references, and explicitly states whether SearchAndSummarizeContent is present.

Validation

  • node evals\run.js --scenario agent-description --parallel 1 — 31/31 checks passed

Introduce a read-only describer sub-agent for direct invocation, document it, and add eval coverage for generated reports including user stories.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Require richer knowledge-source evidence, explicit SearchAndSummarizeContent usage, and a dedicated active settings/capabilities explanation in describer reports.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Refine the describer prompt so knowledge-source evidence focuses on visible names, descriptions, and URLs, and active settings are explained as agent-level capabilities when they are not topic-specific.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant