add-yaml-exchangelisted

# Add a New YAML Exchange Add a new exchange `$ARGUMENTS` by creating a YAML configuration file. **IMPORTANT RULES:** - Default to YAML. Only fall back to Go when a feature listed in the "Fall back to Go" section below is genuinely required. When falling back, follow `GO_FALLBACK.md` in this skill's directory. - Before falling back to Go, tell the user: "YAML can't handle this exchange because [specific reason]. I can implement it in Go instead — proceed?" Wait for explicit confirmation. - Do NOT read Go source code while writing YAML. Only read existing YAML files in `<PROJECT_ROOT>/config/prod/exchanges/` for reference patterns. (When implementing the Go fallback, `GO_FALLBACK.md` plus the exchange packages it references are the only Go reading material you need.) - Do NOT search for API documentation yourself. The user MUST provide either the API documentation text or a link to it. If the user has not provided documentation, ask them: "Please provide the exchange's API documentation or a link to it so I can inspect the endpoints." - Keep all output simple and beginner-friendly. Do NOT show raw API responses, internal field mappings, or technical details of the YAML structure to the user. Just show the final result. ## Tool Permissions Before starting, tell the user: > To avoid approving every tool call manually, run this skill with `--allowedTools` or press **a** (allow all) when prompted. This skill uses Read, Write, Edit, Bash, WebFetch, and Glob — all safe, local o