polymarket
Query Polymarket: markets, prices, orderbooks, history.
Install
Show step-by-stepHide step-by-step
Open your terminal
- Mac: Press โ Space, type "Terminal", press Enter
- Windows: Press Win R, type "cmd", press Enter
Paste the command above and press Enter
Use the Copy command button, then paste in your terminal (Mac: โV, Windows: Ctrl V).
Restart Claude Code
Close and reopen Claude Code, or start a new session, so it picks up the new skill.
Where it lives
Comments
Related skills
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path โ even casually (like \"the xlsx in my downloads\") โ and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
paid-compute-launch
Use before paid accelerator work that launches, scales, retries, or automatically continues. This includes training and batch inference plus synthetic-data generation, evaluations and sweeps, or multi-Job fleets. Allows bounded experiments below $5 without asking. Requires measured cost and hardware evidence, durable partial outputs, tested pause and resume, explicit approval at larger spending boundaries, and fleet-wide containment after shared failures.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes