# pine-visualizer

Turns a trading idea or a YouTube tutorial into a Pine Script spec: which indicators, which entry and exit rules, which numbers. Useful before you write the indicator itself.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 305 installs · ★ 218
- Author: TradersPost
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/TradersPost/pinescript-agents/tree/HEAD/skills/pine-visualizer/SKILL.md
- Updated: 2026-07-23
- HTML: https://affpapa.org/en/nevibecode/skills/pine-visualizer

## What it does

This skill takes a trading concept apart until it reads like instructions for Pine Script. Hand it a YouTube link and it runs the bundled `tools/video-analyzer.py`: metadata and transcript come in, then the script looks for indicators (RSI, MACD, EMA and the like), chart patterns such as breakouts or divergences, entry and exit rules, risk rules, and the exact periods, percentages and levels the presenter mentions. The write-up lands in `projects/analysis/` so you can reopen it later.

Descriptions in plain text go through the same filter. The skill pushes custom types (UDTs) first: define the fields each record carries, keep the collection in one array, add methods for drawing and cleanup. It advises storing timestamps rather than bar numbers for anything you draw, since bar numbers stop at the 5000-bar history limit. Loops should use `for...in`; the classic counter loop with an array bound is easy to get wrong.

The skill can call `Read`, `Glob`, `Grep`, `Bash` and `WebFetch`. Video work needs Python; when a clip has no captions, add `--whisper`, optionally with a larger model. Captions are cached, so a second pass over the same link returns fast. The finished spec is meant to go to the `pine-developer` skill, so the two are used together.

The analyzer script ships with the repository — without it, video analysis won't start.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add TradersPost/pinescript-agents --skill pine-visualizer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pine-visualizer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pine-visualizer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add TradersPost/pinescript-agents --skill pine-visualizer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pine-visualizer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add TradersPost/pinescript-agents --skill pine-visualizer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pine-visualizer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install TradersPost/pinescript-agents pine-visualizer
```

2. **Manually: put the files in place**
- File: `.github/skills/pine-visualizer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add TradersPost/pinescript-agents --skill pine-visualizer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/TradersPost/pinescript-agents --path skills/pine-visualizer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pine-visualizer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add TradersPost/pinescript-agents --skill pine-visualizer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/TradersPost/pinescript-agents/tree/HEAD/skills/pine-visualizer/SKILL.md

## When to use it
- extract entry and exit rules from a YouTube tutorial
- list the indicators and periods a trading idea relies on
- plan storage for chart objects with custom types
- turn a verbal strategy into a Pine Script specification
- catch fragile patterns in an idea, like parallel arrays

## Example prompts
- Analyze this video and pull out the entry and exit conditions: https://youtube.com/watch?v=ABC123
- Plan the UDT structure for this idea, with draw() and delete() methods
- Write a spec for an EMA crossover indicator with explicit periods

## Similar
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [ask-matt](https://affpapa.org/en/nevibecode/skills/ask-matt.md) — skill · 766587 installs
- [to-tickets](https://affpapa.org/en/nevibecode/skills/to-tickets.md) — skill · 711230 installs
- [writing-plans](https://affpapa.org/en/nevibecode/skills/writing-plans.md) — skill · 282859 installs
- [caveman-review](https://affpapa.org/en/nevibecode/skills/caveman-review.md) — skill · 411800 installs
- [caveman-compress](https://affpapa.org/en/nevibecode/skills/caveman-compress.md) — skill · 411500 installs

From the same set: [traderspost/pinescript-agents](https://affpapa.org/en/nevibecode/by/traderspost/pinescript-agents.md) — 5 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md