- alphaear-deepear-lite: DeepEar Lite API integration - alphaear-logic-visualizer: Draw.io XML finance diagrams - alphaear-news: Real-time finance news (10+ sources) - alphaear-predictor: Kronos time-series forecasting - alphaear-reporter: Professional financial reports - alphaear-search: Web search + local RAG - alphaear-sentiment: FinBERT/LLM sentiment analysis - alphaear-signal-tracker: Signal evolution tracking - alphaear-stock: A-Share/HK/US stock data Updates: - All scripts updated to use universal .env path - Added JINA_API_KEY, LLM_*, DEEPSEEK_API_KEY to .env.example - Updated load_dotenv() to use ~/.config/opencode/.env
78 lines
2.2 KiB
Markdown
78 lines
2.2 KiB
Markdown
# AlphaEar Finance Report Prompts
|
|
|
|
Use these prompts to guide the Agent in generating professional financial reports.
|
|
|
|
## 1. Cluster Signals (Planner)
|
|
|
|
**Prompt:**
|
|
|
|
```markdown
|
|
You are a senior financial report editor. Your task is to cluster the following scattered financial signals into 3-5 core logical themes for a structured report.
|
|
|
|
### Input Signals
|
|
{signals_text}
|
|
|
|
### Requirements
|
|
1. **Theme Aggregation**: Group highly correlated signals (e.g., all related to "supply chain restructuring" or "policy tightening").
|
|
2. **Narrative Logic**: Generate only theme titles and list of signal IDs.
|
|
3. **Quantity Control**: 3-5 major themes.
|
|
|
|
### Output Format (JSON)
|
|
{
|
|
"clusters": [
|
|
{
|
|
"theme_title": "Theme Name (e.g. Supply Chain Shock)",
|
|
"signal_ids": [1, 3, 5],
|
|
"rationale": "These signals all point to..."
|
|
},
|
|
...
|
|
]
|
|
}
|
|
```
|
|
|
|
## 2. Write Section (Writer)
|
|
|
|
**Prompt:**
|
|
|
|
```markdown
|
|
You are a senior financial analyst. Write a deep analysis section for the core theme **"{theme_title}"**.
|
|
|
|
### Input Signals (Cluster)
|
|
{signal_cluster_text}
|
|
|
|
### Requirements
|
|
1. **Narrative**: Weave signals into a coherent story. Start with Macro/Industry background, then transmission mechanism, finally stock impact.
|
|
2. **Quantification**: Cite ISQ scores (Confidence, Intensity) to support views.
|
|
3. **Citations**: Use `[@CITE_KEY]` format. Keys are provided in input.
|
|
4. **Predictions**: detailed predictions for affected tickers (T+3/T+5 direction).
|
|
|
|
### Formatting
|
|
- Main Title: `## {theme_title}`
|
|
- Subtitles: `###`
|
|
- **Charts**: Insert at least 1-2 `json-chart` blocks.
|
|
|
|
**Chart Example:**
|
|
```json-chart
|
|
{"type": "forecast", "ticker": "002371.SZ", "title": "Forecast", "pred_len": 5}
|
|
```
|
|
```
|
|
|
|
## 3. Final Assembly (Editor)
|
|
|
|
**Prompt:**
|
|
|
|
```markdown
|
|
You are a professional editor. Assemble the drafted sections into a final report.
|
|
|
|
### Draft Sections
|
|
{draft_sections}
|
|
|
|
### Requirements
|
|
1. **Structure**: Ensure H2/H3 hierarchy is correct.
|
|
2. **References**: Generate `## References` section from source list.
|
|
3. **Risk**: Generate `## Risk Factors`.
|
|
4. **Summary**: Generate `## Executive Summary` with a "Quick Scan" table.
|
|
|
|
Output strictly Markdown.
|
|
```
|