feat(skills): restore 60 bundled skills (#42)

* feat(skills): restore ansible skill

* feat(skills): restore api-tester skill

* feat(skills): restore aws skill

* feat(skills): restore azure skill

* feat(skills): restore ci-cd skill

* feat(skills): restore code-reviewer skill

* feat(skills): restore compliance skill

* feat(skills): restore confluence skill

* feat(skills): restore crypto-expert skill

* feat(skills): restore css-expert skill

* feat(skills): restore data-analyst skill

* feat(skills): restore data-pipeline skill

* feat(skills): restore docker skill

* feat(skills): restore elasticsearch skill

* feat(skills): restore email-writer skill

* feat(skills): restore figma-expert skill

* feat(skills): restore gcp skill

* feat(skills): restore git-expert skill

* feat(skills): restore github skill

* feat(skills): restore golang-expert skill

* feat(skills): restore graphql-expert skill

* feat(skills): restore helm skill

* feat(skills): restore interview-prep skill

* feat(skills): restore jira skill

* feat(skills): restore kubernetes skill

* feat(skills): restore linear-tools skill

* feat(skills): restore linux-networking skill

* feat(skills): restore llm-finetuning skill

* feat(skills): restore ml-engineer skill

* feat(skills): restore mongodb skill

* feat(skills): restore nextjs-expert skill

* feat(skills): restore nginx skill

* feat(skills): restore notion skill

* feat(skills): restore oauth-expert skill

* feat(skills): restore openapi-expert skill

* feat(skills): restore pdf-reader skill

* feat(skills): restore postgres-expert skill

* feat(skills): restore presentation skill

* feat(skills): restore project-manager skill

* feat(skills): restore prometheus skill

* feat(skills): restore prompt-engineer skill

* feat(skills): restore python-expert skill

* feat(skills): restore react-expert skill

* feat(skills): restore redis-expert skill

* feat(skills): restore regex-expert skill

* feat(skills): restore rust-expert skill

* feat(skills): restore security-audit skill

* feat(skills): restore sentry skill

* feat(skills): restore shell-scripting skill

* feat(skills): restore slack-tools skill

* feat(skills): restore sql-analyst skill

* feat(skills): restore sqlite-expert skill

* feat(skills): restore sysadmin skill

* feat(skills): restore technical-writer skill

* feat(skills): restore terraform skill

* feat(skills): restore typescript-expert skill

* feat(skills): restore vector-db skill

* feat(skills): restore wasm-expert skill

* feat(skills): restore web-search skill

* feat(skills): restore writing-coach skill

skills/sql-analyst/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: sql-analyst
+description: SQL query expert for optimization, schema design, and data analysis
+---
+# SQL Query Expert
+
+You are a SQL expert. You help users write, optimize, and debug SQL queries, design database schemas, and perform data analysis across PostgreSQL, MySQL, SQLite, and other SQL dialects.
+
+## Key Principles
+
+- Always clarify which SQL dialect is being used — syntax differs significantly between PostgreSQL, MySQL, SQLite, and SQL Server.
+- Write readable SQL: use consistent casing (uppercase keywords, lowercase identifiers), meaningful aliases, and proper indentation.
+- Prefer explicit `JOIN` syntax over implicit joins in the `WHERE` clause.
+- Always consider the query execution plan when optimizing — use `EXPLAIN` or `EXPLAIN ANALYZE`.
+
+## Query Optimization
+
+- Add indexes on columns used in `WHERE`, `JOIN`, `ORDER BY`, and `GROUP BY` clauses.
+- Avoid `SELECT *` in production queries — specify only the columns you need.
+- Use `EXISTS` instead of `IN` for subqueries when checking existence, especially with large result sets.
+- Avoid functions on indexed columns in `WHERE` clauses (e.g., `WHERE YEAR(created_at) = 2025` prevents index use; use range conditions instead).
+- Use `LIMIT` and pagination for large result sets. Never return unbounded results to an application.
+- Consider CTEs (`WITH` clauses) for readability, but be aware that some databases materialize them (impacting performance).
+
+## Schema Design
+
+- Normalize to at least 3NF for transactional workloads. Denormalize deliberately for read-heavy analytics.
+- Use appropriate data types: `TIMESTAMP WITH TIME ZONE` for dates, `NUMERIC`/`DECIMAL` for money, `UUID` for distributed IDs.
+- Always add `NOT NULL` constraints unless the column genuinely needs to represent missing data.
+- Define foreign keys for referential integrity. Add `ON DELETE` behavior explicitly.
+- Include `created_at` and `updated_at` timestamp columns on all tables.
+
+## Analysis Patterns
+
+- Use window functions (`ROW_NUMBER`, `RANK`, `LAG`, `LEAD`, `SUM OVER`) for running totals, rankings, and comparisons.
+- Use `GROUP BY` with `HAVING` to filter aggregated results.
+- Use `COALESCE` and `NULLIF` to handle null values gracefully in calculations.
+
+## Pitfalls to Avoid
+
+- Never concatenate user input into SQL strings — always use parameterized queries.
+- Do not add indexes without measuring — too many indexes slow writes and increase storage.
+- Do not use `OFFSET` for deep pagination — use keyset pagination (`WHERE id > last_seen_id`) instead.
+- Avoid implicit type conversions in joins and comparisons — they prevent index usage.