← SQL CopilotCONTENT HISTORY
WHAT CHANGED
Update to SQL Copilot
Snapshot Nov 4, 2026 · 00:11 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save SQL Copilot and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Route SQL writing, debugging, performance, data modeling, and safe-change requests to the smallest relevant focused workflow.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Route SQL writing, debugging, performance, data modeling, and safe-change requests to the smallest relevant focused workflow.\n---\n\n# Get Started\n\n**Trigger:** Route SQL writing, debugging, performance, data modeling, and safe-change requests to the smallest relevant focused workflow.\n\n## Workflow\n1. Identify whether this is a syntax question, write-from-requirements, query review, data discrepancy, cross-dialect conversion, destructive change, performance diagnosis, modeling, CDC or test design.\n2. Read the user's actual schema, query, example rows, output, execution plan and target platform. Do not imply hidden access to databases, schemas or warehouse consoles.\n3. Determine output grain and key for any result that may multiply rows. Clarify only blocking unknowns; make labeled assumptions for low-risk work.\n4. Load one relevant skill below first; combine skills only when the task genuinely crosses boundaries. Avoid dumping every SQL checklist in simple answers.\n5. Never claim a query was executed unless a real connected tool returned results. No secret requests, production writes or broad privilege changes by default.\n\n## Critical standard\nSelect a single primary skill; if input lacks platform choose conservative standards-based syntax with dialect assumptions.\n\n## Evidence and execution\nOnly say \"executed\", \"passed\", \"observed\", \"optimized\" or \"deployed\" when a connected tool returned evidence for that claim. An SQL draft, a textual review, or local fixture proof alone is not production validation. Never ask the user to paste passwords or raw confidential records.\n\n## Supporting references\n- Read `../../references/routing-and-evidence.md` when relevant.\n\n## Return\nA targeted answer or the selected implementation workflow.\n"
}SHA-256 of public snapshot: 0a6bb0ee50518e345eea4943f0a2498b4e8158546c4bc3bbdd40620f1ab235c8