Route telemetry/download prompts to vista-data MCP server

[thefactremains]

Summary

• Integrates the new vista-data MCP server into VISTA's skill definition
• ClickHouse (telemetry) and Elasticsearch (downloads) are now routable via real MCP tools instead of generating dummy data
• Added data source selection logic, schema discovery guidance, and prompt-to-tool routing for reports #13, #14, #16

What changed in SKILL.md

• MCP connector table: ClickHouse and Elasticsearch now show actual tool names (query_clickhouse, search_elasticsearch, etc.)
• New section: Telemetry & Downloads Data Source Selection Logic (parallel to existing Jira logic)
• Reports #13, #14, #16: Updated with data source guidance and query patterns
• Natural language triggers: Added 7 new telemetry/download prompt examples with tool routing

Prerequisites

Filip (or whoever runs this) needs to install the vista-data MCP server with their credentials:

claude mcp add vista-data \
  -e CLICKHOUSE_HOST=... -e CLICKHOUSE_PASSWORD=... \
  -e ES_HOST=... -e ES_PASSWORD=... \
  -- uvx --from git+https://github.com/Percona-Lab/vista-data-mcp vista-data-mcp

Test plan

• Install vista-data MCP server with ClickHouse credentials
• Run /vista Show me download trends for MySQL — should use search_elasticsearch
• Run /vista How many active PS 8.4 instances? — should use query_clickhouse
• Run /vista What's the version distribution for PXC? — should use query_clickhouse
• Verify reports still work correctly when vista-data MCP is not installed (graceful fallback)

🤖 Generated with Claude Code