Update to Winrate

{
  "description": "Use for League of Legends stats questions answered from Winrate data: champion win rates, counters, builds, pro play and leaderboards. Covers writing and debugging the SQL behind them.",
  "included_files": [
    {
      "relative_path": "references/champion-sql.md",
      "size_in_bytes": 10039
    },
    {
      "relative_path": "references/common-sql.md",
      "size_in_bytes": 2860
    },
    {
      "relative_path": "references/leaderboard-sql.md",
      "size_in_bytes": 3679
    },
    {
      "relative_path": "references/pro-player-sql.md",
      "size_in_bytes": 13129
    }
  ],
  "name": "sql",
  "skill_md_contents": "---\nname: sql\ndescription: \"Use for League of Legends stats questions answered from Winrate data: champion win rates, counters, builds, pro play and leaderboards. Covers writing and debugging the SQL behind them.\"\n---\n\n# SQL Skill\n\n## When To Use\n\nUse this skill when the user asks for:\n\n- SQL query writing or debugging\n- data exploration and comparisons\n- evidence-backed analysis from Winrate datasets\n\n## Workflow\n\n1. Clarify what metric and scope the user wants.\n2. Read the relevant reference file in `references/` before writing SQL.\n3. Start with a small validation query (`LIMIT 20` or narrow filters).\n4. Expand to the full analysis query once shape and semantics are correct.\n5. Summarize findings with concrete numbers from query output.\n\n## Query Rules\n\n- Prefer explicit filters for patch, region, queue, and tier when relevant.\n- Avoid full scans when a filtered query can answer the question.\n- Use stable aliases and readable CTEs for multi-step logic.\n- For \"best player on champion\" requests, prefer `summoner_leaderboard` templates over tiny-sample `summoner_match` rankings.\n- Never fabricate results. If a query fails, explain the error and fix it.\n\n## Tooling Notes\n\n- Use `run_sql({ sql })` to execute global ClickHouse SQL.\n- Load supporting docs or references from `references/` when needed.\n- Tables and columns come from `get_schema` (live); `get_guide(\"sql-schema-reference\")` has the full written reference.\n- Champion, item and rune names by ID are not bundled here: call `get_guide(\"champions\")`, `get_guide(\"items\")` or `get_guide(\"runes\")`.\n\n## Showing results\n\nshow_results draws the columns your query returns, in SELECT order. Pick the view that fits them:\n\n- table: any columns. Lists read row by row: rankings, matchups, builds.\n- bars: a name column, then the number to compare; up to 24 rows. More numbers show as text beside each bar.\n- line: a patch or date column, then the numbers to follow over time. A games column shows under the axis.\n- scatter: a name column, then two numbers: the first goes across, the second up. A games column sizes the points.\n- spread: a name column, then one number. Every row on one line around their average, weighted by a games column if there is one. For one champion against many.\n\nThese columns draw pictures: champion_id, champion_name, opponent_champion_id, killer_champion_id, victim_champion_id (portrait and name); item_id, item_0 to item_5, before_item_id, after_item_id (item icon and name); position (role icon); tier (rank crest). Alias IDs to them, for example other_champion_id AS opponent_champion_id, and select one column per champion: champion_id or champion_name, not both. Names ending in _rate or _pct show as percents.\n\nKeep patch as the numeric patch column (1620, never text like '16.20'): the card formats it and draws lines over it.\nUse the listed column names (win_rate, games, champion_id…) rather than your own, so the card can label and draw them.\n\nJoins, CTEs and UNIONs are fine: only the output columns matter. If the columns don't fit the view, the card shows a table and show_results says why.\n\n## Reference Files\n\nBefore writing queries, load the relevant file in `references/`.\nChoose the reference that matches the task and follow its command/query pattern.\n\n## References\n\n- `references/common-sql.md`\n- `references/pro-player-sql.md`\n- `references/champion-sql.md`\n- `references/leaderboard-sql.md`\n"
}