Best use case
AlphaEar Signal Tracker Skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
## Overview
Teams using AlphaEar Signal Tracker Skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/alphaear-signal-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How AlphaEar Signal Tracker Skill Compares
| Feature / Agent | AlphaEar Signal Tracker Skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
## Overview
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AlphaEar Signal Tracker Skill
## Overview
This skill provides logic to track and update investment signals. It assesses how new market information impacts existing signals (Strengthened, Weakened, Falsified, or Unchanged).
## Capabilities
### 1. Track Signal Evolution
### 1. Track Signal Evolution (Agentic Workflow)
**YOU (the Agent)** are the Tracker. Use the prompts in `references/PROMPTS.md`.
**Workflow:**
1. **Research**: Use **FinResearcher Prompt** to gather facts/price for a signal.
2. **Analyze**: Use **FinAnalyst Prompt** to generate the initial `InvestmentSignal`.
3. **Track**: For existing signals, use **Signal Tracking Prompt** to assess evolution (Strengthened/Weakened/Falsified) based on new info.
**Tools:**
- Use `alphaear-search` and `alphaear-stock` skills to gather the necessary data.
- Use `scripts/fin_agent.py` helper `_sanitize_signal_output` if needing to clean JSON.
**Key Logic:**
- **Input**: Existing Signal State + New Information (News/Price).
- **Process**:
1. Compare new info with signal thesis.
2. Determine impact direction (Positive/Negative/Neutral).
3. Update confidence and intensity.
- **Output**: Updated Signal.
**Example Usage (Conceptual):**
```python
# This skill is currently a pattern extracted from FinAgent.
# In a future refactor, it should be a standalone utility class.
# For now, refer to `scripts/fin_agent.py`'s `track_signal` method implementation.
```
## Dependencies
- `agno` (Agent framework)
- `sqlite3` (built-in)
Ensure `DatabaseManager` is initialized correctly.Related Skills
okr-tracker-creator
Okr Tracker Creator - Auto-activating skill for Enterprise Workflows. Triggers on: okr tracker creator, okr tracker creator Part of the Enterprise Workflows skill category.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
data-lineage-tracker
Data Lineage Tracker - Auto-activating skill for Data Pipelines. Triggers on: data lineage tracker, data lineage tracker Part of the Data Pipelines skill category.
recipe-create-expense-tracker
Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.
angular-signals
Implement signal-based reactive state management in Angular v20+. Use for creating reactive state with signal(), derived state with computed(), dependent state with linkedSignal(), and side effects with effect(). Triggers on state management questions, converting from BehaviorSubject/Observable patterns to signals, or implementing reactive data flows.
tech-debt-tracker
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.
repairing-signal-tower
信号塔修复 - Stella尝试修复或建造信号发射装置,希望联系地球或发送求救信号
emergency-distress-signal
紧急求救 - 飞船坠毁后与Stella的首次联系,帮助她评估损伤并制定初步生存计划
chronicle-project-tracker
Manage Chronicle project development using database-tracked milestones, next steps, and roadmap visualization. Works with MCP tools (fast, structured) or CLI commands (portable). Use when planning features, tracking progress, viewing roadmap, or linking sessions to milestones. Eliminates manual DEVELOPMENT_HISTORY.md updates.
goal-tracker
Track goal progress, derive state from execution, identify gaps, trigger actions. Use for goal status checks, progress reviews, and operational goal management.
latency-tracker
Per-call and aggregated latency tracking for MEV infrastructure. Use when implementing performance monitoring or debugging slow operations. Triggers on: latency, timing, performance, slow, speed, instrumentation.
installing-skill-tracker
Installs Claude Code hooks for automatic skill usage measurement. Use when setting up skill tracking infrastructure in a new project. NOT when hooks are already installed (run verify.py to check).