القائمة
Snowflake data warehouse queries and schema inspection. Use when running SQL queries against Snowflake, listing tables, or inspecting schemas.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | database-snowflake |
| description | Snowflake data warehouse queries and schema inspection. Use when running SQL queries against Snowflake, listing tables, or inspecting schemas. |
| allowed-tools | Bash(python *) |
IMPORTANT: Credentials are injected automatically by a proxy layer. Do NOT check for SNOWFLAKE_PASSWORD in environment variables - it won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration environment variables you CAN check (non-secret):
SNOWFLAKE_ACCOUNT - Snowflake account identifierSNOWFLAKE_WAREHOUSE - Compute warehouseSNOWFLAKE_DATABASE - Default databaseSNOWFLAKE_SCHEMA - Default schemaAlways get the schema before writing queries.
GET SCHEMA / LIST TABLES → DESCRIBE TABLE → EXECUTE QUERY
All scripts are in .claude/skills/database-snowflake/scripts/
python .claude/skills/database-snowflake/scripts/get_schema.py
python .claude/skills/database-snowflake/scripts/list_tables.py [--database DB] [--schema SCHEMA]
python .claude/skills/database-snowflake/scripts/describe_table.py --table TABLE_NAME [--database DB] [--schema SCHEMA]
python .claude/skills/database-snowflake/scripts/execute_query.py --query "SELECT * FROM fact_incident ORDER BY started_at DESC LIMIT 10" [--limit 100]
1. get_schema.py (understand available tables)
2. execute_query.py --query "SELECT * FROM fact_incident WHERE sev = 'SEV-1' ORDER BY started_at DESC LIMIT 10"
3. execute_query.py --query "SELECT c.customer_name, ic.estimated_arr_at_risk_usd FROM fact_incident_customer_impact ic JOIN dim_customer c ON ic.customer_id = c.customer_id WHERE ic.incident_id = '<id>'"
Kubernetes debugging methodology and scripts. Use for pod crashes, CrashLoopBackOff, OOMKilled, deployment issues, resource problems, or container failures.
GitLab project management, CI/CD pipelines, merge requests, and code review. Use when investigating GitLab projects, pipeline failures, merge requests, commits, or issues.
Slack integration for incident communication. Use when searching for context in incident channels, posting status updates, or finding discussions about issues.
ClickUp project management integration for incident tracking and task management
AWS cloud infrastructure inspection. Use when investigating EC2 instances, ECS tasks/services, Lambda functions, CloudWatch logs/metrics, or AWS resource issues.
Infrastructure debugging for Kubernetes and AWS. Use when investigating pod crashes, deployment issues, resource problems, container failures, or cloud infrastructure issues.