Prebuiltcards (#233)

* Add prebuilt cards functionality and related changes

* removed old jsons (still need to update the existing ones too)

* Refactor project templates to remove the Example Agent and update related documentation. Updated the copilot behaviour aswell.

* Merge remote-tracking branch 'origin/dev' into prebuiltcards

* Update SHOW_PREBUILT_CARDS logic to use environment variable for better configuration management
This commit is contained in:
Tushar 2025-09-08 21:22:35 +05:30 committed by GitHub
parent d2c15f6b1f
commit a0734f7013
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
9 changed files with 1500 additions and 1319 deletions

View file

@ -7,7 +7,7 @@ The design of the multi-agent system is represented by the following JSON schema
{workflow_schema}
\`\`\`
If the workflow has an 'Example Agent' as the main agent, it means the user is yet to create the main agent. You should treat the user's first request as a request to plan out and create the multi-agent system.
If the workflow has no agents or an empty startAgent, it means the user is yet to create their first agent. You should treat the user's first request as a request to plan out and create the multi-agent system.
---
`;

View file

@ -116,14 +116,14 @@ I'll add the suggested tools for Google Calendar, web search, and email:
### 2. Create Agents
#### a. Hub Agent (Meeting Assistant Hub)
I'll edit the Example Agent to become the hub agent:
I'll create the hub agent:
\`\`\`copilot_change
// action: edit
// config_type: agent
// name: Example Agent
// name: Meeting Assistant Hub
{
"change_description": "Transformed Example Agent into the main hub agent orchestrating the meeting summary workflow.",
"change_description": "Created the main hub agent orchestrating the meeting summary workflow.",
"config_changes": {
"name": "Meeting Assistant Hub",
"type": "conversation",
@ -241,7 +241,7 @@ searchRelevantTools output:
I'll make the following changes to your workflow:
1. Add the "Get document by id" tool for retrieving the content of a Google Doc.
2. Replace the Example Agent with a single user-facing agent that:
2. Create a single user-facing agent that:
* Asks the user for the Google Doc ID and their question.
* Uses the tool to fetch the document content.
* Answers the user's question based only on the content of the fetched Google Doc (no RAG or external search).
@ -277,14 +277,14 @@ I'm adding the "Get document by id" tool to fetch the content of a Google Doc by
}
\`\`\`
I'm replacing the Example Agent with a user-facing agent that fetches a Google Doc by ID and answers questions based on its content:
I'm creating a user-facing agent that fetches a Google Doc by ID and answers questions based on its content:
\`\`\`copilot_change
// action: edit
// config_type: agent
// name: Example Agent
// name: Meeting Assistant Hub
{
"change_description": "Replaced Example Agent with a user-facing agent that fetches a Google Doc by ID and answers user questions based only on its content.",
"change_description": "Created a user-facing agent that fetches a Google Doc by ID and answers user questions based only on its content.",
"config_changes": {
"name": "Google Doc QnA Assistant",
"type": "conversation",