Ling0925
/
buster
mirror of https://github.com/buster-so/buster.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

thoughtfulness

This commit is contained in:
dal 2025-04-11 17:04:21 -06:00
parent 573c94e84f
commit cfc314d9eb
No known key found for this signature in database
GPG Key ID: 16F4B0E1E9F61122
5 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api/libs/agents/src/tools/categories/file_tools/common.rs
View File

@ -366,10 +366,12 @@ definitions:
type: array
items:
type: string
description: Multiple y-axis columns can be specified to create multi-line charts. Each column will be represented as a separate line on the chart.
category:
type: array
items:
type: string
description: Used to create multi-line charts with different lines based on categorical values. Especially useful for time series data that combines numeric values with categorical fields, allowing visualization of trends across different categories over time. Alternative to using multiple y-axis columns.
required:
- x
- y

4
api/libs/agents/src/tools/categories/file_tools/create_dashboards.rs
View File

@ -352,7 +352,7 @@ impl ToolExecutor for CreateDashboardFilesTool {
async fn get_dashboard_description() -> String {
if env::var("USE_BRAINTRUST_PROMPTS").is_err() {
return "Creates **new** dashboard files. Use this if no existing dashboard file can fulfill the user's needs. Guard Rail: Do not execute any file creation or modifications until a thorough data catalog search has been completed and reviewed.".to_string();
return "Creates **new** dashboard files. Use this if no existing dashboard file can fulfill the user's needs. Before using this tool, carefully think through the dashboard format, specification, and structure to ensure it meets requirements. Guard Rail: Do not execute any file creation or modifications until a thorough data catalog search has been completed and reviewed, and you have a clear understanding of the dashboard specification.".to_string();
}
let client = BraintrustClient::new(None, "96af8b2b-cf3c-494f-9092-44eb3d5b96ff").unwrap();
@ -360,7 +360,7 @@ async fn get_dashboard_description() -> String {
Ok(message) => message,
Err(e) => {
eprintln!("Failed to get prompt system message: {}", e);
"Creates **new** dashboard files. Use this if no existing dashboard file can fulfill the user's needs. Guard Rail: Do not execute any file creation or modifications until a thorough data catalog search has been completed and reviewed.".to_string()
"Creates **new** dashboard files. Use this if no existing dashboard file can fulfill the user's needs. Before using this tool, carefully think through the dashboard format, specification, and structure to ensure it meets requirements. Guard Rail: Do not execute any file creation or modifications until a thorough data catalog search has been completed and reviewed, and you have a clear understanding of the dashboard specification.".to_string()
}
}
}

4
api/libs/agents/src/tools/categories/file_tools/create_metrics.rs
View File

@ -287,7 +287,7 @@ impl ToolExecutor for CreateMetricFilesTool {
async fn get_create_metrics_description() -> String {
if env::var("USE_BRAINTRUST_PROMPTS").is_err() {
return "Creates metric configuration files with YAML content following the metric schema specification".to_string();
return "Creates metric configuration files with YAML content following the metric schema specification. Before using this tool, carefully consider the appropriate visualization type (bar, line, scatter, pie, combo, metric, table) and its specific configuration requirements. Each visualization has unique axis settings, formatting options, and data structure needs that must be thoroughly planned to create effective metrics.".to_string();
}
let client = BraintrustClient::new(None, "96af8b2b-cf3c-494f-9092-44eb3d5b96ff").unwrap();
@ -295,7 +295,7 @@ async fn get_create_metrics_description() -> String {
Ok(message) => message,
Err(e) => {
eprintln!("Failed to get prompt system message: {}", e);
"Creates metric configuration files with YAML content following the metric schema specification".to_string()
"Creates metric configuration files with YAML content following the metric schema specification. Before using this tool, carefully consider the appropriate visualization type (bar, line, scatter, pie, combo, metric, table) and its specific configuration requirements. Each visualization has unique axis settings, formatting options, and data structure needs that must be thoroughly planned to create effective metrics.".to_string()
}
}
}

4
api/libs/agents/src/tools/categories/file_tools/modify_dashboards.rs
View File

@ -272,7 +272,7 @@ impl ToolExecutor for ModifyDashboardFilesTool {
async fn get_modify_dashboards_description() -> String {
if env::var("USE_BRAINTRUST_PROMPTS").is_err() {
return "Modifies existing dashboard configuration files by replacing specified content with new content. If the dashboard fundamentally changes, the name should be updated to reflect the changes. However, if the core dashboard topic remains the same, the name should stay unchanged.".to_string();
return "Modifies existing dashboard configuration files by replacing specified content with new content. Before using this tool, carefully think through the dashboard format, specification, and structure to ensure your edits maintain consistency and meet requirements. If the dashboard fundamentally changes, the name should be updated to reflect the changes. However, if the core dashboard topic remains the same, the name should stay unchanged.".to_string();
}
let client = BraintrustClient::new(None, "96af8b2b-cf3c-494f-9092-44eb3d5b96ff").unwrap();
@ -280,7 +280,7 @@ async fn get_modify_dashboards_description() -> String {
Ok(message) => message,
Err(e) => {
eprintln!("Failed to get prompt system message: {}", e);
"Modifies existing dashboard configuration files by replacing specified content with new content. If the dashboard fundamentally changes, the name should be updated to reflect the changes. However, if the core dashboard topic remains the same, the name should stay unchanged.".to_string()
"Modifies existing dashboard configuration files by replacing specified content with new content. Before using this tool, carefully think through the dashboard format, specification, and structure to ensure your edits maintain consistency and meet requirements. If the dashboard fundamentally changes, the name should be updated to reflect the changes. However, if the core dashboard topic remains the same, the name should stay unchanged.".to_string()
}
}
}

4
api/libs/agents/src/tools/categories/file_tools/modify_metrics.rs
View File

@ -354,7 +354,7 @@ impl ToolExecutor for ModifyMetricFilesTool {
async fn get_modify_metrics_description() -> String {
if env::var("USE_BRAINTRUST_PROMPTS").is_err() {
return "Modifies existing metric configuration files by replacing specified content with new content. When modifying a metric's SQL, make sure to also update the name and/or time frame to reflect the changes.".to_string();
return "Modifies existing metric configuration files by replacing specified content with new content. Before using this tool, carefully review the metric YAML specification and thoughtfully plan your edits based on the visualization type and its specific configuration requirements. When modifying a metric's SQL, make sure to also update the name and/or time frame to reflect the changes. Each visualization has unique axis settings, formatting options, and data structure needs that must be considered when making modifications.".to_string();
}
let client = BraintrustClient::new(None, "96af8b2b-cf3c-494f-9092-44eb3d5b96ff").unwrap();
@ -362,7 +362,7 @@ async fn get_modify_metrics_description() -> String {
Ok(message) => message,
Err(e) => {
eprintln!("Failed to get prompt system message: {}", e);
"Modifies existing metric configuration files by replacing specified content with new content. When modifying a metric's SQL, make sure to also update the name and/or time frame to reflect the changes.".to_string()
"Modifies existing metric configuration files by replacing specified content with new content. Before using this tool, carefully review the metric YAML specification and thoughtfully plan your edits based on the visualization type and its specific configuration requirements. When modifying a metric's SQL, make sure to also update the name and/or time frame to reflect the changes. Each visualization has unique axis settings, formatting options, and data structure needs that must be considered when making modifications.".to_string()
}
}
}