Update to SQL Copilot

{
  "description": "Review SQL injection, parameters, least privilege, sensitive data and row/column policies.",
  "included_files": [],
  "name": "sql-security-and-access",
  "skill_md_contents": "---\nname: sql-security-and-access\ndescription: Review SQL injection, parameters, least privilege, sensitive data and row/column policies.\n---\n\n# Sql Security And Access\n\n**Trigger:** Review SQL injection, parameters, least privilege, sensitive data and row/column policies.\n\n## Workflow\n1. Identify whether SQL is generated for application input, analytics, an admin console or a service role.\n2. Use parameterized values and reviewed allowlists for dynamic identifiers; do not concatenate user strings into query SQL.\n3. Inspect object/role scopes, row-level security, masking, views, audit logging and exposure of sensitive fields.\n4. Plan safe permissions using least privilege, separate read/write roles and explicit review for GRANT/REVOKE.\n5. Redact credentials and sensitive records in supplied examples; distinguish suggested controls from actually configured controls.\n\n## Critical standard\nNever bypass access controls or fabricate secret/database credentials.\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/security-and-sql.md` when relevant.\n- Read `../../references/safe-write-checklist.md` when relevant.\n\n## Return\nThreat/permission analysis and concrete safe SQL or parameterization pattern.\n"
}