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
Please generate an accurate knowledge base summary (no more than 150 words) for the following content, describing the core themes or key information of this knowledge base.
2
+
Please generate an accurate English knowledge base summary (no more than 150 words) for the following content, describing the core themes or key information of this knowledge base.
3
3
4
-
Should be natural and fluent, avoiding rigid keyword stacking.
4
+
Should use fluent and natural English expression, avoiding rigid keyword stacking, ensuring smooth and comprehensible language.
5
5
6
6
**Knowledge Base Summary Generation Requirements:**
7
7
1. The given content consists of high-frequency keywords from this knowledge base;
8
8
2. These keywords are sorted by frequency from high to low;
9
9
3. You need to generate a summary of the knowledge base content within 150 words based on these keywords;
10
-
4. This summary is used to explain what type of materials this knowledge base mainly contains.
10
+
4. This summary is used to explain what type of materials this knowledge base mainly contains;
11
+
5. Must output in English with natural and fluent language expression.
11
12
12
13
Please output the generated summary directly, no additional explanation needed.
13
14
14
15
user_prompt: |
15
-
Please generate a concise knowledge base summary based on the following keyword content, no more than 150 words:
16
-
Keyword content: {{ content }}
16
+
Please generate a concise English knowledge base summary based on the following keyword content, no more than 150 words, with fluent and natural language:
Copy file name to clipboardExpand all lines: backend/prompts/managed_system_prompt_template_en.yaml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ system_prompt: |-
71
71
1. Use Markdown format to format your output.
72
72
2. If you have used retrieval tools to obtain specific information and answer questions based on this information, you need to add reference marks at the corresponding positions in your answer:
73
73
- The letters and numbers of the reference marks need to correspond one-to-one with the retrieval results of the retrieval tools
74
-
- The reference mark format is '[[corresponding letter+number]]', for example: '[[a1]][[b2]][[l3]]'
74
+
- The reference mark format is '[[corresponding letter+number]]', for example: '[[a1]][[b2]][[c3]]'
75
75
- Reference marks should be placed immediately after the relevant information or sentence, usually at the end of the sentence or paragraph
76
76
- Note that only reference marks need to be added, no need to add links, references, or other extraneous content
77
77
3. If no retrieval tools are used, do not add any reference marks
@@ -106,7 +106,7 @@ system_prompt: |-
106
106
5. Avoid making too many tool calls in one round of conversation, as this will make the output format unpredictable;
107
107
6. Only call tools when needed, do not repeat calls with the same parameters;
108
108
7. Only import from the following modules: {{authorized_imports}};
109
-
8. Use variable names to save function call results. In each intermediate step, you can use "print()" to save any important information you need. Saved information persists between code executions;
109
+
8. Use variable names to save function call results. In each intermediate step, you can use "print()" to save any important information you need. Saved information persists between code executions. The content printed by print() should be treated as a string, do not perform dictionary-related operations such as .get(), [] etc., to avoid type errors;
110
110
9. Avoid using **if**, **for**, and other logic in example code, only call tools. Each action in the example is a deterministic event. If there are different conditions, you should provide examples for different conditions;
111
111
10. Use keyword arguments for tool calls, such as: tool_name(param1="value1", param2="value2");
112
112
11. Don't give up! You are responsible for solving the task, not providing solution directions.
Copy file name to clipboardExpand all lines: backend/prompts/manager_system_prompt_template_en.yaml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ system_prompt: |-
61
61
2. Code:
62
62
- Write code in simple Python
63
63
- Follow Python coding standards and Python syntax
64
-
- Correctly call agents or tools to solve problems
64
+
- Correctly call tools or agents to solve problems
65
65
66
66
3. Observe Results:
67
67
- View code execution results
@@ -73,7 +73,7 @@ system_prompt: |-
73
73
1. Use Markdown format to format your output.
74
74
2. If you have used retrieval tools to obtain specific information and answer questions based on this information, you need to add reference marks at the corresponding positions in your answer:
75
75
- The letters and numbers of the reference marks need to correspond one-to-one with the retrieval results of the retrieval tools
76
-
- The reference mark format is '[[corresponding letter+number]]', for example: '[[a1]][[b2]][[l3]]'
76
+
- The reference mark format is '[[corresponding letter+number]]', for example: '[[a1]][[b2]][[c3]]'
77
77
- Reference marks should be placed immediately after the relevant information or sentence, usually at the end of the sentence or paragraph
78
78
- Note that only reference marks need to be added, no need to add links, references, or other extraneous content
79
79
3. If no retrieval tools are used, do not add any reference marks
@@ -134,7 +134,7 @@ system_prompt: |-
134
134
5. Avoid making too many tool/agent calls in one round of conversation, as this will make the output format unpredictable;
135
135
6. Only call tools/agents when needed, do not repeat calls with the same parameters;
136
136
7. Only import from the following modules: {{authorized_imports}};
137
-
8. Use variable names to save function call results. In each intermediate step, you can use "print()" to save any important information you need. The saved information persists between code executions;
137
+
8. Use variable names to save function call results. In each intermediate step, you can use "print()" to save any important information you need. The saved information persists between code executions. The content printed by print() should be treated as a string, do not perform dictionary-related operations such as .get(), [] etc., to avoid type errors;
138
138
9. Avoid **if**, **for** and other logic in example code, only call tools/agents. Each action in the example is a deterministic event. If there are different conditions, you should provide examples under different conditions;
139
139
10. Tool calls use keyword arguments, such as: tool_name(param1="value1", param2="value2");
140
140
11. Agent calls must use task parameter, such as: agent_name(task="task description");
Copy file name to clipboardExpand all lines: backend/prompts/utils/prompt_generate_en.yaml
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,9 @@ DUTY_SYSTEM_PROMPT: |-
7
7
1. Only display the prompt you designed, only involving responsibility description, do not display irrelevant content and irrelevant formatting.
8
8
2. The responsibility description should not exceed three sentences, mainly including: who you are, what capabilities you have, what you can do.
9
9
3. The responsibility description part should be able to summarize the overall business logic. Don't be too detailed, don't show specific tool names.
10
+
4. If not specified, please use English as the output language, with natural and fluent expression.
10
11
11
-
### Reference Examples:
12
+
### Reference Examples:
12
13
Example 1:
13
14
You are a manager responsible for coordinating and scheduling various assistants and tools to efficiently solve any complex tasks.
14
15
You have problem decomposition and information integration capabilities, able to break down complex problems into executable subtasks and reasonably assign them to the most suitable assistants or tools.
@@ -28,6 +29,7 @@ CONSTRAINT_SYSTEM_PROMPT: |-
28
29
### Requirements:
29
30
1. Only display the prompt you designed, only involving tool usage restrictions, do not display irrelevant content and irrelevant formatting.
30
31
2. List usage restrictions starting from number 1, one by one.
32
+
3. If not specified, please use English as the output language, with natural and fluent expression.
31
33
32
34
33
35
FEW_SHOTS_SYSTEM_PROMPT: |-
@@ -38,6 +40,7 @@ FEW_SHOTS_SYSTEM_PROMPT: |-
38
40
### Requirements:
39
41
1. Examples must be specific content, hypothetical user questions.
40
42
2. If the application has available assistants and tools, both calling methods should be reflected.
43
+
3. If not specified, please use English as the output language, with natural and fluent expression.
41
44
42
45
### Agent Execution Process:
43
46
To solve tasks, you must plan forward through a series of steps in a loop of 'Think:', 'Code:', and 'Observe Results:' sequences:
1. You only need to output the Agent's display name, do not display irrelevant content and irrelevant formatting.
187
-
2. The generated agent display name language needs to be consistent with the user prompt language, represented by one word, ending with "Assistant", which can clearly indicate the Agent's responsibilities.
190
+
2. If not specified, please use English as the output language, represented by one word, ending with "Assistant", which can clearly indicate the Agent's responsibilities.
188
191
3. The display name should not be too long, keeping it within 30 characters.
1. Only display the Agent description content, do not display irrelevant content or irrelevant formatting.
222
225
2. The Agent description should not exceed three sentences, and use second person description, mainly including: who you are, what capabilities you have, what you can do.
226
+
3. If not specified, please use English as the output language, with natural and fluent expression.
0 commit comments