
Chart Annotation
Extra guidance for draw_chart_annotation, which works without loading this.
Install
npx skills add ginlix-ai/LangAlpha --skill chart-annotation -g -a claude-code -y- Repository
- ginlix-ai/LangAlpha2.2k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,145 tokens
- Runs scripts
- No, instructions only
What it does
Extra guidance for draw_chart_annotation, which works without loading this. Covers choosing between similar variants, aligning times to bars, several charts in one turn, and answering a chart selection the user sends.
Chart Annotation Skill
When to use
You want to call out a technical level, a pattern, or an event on a stock's
price chart. Drawing directly on the chart is almost always clearer than
describing it in prose. Reach for draw_chart_annotation whenever you would
otherwise say "look at the level around 205" or "notice the downtrend from
October to December".
MarketView is the app's live, trading-chart style price chart page (pan, zoom, switch timeframes). You do not need the user to be on it to annotate. If they are, the drawing appears on their live chart immediately. Anywhere else in the app, the same drawing renders as a chart card in the chat that opens the live chart beside the conversation, so annotate freely whenever it helps, then mention the user can click the card to see it.
Both tools are always available; this guide is how to use them well:
draw_chart_annotation, add a single annotation to a chart.manage_chart_annotations, list, remove, or clear annotations.
Interactive chart vs. a Python chart (deliverable)
There are two ways to show price information visually, pick by what the user needs:
- The annotation tools (interactive). Annotations land on a live, pannable chart: MarketView's, or the one a chart card in the chat opens. Best when the user just wants to see and explore a level, pattern, or event themselves, quick, in-the-moment, nothing to hand off.
- A Python chart (deliverable). A static image you render with code and embed in a report or document. Best when the output is a deliverable the user keeps, shares, or exports, a research note, PDF, or deck.
The two aren't exclusive: draw on the live chart for a quick look, render a Python chart when it belongs in a written artifact, or do both.
Charts are identified by SYMBOL:timeframe
Every annotation belongs to a chart identified by its ticker + timeframe
(e.g. NVDA:1day), that pair is the chart's id:
