Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with copy-paste-ready commands, a clear sequenced workflow, and clean one-level progressive disclosure to references/commands.md. Its main weakness is conciseness: several intro paragraphs explain CDP/CORS/Electron internals and a sibling-skill comparison that Claude doesn't need to run the commands.
Suggestions
Trim the 'How it works' CDP/CORS/Electron-main-process paragraph to one sentence or move it to references/commands.md; Claude only needs the commands, not the network-stack rationale.
Cut or shorten the headless-alternative comparison paragraph (sibling tradingview-mcp) in the body, or relocate it to references so the overview stays execution-focused.
Add an explicit verify-after-launch checkpoint ('after launch, re-run opencli tradingview status and only proceed when CDP is reachable') to close the destructive-relaunch loop with a hard validation gate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is lean operational tables and commands, but the intro paragraphs over-explain internals Claude doesn't need to act — e.g. the CDP/CORS/Electron main-process mechanism ('Page-context fetch is blocked by browser CORS preflight... the desktop app uses Electron's main process (Node network stack) to bypass this') and the headless-alternative comparison paragraph add background beyond what's required to execute. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover common cases — e.g. 'opencli tradingview options-chain --ticker SNDK --expiry 2026-05-22 -f json' and a complete screener example with --columns, --filter JSON, and --sort — plus enumerated output columns per command. | 5 / 5 |
Workflow Clarity | Steps 1–5 are clearly sequenced with a status-check branch (READY/NOT_INSTALLED/SETUP_NEEDED), a layout-save warning before the destructive relaunch, and a diagnostics step, but there is no tight validate→fix→retry feedback loop and the launch warning is advisory rather than a forced verify step. | 4 / 5 |
Progressive Disclosure | A single real one-level reference (references/commands.md, confirmed present) holds the bulk of flag/output detail, while the body keeps a tight overview with clearly signaled pointers in Step 3 rule 6 and the Reference Files section — well split and easy to navigate. | 5 / 5 |
Total | 17 / 20 Passed |