create-eval-set
Skill486 starsChanged 8 months agoMITView on GitHub
Create a test set CSV file for import into Copilot Studio's in-product Evaluate tab. Reads the agent's topics, instructions, and knowledge sources to generate meaningful test cases with appropriate graders (General quality, Compare meaning, Exact match, etc.). Use when the user asks to create, prepare, or generate evaluation test cases for their agent.
In this repository30 other files it gives its agents.
- add-actionSkill
- add-adaptive-cardSkill
- add-generative-answersSkill
- add-global-variableSkill
- add-knowledgeSkill
- add-nodeSkill
- add-other-agentsSkill
- analyze-evalsSkill
- chat-directlineSkill
- chat-sdkSkill
- chat-with-agentSkill
- clone-agentSkill
- create-evalSkill
- detect-modeSkill
- directline-chatSkill
- edit-actionSkill
- edit-agentSkill
- edit-triggersSkill
- int-patternsSkill
- int-project-contextSkill
- int-referenceSkill
- list-kindsSkill
- list-topicsSkill
- lookup-schemaSkill
- manage-agentSkill
- new-topicSkill
- run-evalSkill
- run-tests-kitSkill
- test-authSkill
- validateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Create a test set CSV file that can be imported into Copilot Studio's Evaluate tab for in-product agent evaluation.
- Distinctive: line 19
Read the agent's YAML files to understand what it does:
- Very specific: line 22
Read agent.mcs.yml — get the agent's instructions, description, and capabilities
- Very specific: line 23
Read settings.mcs.yml — check orchestration mode (generative vs classic)
- Distinctive: line 25
Read key topics (especially non-system ones) — understand trigger phrases, conversation flows, expected behaviors
- Distinctive: line 26
Check for knowledge sources, actions, and connected tools
- Distinctive: line 30
Create test cases that cover:
- Distinctive: line 46
Write expected responses with this in mind:
- Very specific: line 49
Leave expectedResponse empty for questions that only need General quality (it works without expected responses)
- Distinctive: line 65
Write the CSV file using the Write tool.
- Distinctive: line 86
Use double quotes around all values
- Distinctive: line 109
After writing the CSV, tell the user:
- Distinctive: line 120
After import, some things can only be configured in the UI:
≈ “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
Create Evaluation Test Set
Create a test set CSV file that can be imported into Copilot Studio's Evaluate tab for in-product agent evaluation.
Phase 1: Understand the Agent
Read the agent's YAML files to understand what it does:
Glob: **/agent.mcs.yml— find the agent- Read
agent.mcs.yml— get the agent's instructions, description, and capabilities - Read
settings.mcs.yml— check orchestration mode (generative vs classic) Glob: **/topics/*.mcs.yml— list all topics- Read key topics (especially non-system ones) — understand trigger phrases, conversation flows, expected behaviors
- Check for knowledge sources, actions, and connected tools
Phase 2: Design Test Cases
Create test cases that cover:
| Category | What to test | Example |
| Core functionality | Main topics and capabilities | Questions matching trigger phrases |
| Knowledge/generative | Knowledge source responses | Questions the agent should answer from its knowledge |
| System topics | Greeting, Escalation, Goodbye, Thank You, Fallback | "Hi", "I want to speak to a person", "Goodbye" |
| Edge cases | Out-of-scope, ambiguous, off-topic | "Tell me a joke", "Book a flight for me" |
| Boundary testing | Things the agent should NOT do | Actions beyond its capabilities |
Aim for 10–25 test cases with good coverage across categories.
Phase 3: Write the Expected Responses
The CSV import only supports two columns: question and expectedResponse. Test methods cannot be set via CSV import — they are configured in the UI after import. The default test method (General quality) is applied to all imported test cases.
Write expected responses with this in mind:
- For questions where you want General quality grading: write behavioral descriptions ("The response should recommend hotels in Paris with relevant details")
- For questions where you'll later switch to Compare meaning or Exact match in the UI: write realistic agent replies that the grader can compare against
- Leave
expectedResponseempty for questions that only need General quality (it works without expected responses)
Available test methods (configured in UI after import)
| Test method | What it measures | Requires expected response? |
| General quality (default) | AI-graded quality: relevance, completeness, groundedness, abstention | No (but recommended as a rubric) |
| Compare meaning | Semantic similarity — compares meaning/intent | Yes |
| Text similarity | Cosine similarity of text | Yes, configurable pass threshold |
| Exact match | Character-for-character match | Yes |
| Keyword match | Response contains expected keywords/phrases | Yes (keywords added in UI) |
| Capability use | Agent called expected tools/topics | Configured in UI |
| Custom | Custom grader with your own instructions and labels | Configured in UI |
Phase 4: Write the CSV
Write the CSV file using the Write tool. The format must be:
"question","expectedResponse"
"User question here","Expected agent response or behavioral rubric"
"Question without expected response",Column specification
| Column | Required | Description |
question | Yes | The user message to send to the agent. Max 1,000 characters. |
expectedResponse | No | The expected response or behavioral rubric. Leave empty if not needed. |
Important: The Testing method column is not supported on import — it is ignored. All imported test cases get the default test method (General quality). Configure other test methods in the UI after import.
Rules
- Max 100 questions per test set
- Max 1,000 characters per question (including spaces)
- File must be
.csvformat - Use double quotes around all values
- For questions that will use General quality: write expected responses as behavioral descriptions
- For questions that will use Compare meaning or Exact match: write expected responses as realistic agent replies
Expected response examples
Behavioral rubric (for General quality):
"Find me a hotel in Paris","The response should include hotel recommendations in Paris with relevant details like names, locations, or prices."Realistic reply (for Compare meaning — set method in UI after import):
"Hi there","Hello! How can I help you today?"Exact expected text (for Exact match — set method in UI after import):
"What is 2+2?","4"Phase 5: Instruct the User
After writing the CSV, tell the user:
To import into Copilot Studio:
- Open your agent in Copilot Studio
- Go to the Evaluate tab
- Click New evaluation > Single response
- Drag or browse for the CSV file
- Review the imported test cases and adjust if needed
- Optionally add more test methods (Capability use, Custom) in the UI
- Click Evaluate to run, or Save to run later
After import, some things can only be configured in the UI:
- Pass thresholds for Compare meaning and Text similarity
- Keywords for Keyword match test cases
- Expected capabilities for Capability use test cases
- Custom grader instructions and labels
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.

