You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/orchestrate-sk-multi-agent-solution/6-knowledge-check.yml
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -16,24 +16,24 @@ quiz:
16
16
choices:
17
17
- content: "A human-controlled interface for interacting with AI models"
18
18
isCorrect: false
19
-
explanation: "Incorrect. Agents in the framework are not human-controlled; they are autonomous systems designed to process input and complete tasks."
19
+
explanation: "Incorrect. Agents in the framework aren't human-controlled; they're autonomous systems designed to process input and complete tasks."
20
20
- content: "A storage system used to manage user data"
21
21
isCorrect: false
22
-
explanation: "Incorrect. Agents do not function as data storage systems; they perform tasks based on user interaction and intent."
22
+
explanation: "Incorrect. Agents don't function as data storage systems; they perform tasks based on user interaction and intent."
23
23
- content: "An autonomous system that interacts with users and performs specific tasks based on user input and intent."
24
24
isCorrect: true
25
25
explanation: "Correct. In the Semantic Kernel Agent Framework, agents are autonomous systems that interact with users, interpret input, and perform tasks tailored to the user's needs."
26
26
- content: "How does the Semantic Kernel Agent Framework select the right agent for a task?"
27
27
choices:
28
28
- content: "By random selection"
29
29
isCorrect: false
30
-
explanation: "Incorrect. Agent selection is not random; it is based on analyzing user intent and routing according to specific rules."
30
+
explanation: "Incorrect. Agent selection isn't random; it's based on analyzing user intent and routing according to specific rules."
31
31
- content: "Based on the user's intent and predefined rules"
32
32
isCorrect: true
33
33
explanation: "Correct. The framework uses intent recognition and predefined rules to route queries to the most relevant agent."
34
34
- content: "By the agent's physical location"
35
35
isCorrect: false
36
-
explanation: "Incorrect. Agent selection is not based on physical location but on task relevance and expertise."
36
+
explanation: "Incorrect. Agent selection isn't based on physical location but on task relevance and expertise."
37
37
- content: "What is the role of the Termination Strategy in the Semantic Kernel Agent Framework?"
38
38
choices:
39
39
- content: "It determines when a conversation or task should end"
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/orchestrate-sk-multi-agent-solution/includes/1-introduction.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,15 @@
1
1
AI agents offer a powerful combination of technologies, able to complete tasks with the use of generative AI. However, in some situations, the task required might be larger than is realistic for a single agent. For those scenarios, consider a **multi-agent** solution. A multi-agent solution allows agents to collaborate within the same conversation.
2
2
3
-
Imagine you are trying to address common DevOps challenges such as monitoring application performance, identifying issues, and deploying fixes. A multi-agent system could consist of four specialized agents working collaboratively:
3
+
Imagine you're trying to address common DevOps challenges such as monitoring application performance, identifying issues, and deploying fixes. A multi-agent system could consist of four specialized agents working collaboratively:
4
4
5
5
1. The Monitoring Agent continuously ingests logs and metrics, detects anomalies using natural language processing (NLP), and triggers alerts when issues arise.
6
-
1. The Root Cause Analysis Agent then correlates these anomalies with recent system changes, leveraging machine learning models or predefined rules to pinpoint the root cause of the problem.
6
+
1. The Root Cause Analysis Agent then correlates these anomalies with recent system changes, using machine learning models or predefined rules to pinpoint the root cause of the problem.
7
7
1. Once the root cause is identified, the Automated Deployment Agent takes over to implement fixes or roll back problematic changes by interacting with CI/CD pipelines and executing deployment scripts.
8
8
1. Finally, the Reporting Agent generates detailed reports summarizing the anomalies, root causes, and resolutions, and notifies stakeholders via email or other communication channels.
9
9
10
-
This modular, scalable, and intelligent multi-agent system streamlines the DevOps process, reducing manual intervention and improving efficiency while ensuring timely communication and resolution of issues.
10
+
This modular, scalable, and intelligent multi-agent system streamlines the DevOps process. The agents collaborate to reduce manual intervention and improve efficiency while ensuring timely communication and resolution of issues.
11
11
12
-
In this module, we will explore how to leverage the powerful capabilities of Semantic Kernel to design, implement, and orchestrate intelligent agents that work collaboratively to solve complex problems.
13
-
14
-
In this module, you'll learn how to use the Semantic Kernel Agents Framework to develop your own AI agents that can collaborate for a multi-agent solution.
12
+
In this module, you'll explore how to use the powerful capabilities of Semantic Kernel to design and orchestrate intelligent agents that work collaboratively to solve complex problems. You'll also learn how to use the Semantic Kernel Agents Framework to develop your own AI agents that can collaborate for a multi-agent solution.
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/orchestrate-sk-multi-agent-solution/includes/4-define-chat-completion.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ This unit uses the example multi-agent solution where we have two agents:
7
7
8
8
## Termination strategy
9
9
10
-
A termination strategy ensures that conversations or tasks conclude appropriately, preventing unnecessary messages to the user, limiting resource usage, and improving user experience.
10
+
A termination strategy ensures that conversations or tasks conclude appropriately. This strategy prevents unnecessary messages to the user, limits resource usage, and improves the overall user experience.
11
11
12
-
For example, once the _ReviewingDirectorAgent_has reviewed and approved our scrubbing brush slogan from the _CopywriterAgent_, us humans know the conversation should be over. However, if we don't define when to terminate the conversation, the _CopywriterAgent_ is going to keep submitting slogans unnecessarily.
12
+
For example, once the _ReviewingDirectorAgent_reviews and approves our scrubbing brush slogan from the _CopywriterAgent_, us humans know the conversation should be over. However, if we don't define when to terminate the conversation, the _CopywriterAgent_ is going to keep submitting slogans unnecessarily.
13
13
14
14
### Why use a termination strategy?
15
15
@@ -21,7 +21,7 @@ For example, once the _ReviewingDirectorAgent_ has reviewed and approved our scr
21
21
22
22
Similar to how the selection strategy is specified, developers can specify a termination strategy or use one of the predefined strategies. Termination strategies can also define a maximum number of iterations a conversation should be limited to.
23
23
24
-
Termination strategies can be created by a prompt, such as:
24
+
Termination strategies can be created using a prompt, such as:
25
25
26
26
```python
27
27
prompt="""
@@ -34,12 +34,12 @@ prompt="""
34
34
35
35
You can also specify which agent should determine that termination, which in our case would be _ReviewingDirectorAgent_. The agents to determine termination are also defined in the `AgentGroupChat`.
36
36
37
-
If it makes more sense for a given scenario, developers can also define termination functions explicitly in code. For example, we could define a termination function that checks the most recent history entry for just the word "yes". There are other use-case specific considerations if that route is chosen, such as very explicit agent instructions for approval, but it is an option.
37
+
If it makes more sense for a given scenario, developers can also define termination functions explicitly in code. For example, we could define a termination function that checks the most recent history entry for just the word "yes". There are other use-case specific considerations if that route is chosen, such as explicit agent instructions for approval, but it's an option.
38
38
39
39
### Conversation state
40
40
41
-
Whether you use `AgentGroupChat` for a single-turn or multi-turn conversation, the state is updated to _completed_ once it meets the termination criteria. However, you may want to use the group chat instance again. To keep using the same chat instance, you'll need to reset the completion state to `False`. Without a state reset, the `AgentGroupChat`won't accept new interactions.
41
+
Whether you use `AgentGroupChat` for a single-turn or multi-turn conversation, the state is updated to _completed_ once it meets the termination criteria. However, you may want to use the group chat instance again. To keep using the same chat instance, you'll need to reset the completion state to `False`. Without a state reset, the `AgentGroupChat`can't accept new interactions.
42
42
43
-
In the case of a conversation hitting the maximum number of iterations allowed, the conversation will end but will not be marked as _completed_. In this case, you can extend the conversation without resetting the conversation state.
43
+
When a conversation hits the maximum number of iterations allowed, the conversation will end but won't be marked as _completed_. In this case, you can extend the conversation without resetting the conversation state.
44
44
45
45
By understanding these components, you can better utilize the Semantic Kernel Agent Framework to build intelligent multi-agent systems.
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/orchestrate-sk-multi-agent-solution/includes/5-exercise.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Now it's your opportunity to build a multi agent solution with the Semantic Kernel Agent Framework. In this exercise, you'll create an application that automatically triages and resolves issues presented in log files of a system. Using Azure AI Agents, you'll create an incident manager agent an a devops agent that will collaborate to fix the issues.
1
+
Now it's your opportunity to build a multi agent solution with the Semantic Kernel Agent Framework. In this exercise, you create an application that automatically triages and resolves issues presented in log files of a system. Using Azure AI Agents, you create an incident manager agent and a devops agent that collaborates to fix the issues.
0 commit comments