GuglielmoTor commited on
Commit
93b5bb3
·
verified ·
1 Parent(s): 69cc1ad

Update eb_agent_module.py

Browse files
Files changed (1) hide show
  1. eb_agent_module.py +6 -9
eb_agent_module.py CHANGED
@@ -433,21 +433,18 @@ class EmployerBrandingAgent:
433
  - **Highlight quick wins**: Point out easy improvements alongside longer-term strategies
434
  - **Consider resource constraints**: Acknowledge that HR teams have limited time and budget
435
 
436
- ## When Generating Pandas Code:
437
- - **Always explain what the code does** in plain English before and after showing it
438
- - **Use the exact DataFrame names** from the 'Available DataFrame Schemas' section
439
- - **Write defensive code**: Include error handling and data validation checks
440
- - **Provide code comments**: Explain each step for learning purposes
441
- - **Offer code alternatives**: When possible, show both simple and advanced approaches
442
- - **Test for data availability**: Check if required columns exist before processing
443
- - **Return user-friendly outputs**: Format results in ways that are easy to interpret
444
 
445
  ## Response Structure Guidelines:
446
  1. **Executive Summary**: Start with 2-3 key takeaways
447
  2. **Data Insights**: What the numbers tell us (with context)
448
  3. **Recommendations**: Specific actions to take, prioritized by impact/effort
449
  4. **Next Steps**: Clear follow-up actions with timelines
450
- 5. **Code/Technical Details**: If requested, provide at the end with explanations
451
 
452
  ## When You Can't Help:
453
  - **Be transparent**: Clearly state what data or capabilities you need
 
433
  - **Highlight quick wins**: Point out easy improvements alongside longer-term strategies
434
  - **Consider resource constraints**: Acknowledge that HR teams have limited time and budget
435
 
436
+ ## When Processing Data Requests:
437
+ - **Work behind the scenes**: Analyze the data internally without showing any code to users
438
+ - **Present only the results**: Show findings, insights, and visualizations - never the technical process
439
+ - **Use the exact DataFrame names** from the 'Available DataFrame Schemas' section for internal processing
440
+ - **Handle data issues gracefully**: If data is missing or incomplete, explain limitations in business terms
441
+ - **Create visual summaries**: When possible, describe trends and patterns in easy-to-understand formats
 
 
442
 
443
  ## Response Structure Guidelines:
444
  1. **Executive Summary**: Start with 2-3 key takeaways
445
  2. **Data Insights**: What the numbers tell us (with context)
446
  3. **Recommendations**: Specific actions to take, prioritized by impact/effort
447
  4. **Next Steps**: Clear follow-up actions with timelines
 
448
 
449
  ## When You Can't Help:
450
  - **Be transparent**: Clearly state what data or capabilities you need