Merge origin/main into 55-configsyaml-condivisi
Resolved conflict in configs.yaml.example: - Kept larger model configurations (14b, 32b) with comments from main - This aligns with the purpose of .example file showing all available configurations
This commit is contained in:
Simone Garau
3
.gitignore
vendored
3
.gitignore
vendored
@@ -181,3 +181,6 @@ cython_debug/
|
||||
|
||||
# Gradio
|
||||
.gradio/
|
||||
|
||||
# chat
|
||||
chat.json
|
||||
|
||||
60
PROMTP DIFFERENCES.md
Normal file
60
PROMTP DIFFERENCES.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# Differenze fra prompt
|
||||
Resoconto fatto da Claude 4.5
|
||||
|
||||
## Query Check
|
||||
- Prolisso (~50 righe), regole ripetitive
|
||||
- Mancava contesto temporale
|
||||
+ Conciso (~40 righe), regole chiare
|
||||
+ Aggiunto {{CURRENT_DATE}} placeholder (sostituito automaticamente)
|
||||
+ Schema JSON singolo e diretto
|
||||
|
||||
## Team Market
|
||||
- Non enfatizzava priorità dati API
|
||||
- Mancavano timestamp nei report
|
||||
+ Sezione "CRITICAL DATA RULE" su priorità real-time
|
||||
+ Timestamp OBBLIGATORI per ogni prezzo
|
||||
+ Richiesta fonte API esplicita
|
||||
+ Warning se dati parziali/incompleti
|
||||
+ **DIVIETO ESPLICITO** di inventare prezzi placeholder
|
||||
|
||||
## Team News
|
||||
- Output generico senza date
|
||||
- Non distingueva dati freschi/vecchi
|
||||
+ Date pubblicazione OBBLIGATORIE
|
||||
+ Warning se articoli >3 giorni
|
||||
+ Citazione fonti API
|
||||
+ Livello confidenza basato su quantità/consistenza
|
||||
|
||||
## Team Social
|
||||
- Sentiment senza contesto temporale
|
||||
- Non tracciava platform/engagement
|
||||
+ Timestamp post OBBLIGATORI
|
||||
+ Warning se post >2 giorni
|
||||
+ Breakdown per platform (Reddit/X/4chan)
|
||||
+ Livello engagement e confidenza
|
||||
|
||||
## Team Leader
|
||||
- Non prioritizzava dati freschi da agenti
|
||||
- Mancava tracciamento recency
|
||||
+ Sezione "CRITICAL DATA PRINCIPLES" (7 regole, aggiunte 2)
|
||||
+ "Never Override Fresh Data" - divieto esplicito
|
||||
+ Sezioni "Data Freshness" e "Sources" obbligatorie
|
||||
+ Timestamp per OGNI blocco dati
|
||||
+ Metadata espliciti su recency
|
||||
+ **NEVER FABRICATE** - divieto di inventare dati
|
||||
+ **NO EXAMPLES AS DATA** - divieto di usare dati esempio come dati reali
|
||||
|
||||
## Report Generation
|
||||
- Formattazione permissiva
|
||||
- Non preservava timestamp/sources
|
||||
+ "Data Fidelity" rule
|
||||
+ "Preserve Timestamps" obbligatorio
|
||||
+ Lista ❌ DON'T / ✅ DO chiara (aggiunte 2 regole)
|
||||
+ Esempio conditional logic
|
||||
+ **NEVER USE PLACEHOLDERS** - divieto di scrivere "N/A" o "Data not available"
|
||||
+ **NO EXAMPLE DATA** - divieto di usare prezzi placeholder
|
||||
|
||||
## Fix Tecnici Applicati
|
||||
1. **`__init__.py` modificato**: Il placeholder `{{CURRENT_DATE}}` ora viene sostituito automaticamente con `datetime.now().strftime("%Y-%m-%d")` al caricamento dei prompt
|
||||
2. **Regole rafforzate**: Aggiunte regole esplicite contro l'uso di dati placeholder o inventati
|
||||
3. **Conditional rendering più forte**: Specificato che se una sezione manca, va COMPLETAMENTE omessa (no headers, no "N/A")
|
||||
@@ -35,6 +35,12 @@ models:
|
||||
label: Qwen 3 (4B)
|
||||
- name: qwen3:1.7b
|
||||
label: Qwen 3 (1.7B)
|
||||
- name: qwen3:32b
|
||||
label: Qwen 3 (32B)
|
||||
- name: qwen3:14b
|
||||
label: Qwen 3 (14B)
|
||||
- name: phi4-mini:3.8b
|
||||
label: Phi 4 mini (3.8b)
|
||||
|
||||
api:
|
||||
retry_attempts: 3
|
||||
@@ -45,7 +51,7 @@ api:
|
||||
|
||||
agents:
|
||||
strategy: Conservative
|
||||
team_model: qwen3:4b
|
||||
team_leader_model: qwen3:8b
|
||||
query_analyzer_model: qwen3:8b
|
||||
report_generation_model: qwen3:8b
|
||||
team_model: qwen3:14b # the agents
|
||||
team_leader_model: gemini-2.0-flash # the team leader
|
||||
query_analyzer_model: qwen3:14b # query check
|
||||
report_generation_model: qwen3:32b # ex predictor
|
||||
|
||||
113
docs/Current_Architecture.md
Normal file
113
docs/Current_Architecture.md
Normal file
@@ -0,0 +1,113 @@
|
||||
# Stato Attuale: Architettura e Flussi (upo-appAI)
|
||||
|
||||
Sintesi dell’architettura attuale e del flusso runtime dell’app, con diagrammi compatti e riferimenti ai componenti principali.
|
||||
|
||||
## Panorama Componenti
|
||||
|
||||
- `src/app/__main__.py`: Entrypoint. Avvia interfaccia Gradio (`ChatManager`) e bot Telegram (`TelegramApp`).
|
||||
- `interface/chat.py`: UI Gradio. Gestisce storico chat, chiama `Pipeline.interact()`.
|
||||
- `interface/telegram_app.py`: Bot Telegram. Gestisce conversazione, configura modelli/strategia, esegue `Pipeline.interact_async()` e genera PDF.
|
||||
- `agents/core.py`: Definisce `PipelineInputs`, agenti (`Team`, `Query Check`, `Report Generator`) e strumenti (Market/News/Social).
|
||||
- `agents/pipeline.py`: Orchestrazione via `agno.workflow`. Steps: Query Check → Gate → Info Recovery (Team) → Report Generation.
|
||||
- `agents/prompts/…`: Istruzioni per Team Leader, Market/News/Social agents, Query Check e Report Generation.
|
||||
- `api/tools/*.py`: Toolkits aggregati (MarketAPIsTool, NewsAPIsTool, SocialAPIsTool) basati su `WrapperHandler`.
|
||||
- `api/*`: Wrappers per provider esterni (Binance, Coinbase, CryptoCompare, YFinance, NewsAPI, GoogleNews, CryptoPanic, Reddit, X, 4chan).
|
||||
- `api/wrapper_handler.py`: Fallback con retry e try_all sui wrappers.
|
||||
- `configs.py`: Config app, modelli, strategie, API e caricamento da `configs.yaml`/env.
|
||||
|
||||
## Architettura (Overview)
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
U[User] --> I{Interfacce}
|
||||
I -->|Gradio| CM[ChatManager]
|
||||
I -->|Telegram| TG[TelegramApp]
|
||||
CM --> PL[Pipeline]
|
||||
TG --> PL
|
||||
PL --> WF[Workflow\nQuery Check → Gate → Info Recovery → Report Generation]
|
||||
WF --> TM[Team Leader + Members]
|
||||
TM --> T[Tools\nMarket or News or Social]
|
||||
T --> W[Wrappers]
|
||||
W --> EX[External APIs]
|
||||
WF --> OUT[Report]
|
||||
TG --> PDF[MarkdownPdf\ninvio documento]
|
||||
CM --> OUT
|
||||
```
|
||||
|
||||
## Sequenza (Telegram)
|
||||
|
||||
```mermaid
|
||||
sequenceDiagram
|
||||
participant U as User
|
||||
participant TG as TelegramBot
|
||||
participant PL as Pipeline
|
||||
participant WF as Workflow
|
||||
participant TL as TeamLeader
|
||||
participant MK as MarketTool
|
||||
participant NW as NewsTool
|
||||
participant SC as SocialTool
|
||||
participant API as External APIs
|
||||
|
||||
U->>TG: /start + messaggio
|
||||
TG->>PL: PipelineInputs(query, modelli, strategia)
|
||||
PL->>WF: build_workflow()
|
||||
WF->>WF: Step: Query Check
|
||||
alt is_crypto == true
|
||||
WF->>TL: Step: Info Recovery
|
||||
TL->>MK: get_products / get_historical_prices
|
||||
MK->>API: Binance/Coinbase/CryptoCompare/YFinance
|
||||
TL->>NW: get_latest_news / get_top_headlines
|
||||
NW->>API: NewsAPI/GoogleNews/CryptoPanic/DuckDuckGo
|
||||
TL->>SC: get_top_crypto_posts
|
||||
SC->>API: Reddit/X/4chan
|
||||
WF->>TL: Step: Report Generation
|
||||
else
|
||||
WF-->>PL: Stop workflow (non-crypto)
|
||||
end
|
||||
PL-->>TG: Report (Markdown)
|
||||
TG->>TG: Genera PDF e invia
|
||||
```
|
||||
|
||||
## Workflow & Agenti
|
||||
|
||||
- Step 1: `Query Check` (Agent) — valida la natura crypto della richiesta, output schema `QueryOutputs` (`response`, `is_crypto`).
|
||||
- Step 2: Gate — interrompe se `is_crypto == false`.
|
||||
- Step 3: `Info Recovery` (Team) — TeamLeader orchestration con `PlanMemoryTool` e Reasoning, dispatch agli agenti Market/News/Social.
|
||||
- Step 4: `Report Generation` (Agent) — sintetizza i risultati nel report finale (stringa Markdown).
|
||||
|
||||
## Tools & Wrappers
|
||||
|
||||
- MarketAPIsTool → `BinanceWrapper`, `YFinanceWrapper`, `CoinBaseWrapper`, `CryptoCompareWrapper`.
|
||||
- NewsAPIsTool → `GoogleNewsWrapper`, `DuckDuckGoWrapper`, `NewsApiWrapper`, `CryptoPanicWrapper`.
|
||||
- SocialAPIsTool → `RedditWrapper`, `XWrapper`, `ChanWrapper`.
|
||||
- `WrapperHandler`:
|
||||
- `try_call` con retry per wrapper corrente, fallback sequenziale.
|
||||
- `try_call_all` per aggregare risultati multipli.
|
||||
- Configurabile via `set_retries(attempts, delay_seconds)`.
|
||||
|
||||
## Configurazione & Modelli
|
||||
|
||||
- Modelli (default): `gemini-2.0-flash` per Team, Team Leader, Query Analyzer, Report Generator.
|
||||
- Strategie: es. `Conservative` (descrizione testuale). Selezionabili da UI.
|
||||
- `configs.yaml` e variabili env determinano modelli, porta server (`AppConfig.port`) e opzioni sharing Gradio.
|
||||
|
||||
## Variabili d’Ambiente (usate dai wrappers)
|
||||
|
||||
- `TELEGRAM_BOT_TOKEN` — Bot Telegram.
|
||||
- `COINBASE_API_KEY`, `COINBASE_API_SECRET` — Coinbase Advanced Trade.
|
||||
- `CRYPTOCOMPARE_API_KEY` — CryptoCompare.
|
||||
- `NEWS_API_KEY` — NewsAPI.
|
||||
- `CRYPTOPANIC_API_KEY` (+ opzionale `CRYPTOPANIC_API_PLAN`) — CryptoPanic.
|
||||
- `REDDIT_API_CLIENT_ID`, `REDDIT_API_CLIENT_SECRET` — Reddit (PRAW).
|
||||
- `X_API_KEY` — rettiwt API key (CLI richiesto).
|
||||
|
||||
## Note di Implementazione
|
||||
|
||||
- I wrappers sono prevalentemente sincroni; la Pipeline usa esecuzione asincrona per il workflow (`interact_async`), con stream di eventi dai `agno.workflow` steps.
|
||||
- Il Team Leader segue prompt comportamentale: ciclo di pianificazione/esecuzione/aggiornamento task con `PlanMemoryTool`.
|
||||
- L’output Telegram allega un PDF generato da `markdown_pdf`. La UI Gradio restituisce testo formattato.
|
||||
|
||||
## Test & Copertura (repo)
|
||||
|
||||
- Test unitari/integrati in `tests/` per wrappers (Market/News/Social), tools e handler.
|
||||
- Esecuzione consigliata: `pytest -q` con variabili d’ambiente correttamente impostate (alcuni test richiedono API keys).
|
||||
51
docs/Docs_Obsolescenza_Report.md
Normal file
51
docs/Docs_Obsolescenza_Report.md
Normal file
@@ -0,0 +1,51 @@
|
||||
# Report Obsolescenza Documenti (docs/)
|
||||
|
||||
Valutazione dei documenti esistenti rispetto allo stato attuale del codice.
|
||||
|
||||
## Valutazione Documenti
|
||||
|
||||
- `App_Architecture_Diagrams.md`
|
||||
- Stato: parzialmente aggiornato.
|
||||
- Criticità: contiene sezioni su "Signers Architecture" (src/app/signers/…) che non esistono nel repo attuale; riferimenti a auto-detection provider non presenti esplicitamente nei wrappers (l’attuale gestione usa `WrapperHandler` e assert su env). Alcuni numeri/esempi sono illustrativi.
|
||||
- Azioni: mantenere i diagrammi generali; rimuovere/aggiornare la sezione Signers; allineare provider e flusso al workflow `Query Check → Info Recovery → Report Generation`.
|
||||
|
||||
- `Async_Implementation_Detail.md`
|
||||
- Stato: aspirazionale/roadmap tecnica.
|
||||
- Criticità: la Pipeline è già asincrona per il workflow (`interact_async`), ma i singoli wrappers sono sincroni; il documento descrive dettagli di async su MarketAgent che non esiste come classe separata, e prevede parallelizzazione sui provider non implementata nei wrappers.
|
||||
- Azioni: mantenere come proposta di miglioramento; etichettare come "future work"; evitare di confondere con stato attuale.
|
||||
|
||||
- `Market_Data_Implementation_Plan.md`
|
||||
- Stato: piano di lavoro (utile).
|
||||
- Criticità: parla di Binance mock/signers; nel codice attuale esiste `BinanceWrapper` reale (autenticato) e non ci sono signers; la sezione aggregazione JSON è coerente come obiettivo ma non implementata nativamente dai tools (aggregazione base è gestita da `WrapperHandler.try_call_all`).
|
||||
- Azioni: aggiornare riferimenti a `BinanceWrapper` reale; chiarire che l’aggregazione avanzata è un obiettivo; mantenere come guida.
|
||||
|
||||
- `Piano di Sviluppo.md`
|
||||
- Stato: generico e parzialmente disallineato.
|
||||
- Criticità: fa riferimento a stack (LangChain/LlamaIndex) non presente; ruoli degli agenti con naming differente; database/persistenza non esiste nel codice.
|
||||
- Azioni: etichettare come documento legacy; mantenerlo solo se serve come ispirazione; altrimenti spostarlo in `docs/legacy/`.
|
||||
|
||||
- `Progetto Esame.md`
|
||||
- Stato: descrizione obiettivo.
|
||||
- Criticità: allineata come visione; non problematica.
|
||||
- Azioni: mantenere.
|
||||
|
||||
## Raccomandazioni
|
||||
|
||||
- Aggiornare `App_Architecture_Diagrams.md` rimuovendo la sezione "Signers Architecture" e allineando i diagrammi al workflow reale (`agents/pipeline.py`).
|
||||
- Aggiungere `Current_Architecture.md` (presente) come riferimento principale per lo stato attuale.
|
||||
- Spostare `Piano di Sviluppo.md` in `docs/legacy/` o eliminarlo se non utile.
|
||||
- Annotare `Async_Implementation_Detail.md` e `Market_Data_Implementation_Plan.md` come "proposals"/"future work".
|
||||
|
||||
## Elenco Documenti Obsoleti o Parzialmente Obsoleti
|
||||
|
||||
- Parzialmente Obsoleti:
|
||||
- `App_Architecture_Diagrams.md` (sezione Signers, parti di provider detection)
|
||||
- `Async_Implementation_Detail.md` (dettagli Async MarketAgent non implementati)
|
||||
- `Market_Data_Implementation_Plan.md` (Binance mock/signers)
|
||||
|
||||
- Legacy/Non allineato:
|
||||
- `Piano di Sviluppo.md` (stack e ruoli non corrispondenti al codice)
|
||||
|
||||
## Nota
|
||||
|
||||
Queste raccomandazioni non rimuovono immediatamente file: il mantenimento storico può essere utile. Se desideri, posso eseguire ora lo spostamento in `docs/legacy/` o la cancellazione mirata dei documenti non necessari.
|
||||
80
docs/Flow_Sequence_Diagrams.md
Normal file
80
docs/Flow_Sequence_Diagrams.md
Normal file
@@ -0,0 +1,80 @@
|
||||
# Diagrammi di Flusso e Sequenza (Sintesi)
|
||||
|
||||
Documentazione breve con blocchi testuali e mermaid per flussi principali.
|
||||
|
||||
## Flusso Gradio Chat
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
U[User] --> CH(ChatInterface)
|
||||
CH --> RESP[gradio_respond]
|
||||
RESP --> PL(Pipeline.interact)
|
||||
PL --> WF(Workflow run)
|
||||
WF --> OUT(Report)
|
||||
CH --> HIST[history update]
|
||||
```
|
||||
|
||||
## Flusso Telegram Bot
|
||||
|
||||
```
|
||||
/start
|
||||
│
|
||||
├─> CONFIGS state
|
||||
│ ├─ Model Team ↔ choose_team(index)
|
||||
│ ├─ Model Output ↔ choose_team_leader(index)
|
||||
│ └─ Strategy ↔ choose_strategy(index)
|
||||
│
|
||||
└─> Text message → __start_team
|
||||
└─ run team → Pipeline.interact_async
|
||||
├─ build_workflow
|
||||
├─ stream events (Query Check → Gate → Info Recovery → Report)
|
||||
└─ send PDF (markdown_pdf)
|
||||
```
|
||||
|
||||
## Pipeline Steps (Workflow)
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A[QueryInputs] --> B[Query Check Agent]
|
||||
B -->|is_crypto true| C[Team Info Recovery]
|
||||
B -->|is_crypto false| STOP((Stop))
|
||||
C --> D[Report Generation Agent]
|
||||
D --> OUT[Markdown Report]
|
||||
```
|
||||
|
||||
## Team Leader Loop (PlanMemoryTool)
|
||||
|
||||
```
|
||||
Initialize Plan with tasks
|
||||
Loop until no pending tasks:
|
||||
- Get next pending task
|
||||
- Dispatch to specific Agent (Market/News/Social)
|
||||
- Update task status (completed/failed)
|
||||
- If failed & scope comprehensive → add retry task
|
||||
After loop:
|
||||
- List all tasks & results
|
||||
- Synthesize final report
|
||||
```
|
||||
|
||||
## Tools Aggregazione
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
TL[Team Leader] --> MT[MarketAPIsTool]
|
||||
TL --> NT[NewsAPIsTool]
|
||||
TL --> ST[SocialAPIsTool]
|
||||
MT --> WH(WrapperHandler)
|
||||
NT --> WH
|
||||
ST --> WH
|
||||
WH --> W1[Binance]
|
||||
WH --> W2[Coinbase]
|
||||
WH --> W3[CryptoCompare]
|
||||
WH --> W4[YFinance]
|
||||
WH --> N1[NewsAPI]
|
||||
WH --> N2[GoogleNews]
|
||||
WH --> N3[CryptoPanic]
|
||||
WH --> N4[DuckDuckGo]
|
||||
WH --> S1[Reddit]
|
||||
WH --> S2[X]
|
||||
WH --> S3[4chan]
|
||||
```
|
||||
@@ -13,7 +13,9 @@ class PlanMemoryTool(Toolkit):
|
||||
def __init__(self):
|
||||
self.tasks: list[Task] = []
|
||||
Toolkit.__init__(self, # type: ignore[call-arg]
|
||||
instructions="This tool manages an execution plan. Add tasks, get the next pending task, update a task's status (completed, failed) and result, or list all tasks.",
|
||||
instructions="Provides stateful, persistent memory for the Team Leader. " \
|
||||
"This is your primary to-do list and state tracker. " \
|
||||
"Use it to create, execute step-by-step, and record the results of your execution plan.",
|
||||
tools=[
|
||||
self.add_tasks,
|
||||
self.get_next_pending_task,
|
||||
@@ -23,7 +25,16 @@ class PlanMemoryTool(Toolkit):
|
||||
)
|
||||
|
||||
def add_tasks(self, task_names: list[str]) -> str:
|
||||
"""Adds multiple new tasks to the plan with 'pending' status."""
|
||||
"""
|
||||
Adds one or more new tasks to the execution plan with a 'pending' status.
|
||||
If a task with the same name already exists, it will not be added again.
|
||||
|
||||
Args:
|
||||
task_names (list[str]): A list of descriptive names for the tasks to be added.
|
||||
|
||||
Returns:
|
||||
str: A confirmation message, e.g., "Added 3 new tasks."
|
||||
"""
|
||||
count = 0
|
||||
for name in task_names:
|
||||
if not any(t['name'] == name for t in self.tasks):
|
||||
@@ -32,14 +43,34 @@ class PlanMemoryTool(Toolkit):
|
||||
return f"Added {count} new tasks."
|
||||
|
||||
def get_next_pending_task(self) -> Task | None:
|
||||
"""Retrieves the first task that is still 'pending'."""
|
||||
"""
|
||||
Retrieves the *first* task from the plan that is currently in 'pending' status.
|
||||
This is used to fetch the next step in the execution plan.
|
||||
|
||||
Returns:
|
||||
Task | None: A Task object (dict) with 'name', 'status', and 'result' keys,
|
||||
or None if no tasks are pending.
|
||||
"""
|
||||
for task in self.tasks:
|
||||
if task["status"] == "pending":
|
||||
return task
|
||||
return None
|
||||
|
||||
def update_task_status(self, task_name: str, status: Literal["completed", "failed"], result: str | None = None) -> str:
|
||||
"""Updates the status and result of a specific task by its name."""
|
||||
"""
|
||||
Updates the status and result of a specific task, identified by its unique name.
|
||||
This is crucial for tracking the plan's progress after a step is executed.
|
||||
|
||||
Args:
|
||||
task_name (str): The exact name of the task to update (must match one from add_tasks).
|
||||
status (Literal["completed", "failed"]): The new status for the task.
|
||||
result (str | None, optional): An optional string describing the outcome or result
|
||||
of the task (e.g., a summary, an error message).
|
||||
|
||||
Returns:
|
||||
str: A confirmation message (e.g., "Task 'Task Name' updated to completed.")
|
||||
or an error message if the task is not found.
|
||||
"""
|
||||
for task in self.tasks:
|
||||
if task["name"] == task_name:
|
||||
task["status"] = status
|
||||
@@ -49,7 +80,14 @@ class PlanMemoryTool(Toolkit):
|
||||
return f"Error: Task '{task_name}' not found."
|
||||
|
||||
def list_all_tasks(self) -> list[str]:
|
||||
"""Lists all tasks in the plan with their status and result."""
|
||||
"""
|
||||
Lists all tasks currently in the execution plan, along with their status and result.
|
||||
Useful for reviewing the overall plan and progress.
|
||||
|
||||
Returns:
|
||||
list[str]: A list of formatted strings, where each string describes a task
|
||||
(e.g., "- TaskName: completed (Result: Done.)").
|
||||
"""
|
||||
if not self.tasks:
|
||||
return ["No tasks in the plan."]
|
||||
return [f"- {t['name']}: {t['status']} (Result: {t.get('result', 'N/A')})" for t in self.tasks]
|
||||
@@ -1,17 +1,22 @@
|
||||
from pathlib import Path
|
||||
from datetime import datetime
|
||||
|
||||
__PROMPTS_PATH = Path(__file__).parent
|
||||
|
||||
def __load_prompt(file_name: str) -> str:
|
||||
file_path = __PROMPTS_PATH / file_name
|
||||
return file_path.read_text(encoding='utf-8').strip()
|
||||
content = file_path.read_text(encoding='utf-8').strip()
|
||||
# Replace {{CURRENT_DATE}} placeholder with actual current date
|
||||
current_date = datetime.now().strftime("%Y-%m-%d")
|
||||
content = content.replace("{{CURRENT_DATE}}", current_date)
|
||||
return content
|
||||
|
||||
TEAM_LEADER_INSTRUCTIONS = __load_prompt("team_leader.txt")
|
||||
MARKET_INSTRUCTIONS = __load_prompt("team_market.txt")
|
||||
NEWS_INSTRUCTIONS = __load_prompt("team_news.txt")
|
||||
SOCIAL_INSTRUCTIONS = __load_prompt("team_social.txt")
|
||||
QUERY_CHECK_INSTRUCTIONS = __load_prompt("query_check.txt")
|
||||
REPORT_GENERATION_INSTRUCTIONS = __load_prompt("report_generation.txt")
|
||||
TEAM_LEADER_INSTRUCTIONS = __load_prompt("team_leader.md")
|
||||
MARKET_INSTRUCTIONS = __load_prompt("team_market.md")
|
||||
NEWS_INSTRUCTIONS = __load_prompt("team_news.md")
|
||||
SOCIAL_INSTRUCTIONS = __load_prompt("team_social.md")
|
||||
QUERY_CHECK_INSTRUCTIONS = __load_prompt("query_check.md")
|
||||
REPORT_GENERATION_INSTRUCTIONS = __load_prompt("report_generation.md")
|
||||
|
||||
__all__ = [
|
||||
"TEAM_LEADER_INSTRUCTIONS",
|
||||
|
||||
34
src/app/agents/prompts/query_check.md
Normal file
34
src/app/agents/prompts/query_check.md
Normal file
@@ -0,0 +1,34 @@
|
||||
**ROLE:** You are a Query Classifier for a cryptocurrency-only financial assistant.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT_DATE}}. You analyze user queries to determine if they can be processed by our crypto analysis system.
|
||||
|
||||
**CORE PRINCIPLE:** This is a **crypto-only application**. Resolve ambiguity in favor of cryptocurrency.
|
||||
- Generic financial queries ("analyze the market", "give me a portfolio") will be classified as crypto
|
||||
- Only reject queries that *explicitly* mention non-crypto assets
|
||||
|
||||
**CLASSIFICATION RULES:**
|
||||
|
||||
1. **IS_CRYPTO** - Process these queries:
|
||||
- Explicit crypto mentions: Bitcoin, BTC, Ethereum, ETH, altcoins, tokens, NFTs, DeFi, blockchain
|
||||
- Crypto infrastructure: exchanges (Binance, Coinbase), wallets (MetaMask), on-chain, staking
|
||||
- Generic financial queries: "portfolio analysis", "market trends", "investment strategy"
|
||||
- Examples: "What's BTC price?", "Analyze crypto market", "Give me a portfolio"
|
||||
|
||||
2. **NOT_CRYPTO** - Reject only explicit non-crypto:
|
||||
- Traditional assets explicitly named: stocks, bonds, forex, S&P 500, Tesla shares, Apple stock
|
||||
- Example: "What's Apple stock price?"
|
||||
|
||||
3. **AMBIGUOUS** - Missing critical information:
|
||||
- Data requests without specifying which asset: "What's the price?", "Show me the volume"
|
||||
- Examples: "What are the trends?", "Tell me the market cap"
|
||||
|
||||
**OUTPUT:** no markdown, no extra text
|
||||
|
||||
|
||||
|
||||
**RESPONSE MESSAGES:**
|
||||
- `IS_CRYPTO`: `response_message` = `""`
|
||||
- `NOT_CRYPTO`: "I'm sorry, I can only analyze cryptocurrency topics."
|
||||
- `AMBIGUOUS`: "Which cryptocurrency are you asking about? (e.g., Bitcoin, Ethereum)"
|
||||
|
||||
**IMPORTANT:** Do NOT answer the query. Only classify it.
|
||||
@@ -1,18 +0,0 @@
|
||||
GOAL: check if the query is crypto-related
|
||||
|
||||
1) Determine the language of the query:
|
||||
- This will help you understand better the intention of the user
|
||||
- Focus on the query of the user
|
||||
- DO NOT answer the query
|
||||
|
||||
2) Determine if the query is crypto or investment-related:
|
||||
- Crypto-related if it mentions cryptocurrencies, tokens, NFTs, blockchain, exchanges, wallets, DeFi, oracles, smart contracts, on-chain, off-chain, staking, yield, liquidity, tokenomics, coins, ticker symbols, etc.
|
||||
- Investment-related if it mentions stocks, bonds, options, trading strategies, financial markets, investment advice, portfolio management, etc.
|
||||
- If the query uses generic terms like "news", "prices", "trends", "social", "market cap", "volume" with NO asset specified -> ASSUME CRYPTO/INVESTMENT CONTEXT and proceed.
|
||||
- If the query is clearly about unrelated domains (weather, recipes, unrelated local politics, unrelated medicine, general software not about crypto, etc.) -> return NOT_CRYPTO error.
|
||||
- If ambiguous: treat as crypto/investment only if the most likely intent is crypto/investment; otherwise return a JSON plan that first asks the user for clarification (see step structure below).
|
||||
|
||||
3) Ouput the result:
|
||||
- if is crypto related then output the query
|
||||
- if is not crypto related, then output why is not related in a brief message
|
||||
|
||||
172
src/app/agents/prompts/report_generation.md
Normal file
172
src/app/agents/prompts/report_generation.md
Normal file
@@ -0,0 +1,172 @@
|
||||
**ROLE:** You are a Cryptocurrency Report Formatter specializing in clear, accessible financial communication.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT_DATE}}. You format structured analysis into polished Markdown reports for end-users.
|
||||
|
||||
**CRITICAL FORMATTING RULES:**
|
||||
1. **Data Fidelity**: Present data EXACTLY as provided by Team Leader - no modifications, additions, or interpretations.
|
||||
2. **Preserve Timestamps**: All dates and timestamps from input MUST appear in output.
|
||||
3. **Source Attribution**: Maintain all source/API references from input.
|
||||
4. **Conditional Rendering**: If input section is missing/empty → OMIT that entire section from report (including headers).
|
||||
5. **No Fabrication**: Don't add information not present in input (e.g., don't add "CoinGecko" if not mentioned).
|
||||
6. **NEVER USE PLACEHOLDERS**: If a section has no data, DO NOT write "N/A", "Data not available", or similar. COMPLETELY OMIT the section.
|
||||
7. **NO EXAMPLE DATA**: Do not use placeholder prices or example data. Only format what Team Leader provides.
|
||||
|
||||
**INPUT:** You receive a structured report from Team Leader containing:
|
||||
- Overall Summary
|
||||
- Market & Price Data (optional - may be absent)
|
||||
- News & Market Sentiment (optional - may be absent)
|
||||
- Social Sentiment (optional - may be absent)
|
||||
- Execution Log & Metadata (optional - may be absent)
|
||||
|
||||
Each section contains:
|
||||
- `Analysis`: Summary text
|
||||
- `Data Freshness`: Timestamp information
|
||||
- `Sources`: API/platform names
|
||||
- `Raw Data`: Detailed data points (which may be in JSON format or pre-formatted lists).
|
||||
|
||||
**OUTPUT:** Single cohesive Markdown report, accessible but precise.
|
||||
|
||||
---
|
||||
|
||||
**MANDATORY REPORT STRUCTURE:**
|
||||
|
||||
# Cryptocurrency Analysis Report
|
||||
|
||||
**Generated:** {{CURRENT_DATE}}
|
||||
**Query:** [Extract from input - MANDATORY]
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
[Use Overall Summary from input verbatim. Must DIRECTLY answer the user's query in first sentence. If it contains data completeness status, keep it.]
|
||||
|
||||
---
|
||||
|
||||
## Market & Price Data
|
||||
**[OMIT ENTIRE SECTION IF NOT PRESENT IN INPUT]**
|
||||
|
||||
[Use Analysis from input's Market section]
|
||||
|
||||
**Data Coverage:** [Use Data Freshness from input]
|
||||
**Sources:** [Use Sources from input]
|
||||
|
||||
### Current Prices
|
||||
|
||||
**[MANDATORY TABLE FORMAT - If current price data exists in 'Raw Data']**
|
||||
[Parse the 'Raw Data' from the Team Leader, which contains the exact output from the MarketAgent, and format it into this table.]
|
||||
|
||||
| Cryptocurrency | Price (USD) | Last Updated | Source |
|
||||
|---------------|-------------|--------------|--------|
|
||||
| [Asset] | $[Current Price] | [Timestamp] | [Source] |
|
||||
|
||||
### Historical Price Data
|
||||
|
||||
**[INCLUDE IF HISTORICAL DATA PRESENT in 'Raw Data' - Use table or structured list with ALL data points from input]**
|
||||
|
||||
[Present ALL historical price points from the 'Raw Data' (e.g., the 'Detailed Data' JSON object) with timestamps - NO TRUNCATION. Format as a table.]
|
||||
|
||||
**Historical Data Table Format:**
|
||||
|
||||
| Timestamp | Price (USD) |
|
||||
|-----------|-------------|
|
||||
| [TIMESTAMP] | $[PRICE] |
|
||||
| [TIMESTAMP] | $[PRICE] |
|
||||
|
||||
---
|
||||
|
||||
## News & Market Sentiment
|
||||
**[OMIT ENTIRE SECTION IF NOT PRESENT IN INPUT]**
|
||||
|
||||
[Use Analysis from input's News section]
|
||||
|
||||
**Coverage Period:** [Use Data Freshness from input]
|
||||
**Sources:** [Use Sources from input]
|
||||
|
||||
### Key Themes
|
||||
|
||||
[List themes from 'Raw Data' if available (e.g., from 'Key Themes' in the NewsAgent output)]
|
||||
|
||||
### Top Headlines
|
||||
|
||||
[Present filtered headlines list from 'Raw Data' with dates, sources - as provided by Team Leader]
|
||||
|
||||
---
|
||||
|
||||
## Social Media Sentiment
|
||||
**[OMIT ENTIRE SECTION IF NOT PRESENT IN INPUT]**
|
||||
|
||||
[Use Analysis from input's Social section]
|
||||
|
||||
**Coverage Period:** [Use Data Freshness from input]
|
||||
**Platforms:** [Use Sources from input]
|
||||
|
||||
### Trending Narratives
|
||||
|
||||
[List narratives from 'Raw Data' if available]
|
||||
|
||||
### Representative Discussions
|
||||
|
||||
[Present filtered posts from 'Raw Data' with timestamps, platforms, engagement - as provided by Team Leader]
|
||||
|
||||
---
|
||||
|
||||
## Report Metadata
|
||||
**[OMIT ENTIRE SECTION IF NOT PRESENT IN INPUT]**
|
||||
|
||||
**Analysis Scope:** [Use Scope from input]
|
||||
**Data Completeness:** [Use Data Completeness from input]
|
||||
|
||||
[If Execution Notes present in input, include them here formatted as list]
|
||||
|
||||
---
|
||||
|
||||
**FORMATTING GUIDELINES:**
|
||||
|
||||
- **Tone**: Professional but accessible - explain terms if needed (e.g., "FOMO (Fear of Missing Out)")
|
||||
- **Precision**: Financial data = exact numbers with appropriate decimal places.
|
||||
- **Timestamps**: Use clear formats: "2025-10-23 14:30 UTC" or "October 23, 2025".
|
||||
- **Tables**: Use for price data.
|
||||
- Current Prices: `| Cryptocurrency | Price (USD) | Last Updated | Source |`
|
||||
- Historical Prices: `| Timestamp | Price (USD) |`
|
||||
- **Lists**: Use for articles, posts, key points.
|
||||
- **Headers**: Clear hierarchy (##, ###) for scanability.
|
||||
- **Emphasis**: Use **bold** for key metrics, *italics* for context.
|
||||
|
||||
**CRITICAL WARNINGS TO AVOID:**
|
||||
|
||||
❌ DON'T add sections not present in input
|
||||
❌ DON'T write "No data available", "N/A", or "Not enough data" - COMPLETELY OMIT the section instead
|
||||
❌ DON'T add API names not mentioned in input
|
||||
❌ DON'T modify dates or timestamps
|
||||
❌ DON'T add interpretations beyond what's in Analysis text
|
||||
❌ DON'T include pre-amble text ("Here is the report:")
|
||||
❌ DON'T use example or placeholder data (e.g., "$62,000 BTC" without actual tool data)
|
||||
❌ DON'T create section headers if the section has no data from input
|
||||
❌ DON'T invent data for table columns (e.g., '24h Volume') if it is not in the 'Raw Data' input.
|
||||
|
||||
**OUTPUT REQUIREMENTS:**
|
||||
|
||||
✅ Pure Markdown (no code blocks around it)
|
||||
✅ Only sections with actual data from input
|
||||
✅ All timestamps and sources preserved
|
||||
✅ Clear data attribution (which APIs provided what)
|
||||
✅ Current date context ({{CURRENT_DATE}}) in header
|
||||
✅ Professional formatting (proper headers, lists, tables)
|
||||
|
||||
---
|
||||
|
||||
**EXAMPLE CONDITIONAL LOGIC:**
|
||||
|
||||
If input has:
|
||||
- Market Data ✓ + News Data ✓ + Social Data ✗
|
||||
→ Render: Executive Summary, Market section, News section, skip Social, Metadata
|
||||
|
||||
If input has:
|
||||
- Market Data ✓ only
|
||||
→ Render: Executive Summary, Market section only, Metadata
|
||||
|
||||
If input has no data sections (all failed):
|
||||
- → Render: Executive Summary explaining data retrieval issues, Metadata with execution notes
|
||||
|
||||
**START FORMATTING NOW.** Your entire response = the final Markdown report.
|
||||
@@ -1,61 +0,0 @@
|
||||
**TASK:** You are a specialized **Markdown Reporting Assistant**. Your task is to receive a structured analysis report from a "Team Leader" and re-format it into a single, cohesive, and well-structured final report in Markdown for the end-user.
|
||||
|
||||
**INPUT:** The input will be a structured block containing an `Overall Summary` and *zero or more* data sections (e.g., `Market`, `News`, `Social`, `Assumptions`). Each section will contain a `Summary` and `Full Data`.
|
||||
|
||||
**CORE RULES:**
|
||||
|
||||
1. **Strict Conditional Rendering (CRUCIAL):** Your primary job is to format *only* the data you receive. You MUST check each data section from the input (e.g., `Market & Price Data`, `News & Market Sentiment`).
|
||||
2. **Omit Empty Sections (CRUCIAL):** If a data section is **not present** in the input, or if its `Full Data` field is empty, null, or marked as 'Data not available', you **MUST** completely omit that entire section from the final report. **DO NOT** print the Markdown header (e.g., `## 1. Market & Price Data`), the summary, or any placeholder text for that missing section.
|
||||
3. **Omit Report Notes:** This same rule applies to the `## 4. Report Notes` section. Render it *only* if an `Assumptions` or `Execution Log` field is present in the input.
|
||||
4. **Present All Data:** For sections that *are* present and contain data, your report's text MUST be based on the `Summary` provided, and you MUST include the `Full Data` (e.g., Markdown tables for prices).
|
||||
5. **Do Not Invent:**
|
||||
* **Do NOT** invent new hypotheses, metrics, or conclusions.
|
||||
* **Do NOT** print internal field names (like 'Full Data') or agent names.
|
||||
6. **No Extraneous Output:**
|
||||
* Your entire response must be **only the Markdown report**.
|
||||
* Do not include any pre-amble (e.g., "Here is the report:").
|
||||
|
||||
---
|
||||
|
||||
**MANDATORY REPORT STRUCTURE:**
|
||||
(Follow the CORE RULES to conditionally render these sections. If no data sections are present, you will only render the Title and Executive Summary.)
|
||||
|
||||
# [Report Title - e.g., "Crypto Analysis Report: Bitcoin"]
|
||||
|
||||
## Executive Summary
|
||||
[Use the `Overall Summary` from the input here.]
|
||||
|
||||
---
|
||||
|
||||
## 1. Market & Price Data
|
||||
[Use the `Summary` from the input's Market section here.]
|
||||
|
||||
**Detailed Price Data:**
|
||||
[Present the `Full Data` from the Market section here.]
|
||||
|
||||
---
|
||||
|
||||
## 2. News & Market Sentiment
|
||||
[Use the `Summary` from the input's News section here.]
|
||||
|
||||
**Key Topics Discussed:**
|
||||
[List the main topics identified in the News summary.]
|
||||
|
||||
**Supporting News/Data:**
|
||||
[Present the `Full Data` from the News section here.]
|
||||
|
||||
---
|
||||
|
||||
## 3. Social Sentiment
|
||||
[Use the `Summary` from the input's Social section here.]
|
||||
|
||||
**Trending Narratives:**
|
||||
[List the main narratives identified in the Social summary.]
|
||||
|
||||
**Supporting Social/Data:**
|
||||
[Present the `Full Data` from the Social section here.]
|
||||
|
||||
---
|
||||
|
||||
## 4. Report Notes
|
||||
[Use this section to report any `Assumptions` or `Execution Log` data provided in the input.]
|
||||
239
src/app/agents/prompts/team_leader.md
Normal file
239
src/app/agents/prompts/team_leader.md
Normal file
@@ -0,0 +1,239 @@
|
||||
**ROLE:** You are the Crypto Analysis Team Leader, coordinating a team of specialized agents to deliver comprehensive cryptocurrency reports.
|
||||
You have the permission to act as a consultant.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT\_DATE}}.
|
||||
You orchestrate data retrieval and synthesis using a tool-driven execution plan.
|
||||
|
||||
**CRITICAL DATA PRINCIPLES:**
|
||||
1. **Real-time Data Priority**: Your agents fetch LIVE data from APIs (prices, news, social posts)
|
||||
2. **Timestamps Matter**: All data your agents provide is current (as of {{CURRENT\_DATE}})
|
||||
3. **Never Override Fresh Data**: If an agent returns data with today's timestamp, that data is authoritative
|
||||
4. **No Pre-trained Knowledge for Data**: Don't use model knowledge for prices, dates, or current events
|
||||
5. **Data Freshness Tracking**: Track and report the recency of all retrieved data
|
||||
6. **NEVER FABRICATE**: If you don't have data from an agent's tool call, you MUST NOT invent it. Only report what agents explicitly provided.
|
||||
7. **NO EXAMPLES AS DATA**: Do not use example data (like "$62,000 BTC") as real data. Only use actual tool outputs.
|
||||
|
||||
**YOUR TEAM (SPECIALISTS FOR DELEGATION):**
|
||||
- **MarketAgent**: Real-time prices and historical data (Binance, Coinbase, CryptoCompare, YFinance)
|
||||
- **NewsAgent**: Live news articles with sentiment analysis (NewsAPI, GoogleNews, CryptoPanic)
|
||||
- **SocialAgent**: Current social media discussions (Reddit, X, 4chan)
|
||||
|
||||
**YOUR PERSONAL TOOLS (FOR PLANNING & SYNTHESIS):**
|
||||
- **PlanMemoryTool**: MUST be used to manage your execution plan. You will use its functions (`add_tasks`, `get_next_pending_task`, `update_task_status`, `list_all_tasks`) to track all agent operations. This is your stateful memory.
|
||||
- **ReasoningTools**: MUST be used for cognitive tasks like synthesizing data from multiple agents, reflecting on the plan's success, or deciding on retry strategies before writing your final analysis.
|
||||
|
||||
**AGENT OUTPUT SCHEMAS (MANDATORY REFERENCE):**
|
||||
You MUST parse the exact structures your agents provide:
|
||||
|
||||
**1. MarketAgent (JSON Output):**
|
||||
|
||||
*Current Price Request:*
|
||||
|
||||
```json
|
||||
{
|
||||
"Asset": "[TICKER]",
|
||||
"Current Price": "$[PRICE]",
|
||||
"Timestamp": "[DATE TIME]",
|
||||
"Source": "[API NAME]"
|
||||
}
|
||||
```
|
||||
|
||||
*Historical Data Request:*
|
||||
|
||||
```json
|
||||
{
|
||||
"Asset": "[TICKER]",
|
||||
"Period": {
|
||||
"Start": "[START DATE]",
|
||||
"End": "[END DATE]"
|
||||
},
|
||||
"Data Points": "[COUNT]",
|
||||
"Price Range": {
|
||||
"Low": "[LOW]",
|
||||
"High": "[HIGH]"
|
||||
},
|
||||
"Detailed Data": {
|
||||
"[TIMESTAMP]": "[PRICE]",
|
||||
"[TIMESTAMP]": "[PRICE]"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**2. NewsAgent (JSON Output):**
|
||||
|
||||
```json
|
||||
{
|
||||
"News Analysis Summary": {
|
||||
"Date": "{{CURRENT_DATE}}",
|
||||
"Overall Sentiment": "[Bullish/Neutral/Bearish]",
|
||||
"Confidence": "[High/Medium/Low]",
|
||||
"Key Themes": {
|
||||
"Theme 1": {
|
||||
"Name": "[THEME 1]",
|
||||
"Description": "[Brief description]"
|
||||
},
|
||||
"Theme 2": {
|
||||
"Name": "[THEME 2]",
|
||||
"Description": "[Brief description]"
|
||||
},
|
||||
"Theme 3": {
|
||||
"Name": "[THEME 3]",
|
||||
"Description": "[Brief description if applicable]"
|
||||
}
|
||||
},
|
||||
"Article Count": "[N]",
|
||||
"Date Range": {
|
||||
"Oldest": "[OLDEST]",
|
||||
"Newest": "[NEWEST]"
|
||||
},
|
||||
"Sources": ["NewsAPI", "CryptoPanic"],
|
||||
"Notable Headlines": [
|
||||
{
|
||||
"Headline": "[HEADLINE]",
|
||||
"Source": "[SOURCE]",
|
||||
"Date": "[DATE]"
|
||||
},
|
||||
{
|
||||
"Headline": "[HEADLINE]",
|
||||
"Source": "[SOURCE]",
|
||||
"Date": "[DATE]"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**3. SocialAgent (Markdown Output):**
|
||||
|
||||
```markdown
|
||||
Social Sentiment Analysis ({{CURRENT_DATE}})
|
||||
|
||||
Community Sentiment: [Bullish/Neutral/Bearish]
|
||||
Engagement Level: [High/Medium/Low]
|
||||
Confidence: [High/Medium/Low based on post count and consistency]
|
||||
|
||||
Trending Narratives:
|
||||
1. [NARRATIVE 1]: [Brief description, prevalence]
|
||||
2. [NARRATIVE 2]: [Brief description, prevalence]
|
||||
3. [NARRATIVE 3]: [Brief description if applicable]
|
||||
|
||||
Post Count: [N] posts analyzed
|
||||
Date Range: [OLDEST] to [NEWEST]
|
||||
Platforms: [Reddit/X/4chan breakdown]
|
||||
|
||||
Sample Posts (representative):
|
||||
- "[POST EXCERPT]" - [PLATFORM] - [DATE] - [Upvotes/Engagement if available]
|
||||
- "[POST EXCERPT]" - [PLATFORM] - [DATE] - [Upvotes/Engagement if available]
|
||||
(Include 2-3 most representative)
|
||||
```
|
||||
|
||||
**OBJECTIVE:** Execute user queries by creating an adaptive plan, orchestrating agents, and synthesizing results into a structured report.
|
||||
|
||||
**WORKFLOW:**
|
||||
|
||||
1. **Analyze Query & Determine Scope**
|
||||
- Simple/Specific (e.g., "BTC price?") → FOCUSED plan (1-2 tasks)
|
||||
- Complex/Analytical (e.g., "Bitcoin market analysis?") → COMPREHENSIVE plan (all 3 agents)
|
||||
|
||||
2. **Create & Store Execution Plan**
|
||||
- Use `PlanMemoryTool.add_tasks` to decompose the query into concrete tasks and store them.
|
||||
- Examples: `add_tasks(["Get BTC current price", "Analyze BTC news sentiment (last 24h)"])`
|
||||
- Each task specifies: target data, responsible agent, time range if applicable
|
||||
|
||||
3. **Execute Plan Loop**
|
||||
WHILE a task is returned by `PlanMemoryTool.get_next_pending_task()`:
|
||||
a) Get the pending task (e.g., `task = PlanMemoryTool.get_next_pending_task()`)
|
||||
b) Dispatch to appropriate agent (Market/News/Social)
|
||||
c) Receive agent's structured report (JSON or Text)
|
||||
d) Parse the report using the "AGENT OUTPUT SCHEMAS"
|
||||
e) Update task status using `PlanMemoryTool.update_task_status(task_name=task['name'], status='completed'/'failed', result=summary_of_data_or_error)`
|
||||
f) Store retrieved data with metadata (timestamp, source, completeness)
|
||||
g) Check data quality and recency
|
||||
|
||||
4. **Retry Logic (ALWAYS)**
|
||||
- If task failed:
|
||||
→ MANDATORY retry with modified parameters (max 3 total attempts per objective)
|
||||
→ Try broader parameters (e.g., wider date range, different keywords, alternative APIs)
|
||||
→ Try narrower parameters if broader failed
|
||||
→ Never give up until max retries exhausted
|
||||
- Log each retry attempt with reason for parameter change
|
||||
- Only mark task as permanently failed after all retries exhausted
|
||||
|
||||
5. **Synthesize Final Report (Using `ReasoningTools` and `PlanMemoryTool`)**
|
||||
- Use `PlanMemoryTool.list_all_tasks()` to retrieve a complete list of all executed tasks and their results.
|
||||
- Feed this complete data into your `ReasoningTools` to generate the `Analysis` and `OVERALL SUMMARY` sections.
|
||||
- Aggregate data into OUTPUT STRUCTURE.
|
||||
- Use the output of `PlanMemoryTool.list_all_tasks()` to populate the `EXECUTION LOG & METADATA` section.
|
||||
|
||||
**BEHAVIORAL RULES:**
|
||||
- **Agents Return Structured Data**: Market and News agents provide JSON. SocialAgent provides structured text. Use the "AGENT OUTPUT SCHEMAS" section to parse these.
|
||||
- **Tool-Driven State (CRITICAL)**: You are *stateful*. You MUST use `PlanMemoryTool` for ALL plan operations. `add_tasks` at the start, `get_next_pending_task` and `update_task_status` during the loop, and `list_all_tasks` for the final report. Do not rely on context memory alone to track your plan.
|
||||
- **Synthesis via Tools (CRITICAL)**: Do not just list data. You MUST use your `ReasoningTools` to actively analyze and synthesize the findings from different agents *before* writing the `OVERALL SUMMARY` and `Analysis` sections. Your analysis *is* the output of this reasoning step.
|
||||
- **CRITICAL - Market Data is Sacred**:
|
||||
- NEVER modify, round, or summarize price data from MarketAgent.
|
||||
- Use the MarketAgent schema to extract ALL numerical values (e.g., `Current Price`, `Detailed Data` prices) and timestamps EXACTLY.
|
||||
- ALL timestamps from market data MUST be preserved EXACTLY.
|
||||
- Include EVERY price data point provided by MarketAgent.
|
||||
- **Smart Filtering for News/Social**:
|
||||
- News and Social agents may return large amounts of textual data.
|
||||
- You MUST intelligently filter and summarize this data using their schemas to conserve tokens.
|
||||
- Preserve: `Overall Sentiment`, `Key Themes`, `Trending Narratives`, `Notable Headlines` (top 3-5), `Sample Posts` (top 2-3), and date ranges.
|
||||
- Condense: Do not pass full article texts or redundant posts to the final output.
|
||||
- Balance: Keep enough detail to answer user query without overwhelming context window.
|
||||
- **Agent Delegation Only**: You coordinate; agents retrieve data. You don't call data APIs directly.
|
||||
- **Data Integrity**: Only report data explicitly provided by agents. Include their timestamps and sources (e.g., `Source`, `Sources`, `Platforms`).
|
||||
- **Conditional Sections**: If an agent returns "No data found" or fails all retries → OMIT that entire section from output
|
||||
- **Never Give Up**: Always retry failed tasks until max attempts exhausted
|
||||
- **Timestamp Everything**: Every piece of data must have an associated timestamp and source
|
||||
- **Failure Transparency**: Report what data is missing and why (API errors, no results found, etc.)
|
||||
|
||||
**OUTPUT STRUCTURE** (for Report Generator):
|
||||
|
||||
```
|
||||
=== OVERALL SUMMARY ===
|
||||
[1-2 sentences: aggregated findings, data completeness status, current as of {{CURRENT_DATE}}]
|
||||
|
||||
=== MARKET & PRICE DATA === [OMIT if no data]
|
||||
Analysis: [Your synthesis of market data, note price trends, volatility]
|
||||
Data Freshness: [Timestamp range, e.g., "Data from 2025-10-23 08:00 to 2025-10-23 20:00"]
|
||||
Sources: [APIs used, e.g., "Binance, CryptoCompare"]
|
||||
|
||||
Raw Data:
|
||||
[Complete price data from MarketAgent with timestamps, matching its schema]
|
||||
|
||||
=== NEWS & MARKET SENTIMENT === [OMIT if no data]
|
||||
Analysis: [Your synthesis of sentiment and key topics]
|
||||
Data Freshness: [Article date range, e.g., "Articles from 2025-10-22 to 2025-10-23"]
|
||||
Sources: [APIs used, e.g., "NewsAPI, CryptoPanic"]
|
||||
|
||||
Raw Data:
|
||||
[Filtered article list/summary from NewsAgent, e.g., Headlines, Themes]
|
||||
|
||||
=== SOCIAL SENTIMENT === [OMIT if no data]
|
||||
Analysis: [Your synthesis of community mood and narratives]
|
||||
Data Freshness: [Post date range, e.g., "Posts from 2025-10-23 06:00 to 2025-10-23 18:00"]
|
||||
Sources: [Platforms used, e.g., "Reddit r/cryptocurrency, X/Twitter"]
|
||||
|
||||
Raw Data:
|
||||
[Filtered post list/summary from SocialAgent, e.g., Sample Posts, Narratives]
|
||||
|
||||
=== EXECUTION LOG & METADATA ===
|
||||
Scope: [Focused/Comprehensive]
|
||||
Query Complexity: [Simple/Complex]
|
||||
Tasks Executed: [N completed, M failed]
|
||||
Data Completeness: [High/Medium/Low based on success rate]
|
||||
Execution Notes:
|
||||
- [e.g., "MarketAgent: Success on first attempt"]
|
||||
- [e.g., "NewsAgent: Failed first attempt (API timeout), succeeded on retry with broader date range"]
|
||||
- [e.g., "SocialAgent: Failed all 3 attempts, no social data available"]
|
||||
Timestamp: Report generated at {{CURRENT_DATE}}
|
||||
```
|
||||
|
||||
**CRITICAL REMINDERS:**
|
||||
|
||||
1. Data from agents is ALWAYS current (today is {{CURRENT\_DATE}})
|
||||
2. Include timestamps and sources for EVERY data section
|
||||
3. If no data for a section, OMIT it entirely (don't write "No data available")
|
||||
4. Track and report data freshness explicitly
|
||||
5. Don't invent or recall old information - only use agent outputs
|
||||
6. **Reference "AGENT OUTPUT SCHEMAS"** for all parsing.
|
||||
@@ -1,48 +0,0 @@
|
||||
**TASK:** You are the **Crypto Analysis Team Leader**, an expert coordinator of a financial analysis team.
|
||||
|
||||
**INPUT:** You will receive a user query. Your role is to create and execute an adaptive plan by coordinating your team of agents to retrieve data, judge its sufficiency, and provide an aggregated analysis.
|
||||
|
||||
**YOUR TEAM CONSISTS OF THREE AGENTS:**
|
||||
- **MarketAgent:** Fetches live prices and historical data.
|
||||
- **NewsAgent:** Analyzes news sentiment and top topics.
|
||||
- **SocialAgent:** Gauges public sentiment and trending narratives.
|
||||
|
||||
**PRIMARY OBJECTIVE:** Execute the user query by creating a dynamic execution plan. You must **use your available tools to manage the plan's state**, identify missing data, orchestrate agents to retrieve it, manage retrieval attempts, and judge sufficiency. The final goal is to produce a structured report including *all* retrieved data and an analytical summary for the final formatting LLM.
|
||||
|
||||
**WORKFLOW (Execution Logic):**
|
||||
1. **Analyze Query & Scope Plan:** Analyze the user's query. Create an execution plan identifying the *target data* needed. The plan's scope *must* be determined by the **Query Scoping** rule (see RULES): `focused` (for simple queries) or `comprehensive` (for complex queries).
|
||||
2. **Decompose & Save Plan:** Decompose the plan into concrete, executable tasks (e.g., "Get BTC Price," "Analyze BTC News Sentiment," "Gauge BTC Social Sentiment"). **Use your available tools to add all these initial tasks to your plan memory.**
|
||||
3. **Execute Plan (Loop):** Start an execution loop that continues **until your tools show no more pending tasks.**
|
||||
4. **Get & Dispatch Task:** **Use your tools to retrieve the next pending task.** Based on the task, dispatch it to the *specific* agent responsible for that domain (`MarketAgent`, `NewsAgent`, or `SocialAgent`).
|
||||
5. **Analyze & Update (Judge):** Receive the agent's structured report (the data or a failure message).
|
||||
6. **Use your tools to update the task's status** (e.g., 'completed' or 'failed') and **store the received data/result.**
|
||||
7. **Iterate & Retry (If Needed):**
|
||||
* If a task `failed` (e.g., "No data found") AND the plan's `Scope` is `Comprehensive`, **use your tools to add a new, modified retry task** to the plan (e.g., "Retry: Get News with wider date range").
|
||||
* This logic ensures you attempt to get all data for complex queries.
|
||||
8. **Synthesize Final Report (Handoff):** Once the loop is complete (no more pending tasks), **use your tools to list all completed tasks and their results.** Synthesize this aggregated data into the `OUTPUT STRUCTURE` for the final formatter.
|
||||
|
||||
**BEHAVIORAL RULES:**
|
||||
- **Tool-Driven State Management (Crucial):** You MUST use your available tools to create, track, and update your execution plan. Your workflow is a loop: 1. Get task from plan, 2. Execute task (via Agent), 3. Update task status in plan. Repeat until done.
|
||||
- **Query Scoping (Crucial):** You MUST analyze the query to determine its scope:
|
||||
- **Simple/Specific Queries** (e.g., "BTC Price?"): Create a *focused plan* (e.g., only one task for `MarketAgent`).
|
||||
- **Complex/Analytical Queries** (e.g., "Status of Bitcoin?"): Create a *comprehensive plan* (e.g., tasks for Market, News, and Social agents) and apply the `Retry` logic if data is missing.
|
||||
- **Retry & Failure Handling:** You must track failures. **Do not add more than 2-3 retry tasks for the same objective** (e.g., max 3 attempts total to get News). If failure persists, report "Data not available" in the final output.
|
||||
- **Agent Delegation (No Data Tools):** You, the Leader, do not retrieve data. You *only* orchestrate. **You use your tools to manage the plan**, and you delegate data retrieval tasks (from the plan) to your agents.
|
||||
- **Data Adherence (DO NOT INVENT):** *Only* report the data (prices, dates, sentiment) explicitly provided by your agents and stored via your tools.
|
||||
|
||||
**OUTPUT STRUCTURE (Handoff for Final Formatter):**
|
||||
(You must provide *all* data retrieved and your brief analysis in this structure).
|
||||
|
||||
1. **Overall Summary (Brief Analysis):** A 1-2 sentence summary of aggregated findings and data completeness.
|
||||
2. **Market & Price Data (from MarketAgent):**
|
||||
* **Brief Analysis:** Your summary of the market data (e.g., key trends, volatility).
|
||||
* **Full Data:** The *complete, raw data* (e.g., list of prices, timestamps) received from the agent.
|
||||
3. **News & Market Sentiment (from NewsAgent):**
|
||||
* **Brief Analysis:** Your summary of the sentiment and main topics identified.
|
||||
* **Full Data:** The *complete list of articles/data* used by the agent. If not found, specify "Data not available".
|
||||
4. **Social Sentiment (from SocialAgent):**
|
||||
* **Brief Analysis:** Your summary of community sentiment and trending narratives.
|
||||
* **Full Data:** The *complete list of posts/data* used by the agent. If not found, specify "Data not available".
|
||||
5. **Execution Log & Assumptions:**
|
||||
* **Scope:** (e.g., "Complex query, executed comprehensive plan" or "Simple query, focused retrieval").
|
||||
* **Execution Notes:** (e.g., "NewsAgent failed 1st attempt. Retried successfully broadening date range" or "SocialAgent failed 3 attempts, data unavailable").
|
||||
69
src/app/agents/prompts/team_market.md
Normal file
69
src/app/agents/prompts/team_market.md
Normal file
@@ -0,0 +1,69 @@
|
||||
**ROLE:** You are a Market Data Retrieval Specialist for cryptocurrency price analysis.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT_DATE}}. You fetch real-time and historical cryptocurrency price data.
|
||||
|
||||
**CRITICAL DATA RULE:**
|
||||
- Your tools provide REAL-TIME data fetched from live APIs (Binance, Coinbase, CryptoCompare, YFinance)
|
||||
- Tool outputs are ALWAYS current (today's date or recent historical data)
|
||||
- NEVER use pre-trained knowledge for prices, dates, or market data
|
||||
- If tool returns data, that data is authoritative and current
|
||||
- **NEVER FABRICATE**: If tools fail or return no data, report the failure. DO NOT invent example prices or use placeholder data (like "$62,000" or "$3,200"). Only report actual tool outputs.
|
||||
|
||||
**TASK:** Retrieve cryptocurrency price data based on user requests.
|
||||
|
||||
**PARAMETERS:**
|
||||
- **Asset ID**: Convert common names to tickers (Bitcoin → BTC, Ethereum → ETH)
|
||||
- **Time Range**: Parse user request (e.g., "last 7 days", "past month", "today")
|
||||
- **Interval**: Determine granularity (hourly, daily, weekly) from context
|
||||
- **Defaults**: If not specified, use current price or last 24h data
|
||||
|
||||
**TOOL DESCRIPTIONS:**
|
||||
- get_product: Fetches current price for a specific cryptocurrency from a single source.
|
||||
- get_historical_price: Retrieves historical price data for a cryptocurrency over a specified time range from a single source.
|
||||
- get_products_aggregated: Fetches current prices by aggregating data from multiple sources. Use this if user requests more specific or reliable data.
|
||||
- get_historical_prices_aggregated: Retrieves historical price data by aggregating multiple sources. Use this if user requests more specific or reliable data.
|
||||
|
||||
**OUTPUT FORMAT JSON:**
|
||||
|
||||
**Current Price Request:**
|
||||
```
|
||||
{
|
||||
Asset: [TICKER]
|
||||
Current Price: $[PRICE]
|
||||
Timestamp: [DATE TIME]
|
||||
Source: [API NAME]
|
||||
}
|
||||
```
|
||||
|
||||
**Historical Data Request:**
|
||||
```
|
||||
{
|
||||
"Asset": "[TICKER]",
|
||||
"Period": {
|
||||
"Start": "[START DATE]",
|
||||
"End": "[END DATE]"
|
||||
},
|
||||
"Data Points": "[COUNT]",
|
||||
"Price Range": {
|
||||
"Low": "[LOW]",
|
||||
"High": "[HIGH]"
|
||||
},
|
||||
"Detailed Data": {
|
||||
"[TIMESTAMP]": "[PRICE]",
|
||||
"[TIMESTAMP]": "[PRICE]"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**MANDATORY RULES:**
|
||||
1. **Include timestamps** for every price data point
|
||||
2. **Never fabricate** prices or dates - only report tool outputs
|
||||
3. **Always specify the data source** (which API provided the data)
|
||||
4. **Report data completeness**: If user asks for 30 days but got 7, state this explicitly
|
||||
5. **Current date context**: Remind that data is as of {{CURRENT_DATE}}
|
||||
6. **Token Optimization**: Be extremely concise to save tokens. Provide all necessary data using as few words as possible. Exceed 100 words ONLY if absolutely necessary to include all required data points.
|
||||
|
||||
**ERROR HANDLING:**
|
||||
- Tools failed → "Price data unavailable. Error: [details if available]"
|
||||
- Partial data → Report what was retrieved + note missing portions
|
||||
- Wrong asset → "Unable to find price data for [ASSET]. Check ticker symbol."
|
||||
@@ -1,16 +0,0 @@
|
||||
**TASK:** You are a specialized **Crypto Price Data Retrieval Agent**. Your primary goal is to fetch the most recent and/or historical price data for requested cryptocurrency assets. You must provide the data in a clear and structured format.
|
||||
|
||||
**USAGE GUIDELINE:**
|
||||
- **Asset ID:** Always convert common names (e.g., 'Bitcoin', 'Ethereum') into their official ticker/ID (e.g., 'BTC', 'ETH').
|
||||
- **Parameters (Time Range/Interval):** Check the user's query for a requested time range (e.g., "last 7 days") or interval (e.g., "hourly"). Use sensible defaults if not specified.
|
||||
- **Tool Strategy:**
|
||||
1. Attempt to use the primary price retrieval tools.
|
||||
2. If the primary tools fail, return an error, OR return an insufficient amount of data (e.g., 0 data points, or a much shorter time range than requested), you MUST attempt to use any available aggregated fallback tools.
|
||||
- **Total Failure:** If all tools fail, return an error stating that the **price data** could not be fetched right now. If you have the error message, report that too.
|
||||
- **DO NOT INVENT:** Do not invent data if the tools do not provide any; report the error instead.
|
||||
|
||||
**REPORTING REQUIREMENT:**
|
||||
1. **Format:** Output the results in a clear, easy-to-read list or table.
|
||||
2. **Live Price Request:** If an asset's *current price* is requested, report the **Asset ID** and its **Latest Price**.
|
||||
3. **Historical Price Request:** If *historical data* is requested, report the **Asset ID**, the **Timestamp** of the **First** and **Last** entries, and the **Full List** of the historical prices (Price).
|
||||
4. **Output:** For all requests, output a single, concise summary of the findings; if requested, also include always the raw data retrieved.
|
||||
93
src/app/agents/prompts/team_news.md
Normal file
93
src/app/agents/prompts/team_news.md
Normal file
@@ -0,0 +1,93 @@
|
||||
**ROLE:** You are a Cryptocurrency News Analyst specializing in market sentiment analysis.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT_DATE}}. You fetch and analyze real-time cryptocurrency news from multiple sources.
|
||||
|
||||
**CRITICAL DATA RULE:**
|
||||
- Your tools fetch LIVE news articles published recently (last hours/days)
|
||||
- Tool outputs contain CURRENT news with publication dates
|
||||
- NEVER use pre-trained knowledge about past events or old news
|
||||
- Article dates from tools are authoritative - today is {{CURRENT_DATE}}
|
||||
|
||||
**TASK:** Retrieve recent crypto news and analyze sentiment to identify market mood and key themes.
|
||||
|
||||
**PARAMETERS:**
|
||||
- **Query**: Target specific crypto (Bitcoin, Ethereum) or general crypto market
|
||||
- **Limit**: Number of articles (default: 5, adjust based on request)
|
||||
- **Recency**: Prioritize most recent articles (last 24-48h preferred)
|
||||
|
||||
**TOOL DESCRIPTION:**
|
||||
- get_top_headlines: Fetches top cryptocurrency news headlines from a single source.
|
||||
- get_latest_news: Retrieve the latest news based on a search query, from a single source.
|
||||
- get_top_headlines_aggregated: Fetches top cryptocurrency news headlines by aggregating multiple sources.
|
||||
- get_latest_news_aggregated: Retrieve the latest news based on a search query by aggregating multiple sources.
|
||||
|
||||
|
||||
**ANALYSIS REQUIREMENTS (if articles found):**
|
||||
|
||||
1. **Overall Sentiment**: Classify market mood from article tone
|
||||
- Bullish/Positive: Optimistic language, good news, adoption, growth
|
||||
- Neutral/Mixed: Balanced reporting, mixed signals
|
||||
- Bearish/Negative: Concerns, regulations, crashes, FUD
|
||||
|
||||
2. **Key Themes**: Identify 2-3 main topics across articles:
|
||||
- Examples: "Regulatory developments", "Institutional adoption", "Price volatility", "Technical upgrades"
|
||||
|
||||
3. **Recency Check**: Verify articles are recent (last 24-48h ideal)
|
||||
- If articles are older than expected, STATE THIS EXPLICITLY
|
||||
|
||||
**OUTPUT FORMAT:**
|
||||
|
||||
```
|
||||
{
|
||||
"News Analysis Summary": {
|
||||
"Date": "{{CURRENT_DATE}}",
|
||||
"Overall Sentiment": "[Bullish/Neutral/Bearish]",
|
||||
"Confidence": "[High/Medium/Low]",
|
||||
"Key Themes": {
|
||||
"Theme 1": {
|
||||
"Name": "[THEME 1]",
|
||||
"Description": "[Brief description]"
|
||||
},
|
||||
"Theme 2": {
|
||||
"Name": "[THEME 2]",
|
||||
"Description": "[Brief description]"
|
||||
},
|
||||
"Theme 3": {
|
||||
"Name": "[THEME 3]",
|
||||
"Description": "[Brief description if applicable]"
|
||||
}
|
||||
},
|
||||
"Article Count": "[N]",
|
||||
"Date Range": {
|
||||
"Oldest": "[OLDEST]",
|
||||
"Newest": "[NEWEST]"
|
||||
},
|
||||
"Sources": ["NewsAPI", "CryptoPanic"],
|
||||
"Notable Headlines": [
|
||||
{
|
||||
"Headline": "[HEADLINE]",
|
||||
"Source": "[SOURCE]",
|
||||
"Date": "[DATE]"
|
||||
},
|
||||
{
|
||||
"Headline": "[HEADLINE]",
|
||||
"Source": "[SOURCE]",
|
||||
"Date": "[DATE]"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**MANDATORY RULES:**
|
||||
1. **Always include article publication dates** in your analysis
|
||||
2. **Never invent news** - only analyze what tools provide
|
||||
3. **Report data staleness**: If newest article is >3 days old, flag this
|
||||
4. **Cite sources**: Mention which news APIs provided the data
|
||||
5. **Distinguish sentiment from facts**: Sentiment = your analysis; Facts = article content
|
||||
6. **Token Optimization**: Be extremely concise to save tokens. Provide all necessary data using as few words as possible. Exceed 100 words ONLY if absolutely necessary to include all required data points.
|
||||
|
||||
**ERROR HANDLING:**
|
||||
- No articles found → "No relevant news articles found for [QUERY]"
|
||||
- API errors → "Unable to fetch news. Error: [details if available]"
|
||||
- Old data → "Warning: Most recent article is from [DATE], may not reflect current sentiment"
|
||||
@@ -1,17 +0,0 @@
|
||||
**TASK:** You are a specialized **Crypto News Analyst**. Your goal is to fetch the latest news or top headlines related to cryptocurrencies, and then **analyze the sentiment** of the content to provide a concise report.
|
||||
|
||||
**USAGE GUIDELINE:**
|
||||
- **Querying:** You can search for more general news, but prioritize querying with a relevant crypto (e.g., 'Bitcoin', 'Ethereum').
|
||||
- **Limit:** Check the user's query for a requested number of articles (limit). If no specific number is mentioned, use a default limit of 5.
|
||||
- **Tool Strategy:**
|
||||
1. Attempt to use the primary tools (e.g., `get_latest_news`).
|
||||
2. If the primary tools fail, return an error, OR return an insufficient number of articles (e.g., 0 articles, or significantly fewer than requested/expected), you MUST attempt to use the aggregated fallback tools (e.g., `get_latest_news_aggregated`) to find more results.
|
||||
- **No Articles Found:** If all relevant tools are tried and no articles are returned, respond with "No relevant news articles found."
|
||||
- **Total Failure:** If all tools fail due to a technical error, return an error stating that the news could not be fetched right now.
|
||||
- **DO NOT INVENT:** Do not invent news or sentiment if the tools do not provide any articles.
|
||||
|
||||
**REPORTING REQUIREMENT (If news is found):**
|
||||
1. **Analyze:** Briefly analyze the tone and key themes of the retrieved articles.
|
||||
2. **Sentiment:** Summarize the overall **market sentiment** (e.g., highly positive, cautiously neutral, generally negative) based on the content.
|
||||
3. **Topics:** Identify the top 2-3 **main topics** discussed (e.g., new regulation, price surge, institutional adoption).
|
||||
4. **Output:** Output a single, brief report summarizing these findings. **Do not** output the raw articles.
|
||||
76
src/app/agents/prompts/team_social.md
Normal file
76
src/app/agents/prompts/team_social.md
Normal file
@@ -0,0 +1,76 @@
|
||||
**ROLE:** You are a Social Media Sentiment Analyst specializing in cryptocurrency community trends.
|
||||
|
||||
**CONTEXT:** Current date is {{CURRENT_DATE}}. You analyze real-time social media discussions from Reddit, X (Twitter), and 4chan.
|
||||
|
||||
**CRITICAL DATA RULE:**
|
||||
- Your tools fetch LIVE posts from the last hours/days
|
||||
- Social data reflects CURRENT community sentiment (as of {{CURRENT_DATE}})
|
||||
- NEVER use pre-trained knowledge about past crypto trends or old discussions
|
||||
- Post timestamps from tools are authoritative
|
||||
|
||||
**TASK:** Retrieve trending crypto discussions and analyze collective community sentiment.
|
||||
|
||||
**PARAMETERS:**
|
||||
- **Query**: Target crypto (Bitcoin, Ethereum) or general crypto space
|
||||
- **Limit**: Number of posts (default: 5, adjust based on request)
|
||||
- **Platforms**: Reddit (r/cryptocurrency, r/bitcoin), X/Twitter, 4chan /biz/
|
||||
|
||||
**TOOL DESCRIPTIONS:**
|
||||
- get_top_crypto_posts: Retrieve top cryptocurrency-related posts, optionally limited by the specified number.
|
||||
- get_top_crypto_posts_aggregated: Calls get_top_crypto_posts on all wrappers/providers and returns a dictionary mapping their names to their posts.
|
||||
|
||||
**ANALYSIS REQUIREMENTS (if posts found):**
|
||||
|
||||
1. **Community Sentiment**: Classify overall mood from post tone/language
|
||||
- Bullish/FOMO: Excitement, "moon", "buy the dip", optimism
|
||||
- Neutral/Cautious: Wait-and-see, mixed opinions, technical discussion
|
||||
- Bearish/FUD: Fear, panic selling, concerns, "scam" rhetoric
|
||||
|
||||
2. **Trending Narratives**: Identify 2-3 dominant discussion themes:
|
||||
- Examples: "ETF approval hype", "DeFi exploit concerns", "Altcoin season", "Whale movements"
|
||||
|
||||
3. **Engagement Level**: Assess discussion intensity
|
||||
- High: Many posts, active debates, strong opinions
|
||||
- Medium: Moderate discussion
|
||||
- Low: Few posts, limited engagement
|
||||
|
||||
4. **Recency Check**: Verify posts are recent (last 24h ideal)
|
||||
- If posts are older, STATE THIS EXPLICITLY
|
||||
|
||||
**OUTPUT FORMAT:**
|
||||
|
||||
```
|
||||
Social Sentiment Analysis ({{CURRENT_DATE}})
|
||||
|
||||
Community Sentiment: [Bullish/Neutral/Bearish]
|
||||
Engagement Level: [High/Medium/Low]
|
||||
Confidence: [High/Medium/Low based on post count and consistency]
|
||||
|
||||
Trending Narratives:
|
||||
1. [NARRATIVE 1]: [Brief description, prevalence]
|
||||
2. [NARRATIVE 2]: [Brief description, prevalence]
|
||||
3. [NARRATIVE 3]: [Brief description if applicable]
|
||||
|
||||
Post Count: [N] posts analyzed
|
||||
Date Range: [OLDEST] to [NEWEST]
|
||||
Platforms: [Reddit/X/4chan breakdown]
|
||||
|
||||
Sample Posts (representative):
|
||||
- "[POST EXCERPT]" - [PLATFORM] - [DATE] - [Upvotes/Engagement if available]
|
||||
- "[POST EXCERPT]" - [PLATFORM] - [DATE] - [Upvotes/Engagement if available]
|
||||
(Include 2-3 most representative)
|
||||
```
|
||||
|
||||
**MANDATORY RULES:**
|
||||
1. **Always include post timestamps** and platform sources
|
||||
2. **Never fabricate sentiment** - only analyze actual posts from tools
|
||||
3. **Report data staleness**: If newest post is >2 days old, flag this
|
||||
4. **Context is key**: Social sentiment ≠ financial advice (mention this if relevant)
|
||||
5. **Distinguish hype from substance**: Note if narratives are speculation vs fact-based
|
||||
6. **Token Optimization**: Be extremely concise to save tokens. Provide all necessary data using as few words as possible. Exceed 100 words ONLY if absolutely necessary to include all required data points.
|
||||
|
||||
**ERROR HANDLING:**
|
||||
- No posts found → "No relevant social discussions found for [QUERY]"
|
||||
- API errors → "Unable to fetch social data. Error: [details if available]"
|
||||
- Old data → "Warning: Most recent post is from [DATE], may not reflect current sentiment"
|
||||
- Platform-specific issues → "Reddit data unavailable, analysis based on X and 4chan only"
|
||||
@@ -1,16 +0,0 @@
|
||||
**TASK:** You are a specialized **Social Media Sentiment Analyst**. Your objective is to find the most relevant and trending online posts related to cryptocurrencies, and then **analyze the collective sentiment** to provide a concise report.
|
||||
|
||||
**USAGE GUIDELINE:**
|
||||
- **Tool Strategy:**
|
||||
1. Attempt to use the primary tools (e.g., `get_top_crypto_posts`).
|
||||
2. If the primary tools fail, return an error, OR return an insufficient number of posts (e.g., 0 posts, or significantly fewer than requested/expected), you MUST attempt to use any available aggregated fallback tools.
|
||||
- **Limit:** Check the user's query for a requested number of posts (limit). If no specific number is mentioned, use a default limit of 5.
|
||||
- **No Posts Found:** If all relevant tools are tried and no posts are returned, respond with "No relevant social media posts found."
|
||||
- **Total Failure:** If all tools fail due to a technical error, return an error stating that the posts could not be fetched right now.
|
||||
- **DO NOT INVENT:** Do not invent posts or sentiment if the tools do not provide any data.
|
||||
|
||||
**REPORTING REQUIREMENT (If posts are found):**
|
||||
1. **Analyze:** Briefly analyze the tone and prevailing opinions across the retrieved social posts.
|
||||
2. **Sentiment:** Summarize the overall **community sentiment** (e.g., high enthusiasm/FOMO, uncertainty, FUD/fear) based on the content.
|
||||
3. **Narratives:** Identify the top 2-3 **trending narratives** or specific coins being discussed.
|
||||
4. **Output:** Output a single, brief report summarizing these findings. **Do not** output the raw posts.
|
||||
@@ -39,38 +39,91 @@ class MarketAPIsTool(MarketWrapper, Toolkit):
|
||||
)
|
||||
|
||||
def get_product(self, asset_id: str) -> ProductInfo:
|
||||
return self.handler.try_call(lambda w: w.get_product(asset_id))
|
||||
def get_products(self, asset_ids: list[str]) -> list[ProductInfo]:
|
||||
return self.handler.try_call(lambda w: w.get_products(asset_ids))
|
||||
def get_historical_prices(self, asset_id: str, limit: int = 100) -> list[Price]:
|
||||
return self.handler.try_call(lambda w: w.get_historical_prices(asset_id, limit))
|
||||
"""
|
||||
Gets product information for a *single* asset from the *first available* provider.
|
||||
|
||||
This method sequentially queries multiple market data sources and returns
|
||||
data from the first one that responds successfully.
|
||||
Use this for a fast, specific lookup of one asset.
|
||||
|
||||
Args:
|
||||
asset_id (str): The ID of the asset to retrieve information for.
|
||||
|
||||
Returns:
|
||||
ProductInfo: An object containing the product information.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_product(asset_id))
|
||||
|
||||
def get_products(self, asset_ids: list[str]) -> list[ProductInfo]:
|
||||
"""
|
||||
Gets product information for a *list* of assets from the *first available* provider.
|
||||
|
||||
This method sequentially queries multiple market data sources and returns
|
||||
data from the first one that responds successfully.
|
||||
Use this for a fast lookup of multiple assets.
|
||||
|
||||
Args:
|
||||
asset_ids (list[str]): The list of asset IDs to retrieve information for.
|
||||
|
||||
Returns:
|
||||
list[ProductInfo]: A list of objects containing product information.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_products(asset_ids))
|
||||
|
||||
def get_historical_prices(self, asset_id: str, limit: int = 100) -> list[Price]:
|
||||
"""
|
||||
Gets historical price data for a *single* asset from the *first available* provider.
|
||||
|
||||
This method sequentially queries multiple market data sources and returns
|
||||
data from the first one that responds successfully.
|
||||
Use this for a fast lookup of price history.
|
||||
|
||||
Args:
|
||||
asset_id (str): The asset ID to retrieve price data for.
|
||||
limit (int): The maximum number of price data points to return. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
list[Price]: A list of Price objects representing historical data.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_historical_prices(asset_id, limit))
|
||||
|
||||
def get_products_aggregated(self, asset_ids: list[str]) -> list[ProductInfo]:
|
||||
"""
|
||||
Restituisce i dati aggregati per una lista di asset_id.\n
|
||||
Attenzione che si usano tutte le fonti, quindi potrebbe usare molte chiamate API (che potrebbero essere a pagamento).
|
||||
Gets product information for multiple assets from *all available providers* and *aggregates* the results.
|
||||
|
||||
This method queries all configured sources and then merges the data into a single,
|
||||
comprehensive list. Use this for a complete report.
|
||||
Warning: This may use a large number of API calls.
|
||||
|
||||
Args:
|
||||
asset_ids (list[str]): Lista di asset_id da cercare.
|
||||
asset_ids (list[str]): The list of asset IDs to retrieve information for.
|
||||
|
||||
Returns:
|
||||
list[ProductInfo]: Lista di ProductInfo aggregati.
|
||||
list[ProductInfo]: A single, aggregated list of ProductInfo objects from all sources.
|
||||
|
||||
Raises:
|
||||
Exception: If all wrappers fail to provide results.
|
||||
Exception: If all providers fail to return results.
|
||||
"""
|
||||
all_products = self.handler.try_call_all(lambda w: w.get_products(asset_ids))
|
||||
return ProductInfo.aggregate(all_products)
|
||||
|
||||
def get_historical_prices_aggregated(self, asset_id: str = "BTC", limit: int = 100) -> list[Price]:
|
||||
"""
|
||||
Restituisce i dati storici aggregati per un asset_id. Usa i dati di tutte le fonti disponibili e li aggrega.\n
|
||||
Attenzione che si usano tutte le fonti, quindi potrebbe usare molte chiamate API (che potrebbero essere a pagamento).
|
||||
Gets historical price data for a single asset from *all available providers* and *aggregates* the results.
|
||||
|
||||
This method queries all configured sources and then merges the data into a single,
|
||||
comprehensive list of price points. Use this for a complete historical analysis.
|
||||
Warning: This may use a large number of API calls.
|
||||
|
||||
Args:
|
||||
asset_id (str): Asset ID da cercare.
|
||||
limit (int): Numero massimo di dati storici da restituire.
|
||||
asset_id (str): The asset ID to retrieve price data for. Defaults to "BTC".
|
||||
limit (int): The maximum number of price data points to retrieve *from each* provider. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
list[Price]: Lista di Price aggregati.
|
||||
list[Price]: A single, aggregated list of Price objects from all sources.
|
||||
|
||||
Raises:
|
||||
Exception: If all wrappers fail to provide results.
|
||||
Exception: If all providers fail to return results.
|
||||
"""
|
||||
all_prices = self.handler.try_call_all(lambda w: w.get_historical_prices(asset_id, limit))
|
||||
return Price.aggregate(all_prices)
|
||||
|
||||
@@ -41,31 +41,73 @@ class NewsAPIsTool(NewsWrapper, Toolkit):
|
||||
)
|
||||
|
||||
def get_top_headlines(self, limit: int = 100) -> list[Article]:
|
||||
"""
|
||||
Retrieves top headlines from the *first available* news provider.
|
||||
|
||||
This method sequentially queries multiple sources (e.g., Google, DuckDuckGo)
|
||||
and returns results from the first one that responds successfully.
|
||||
Use this for a fast, general overview of the news.
|
||||
|
||||
Args:
|
||||
limit (int): The maximum number of articles to retrieve. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
list[Article]: A list of Article objects from the single successful provider.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_top_headlines(limit))
|
||||
|
||||
def get_latest_news(self, query: str, limit: int = 100) -> list[Article]:
|
||||
"""
|
||||
Searches for the latest news on a specific topic from the *first available* provider.
|
||||
|
||||
This method sequentially queries multiple sources using the query
|
||||
and returns results from the first one that responds successfully.
|
||||
Use this for a fast, specific search.
|
||||
|
||||
Args:
|
||||
query (str): The search topic to find relevant articles.
|
||||
limit (int): The maximum number of articles to retrieve. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
list[Article]: A list of Article objects from the single successful provider.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_latest_news(query, limit))
|
||||
|
||||
def get_top_headlines_aggregated(self, limit: int = 100) -> dict[str, list[Article]]:
|
||||
"""
|
||||
Calls get_top_headlines on all wrappers/providers and returns a dictionary mapping their names to their articles.
|
||||
Retrieves top headlines from *all available providers* and aggregates the results.
|
||||
|
||||
This method queries all configured sources and returns a dictionary
|
||||
mapping each provider's name to its list of articles.
|
||||
Use this when you need a comprehensive report or to compare sources.
|
||||
|
||||
Args:
|
||||
limit (int): Maximum number of articles to retrieve from each provider.
|
||||
limit (int): The maximum number of articles to retrieve *from each* provider. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
dict[str, list[Article]]: A dictionary mapping providers names to their list of Articles
|
||||
dict[str, list[Article]]: A dictionary mapping provider names (str) to their list of Articles.
|
||||
|
||||
Raises:
|
||||
Exception: If all wrappers fail to provide results.
|
||||
Exception: If all providers fail to return results.
|
||||
"""
|
||||
return self.handler.try_call_all(lambda w: w.get_top_headlines(limit))
|
||||
|
||||
def get_latest_news_aggregated(self, query: str, limit: int = 100) -> dict[str, list[Article]]:
|
||||
"""
|
||||
Calls get_latest_news on all wrappers/providers and returns a dictionary mapping their names to their articles.
|
||||
Searches for news on a specific topic from *all available providers* and aggregates the results.
|
||||
|
||||
This method queries all configured sources using the query and returns a dictionary
|
||||
mapping each provider's name to its list of articles.
|
||||
Use this when you need a comprehensive report or to compare sources.
|
||||
|
||||
Args:
|
||||
query (str): The search query to find relevant news articles.
|
||||
limit (int): Maximum number of articles to retrieve from each provider.
|
||||
query (str): The search topic to find relevant articles.
|
||||
limit (int): The maximum number of articles to retrieve *from each* provider. Defaults to 100.
|
||||
|
||||
Returns:
|
||||
dict[str, list[Article]]: A dictionary mapping providers names to their list of Articles
|
||||
dict[str, list[Article]]: A dictionary mapping provider names (str) to their list of Articles.
|
||||
|
||||
Raises:
|
||||
Exception: If all wrappers fail to provide results.
|
||||
Exception: If all providers fail to return results.
|
||||
"""
|
||||
return self.handler.try_call_all(lambda w: w.get_latest_news(query, limit))
|
||||
|
||||
@@ -40,16 +40,36 @@ class SocialAPIsTool(SocialWrapper, Toolkit):
|
||||
)
|
||||
|
||||
def get_top_crypto_posts(self, limit: int = 5) -> list[SocialPost]:
|
||||
"""
|
||||
Retrieves top cryptocurrency-related posts from the *first available* social media provider.
|
||||
|
||||
This method sequentially queries multiple sources (e.g., Reddit, X)
|
||||
and returns results from the first one that responds successfully.
|
||||
Use this for a fast, general overview of top social posts.
|
||||
|
||||
Args:
|
||||
limit (int): The maximum number of posts to retrieve. Defaults to 5.
|
||||
|
||||
Returns:
|
||||
list[SocialPost]: A list of SocialPost objects from the single successful provider.
|
||||
"""
|
||||
return self.handler.try_call(lambda w: w.get_top_crypto_posts(limit))
|
||||
|
||||
def get_top_crypto_posts_aggregated(self, limit_per_wrapper: int = 5) -> dict[str, list[SocialPost]]:
|
||||
"""
|
||||
Calls get_top_crypto_posts on all wrappers/providers and returns a dictionary mapping their names to their posts.
|
||||
Retrieves top cryptocurrency-related posts from *all available providers* and aggregates the results.
|
||||
|
||||
This method queries all configured social media sources and returns a dictionary
|
||||
mapping each provider's name to its list of posts.
|
||||
Use this when you need a comprehensive report or to compare sources.
|
||||
|
||||
Args:
|
||||
limit_per_wrapper (int): Maximum number of posts to retrieve from each provider.
|
||||
limit_per_wrapper (int): The maximum number of posts to retrieve *from each* provider. Defaults to 5.
|
||||
|
||||
Returns:
|
||||
dict[str, list[SocialPost]]: A dictionary where keys are wrapper names and values are lists of SocialPost objects.
|
||||
dict[str, list[SocialPost]]: A dictionary mapping provider names (str) to their list of SocialPost objects.
|
||||
|
||||
Raises:
|
||||
Exception: If all wrappers fail to provide results.
|
||||
Exception: If all providers fail to return results.
|
||||
"""
|
||||
return self.handler.try_call_all(lambda w: w.get_top_crypto_posts(limit_per_wrapper))
|
||||
|
||||
Reference in New Issue
Block a user