feat(agents): add B2B sales prospecting & outreach agent template

[saurabhiiitm062]

Description

This PR introduces a new professional agent template: B2B Sales Prospecting & Outreach.

This agent automates the end-to-end sales workflow—finding leads via Apollo, researching companies using web scraping, and drafting personalized outreach emails—while maintaining a strict "Human-in-the-Loop" gate for quality control before any emails are sent.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

Related Issues

Fixes #3991

Changes Made

📁 File Structure

examples/templates/sales_prospecting_agent/
├── README.md
├── __init__.py
├── __main__.py
├── agent.json
├── agent.py
├── config.py
├── mcp_servers.json
├── test_agent.py
└── nodes/
    └── __init__.py 

✅ Implementation Details

• Added new agent template at examples/templates/sales_prospecting_agent/
• Implemented SalesProspectingAgent with a 6-node workflow:
  • Intake
  • Lead Search
  • Company Research
  • Draft Email
  • Human Approval
  • Send Email
• Implemented modular node definitions using NodeSpec
• Added configuration support via config.py
• Added standalone runner via __main__.py
• Added comprehensive README with setup and usage instructions
• Added unit tests (test_agent.py) to validate graph structure and tool registration
• Added mock fallback logic for testing environments without external tools

---

Testing

The following tests were performed:

• Unit tests pass:

uv run python -m pytest examples/templates/sales_prospecting_agent/test_agent.py -v

Lint and Format Tests Pass:

 uv run make check

#Manual Testing

Agent successfully loads in

hive tui 

Intake → Research → Draft → Approval → Send workflow verified

Verified compatibility with available LLM providers

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[saurabhiiitm062]

Hii @bryanadenhq @RichardTang-Aden @TimothyZhang7

Happy to make any changes or improvements based on feedback.
Thanks for reviewing!