Loading...
Loading...
Found 975 Skills
SQL analysis skill for Ascend PyTorch Profiler / msprof DB (e.g., ascend_pytorch_profiler*.db, msprof_*.db). Convert natural language questions (operator latency, communication, dispatch, scheduling, schema/table queries) into safe and executable SQL, and extract table structure details from official documents as needed.
Expert SQL query writing, optimization, and database schema design with support for PostgreSQL, MySQL, SQLite, and SQL Server. Use when working with databases for: (1) Writing complex SQL queries with joins, subqueries, and window functions, (2) Optimizing slow queries and analyzing execution plans, (3) Designing database schemas with proper normalization, (4) Creating indexes and improving query performance, (5) Writing migrations and handling schema changes, (6) Debugging SQL errors and query issues
Use this skill whenever working with QuestDB — a high-performance time-series database. Trigger on any mention of QuestDB, time-series SQL with SAMPLE BY, LATEST ON, ASOF JOIN, ILP ingestion, or the questdb Python/Go/Java/Rust/.NET client libraries. Also trigger when writing Grafana queries against QuestDB, creating materialized views for time-series rollups, working with order book or financial market data in QuestDB, or any SQL that involves designated timestamps or time-partitioned tables. QuestDB extends SQL with unique time-series keywords — standard PostgreSQL or MySQL patterns will fail. Always read this skill before writing QuestDB SQL to avoid hallucinating incorrect syntax.
Convert Dune (Trino) SQL queries to Allium (Snowflake) SQL. SQL dialect conversions (Trino → Snowflake) apply to all chains. Comprehensive Solana and EVM chain mappings included.
Manages datasets, tables, and jobs in BigQuery, and integrates with BigQuery ML and Gemini for advanced data analytics and AI-driven insights. Use when you need to interact with BigQuery, run SQL queries, manage BigQuery resources, or leverage BigQuery's built-in ML capabilities. Also use when performing data analysis, ingesting data into BigQuery, or developing AI applications on BigQuery.
Kinetica SQL query knowledge. Activate when the user is writing analytical queries for Kinetica, asking about Kinetica-specific functions, or working with geospatial, time-series, graph, or vector data.
Build end-to-end ETL pipelines with Harvard Art Museums API, SQL analytics, and Streamlit visualization
End-to-end data engineering pipeline with Harvard Art Museums API, ETL processing, SQL analytics, and Streamlit visualization
Query SQLite, PostgreSQL, and MySQL databases and export results to CSV/JSON. Use when: (1) Extracting data for reports, (2) Database backup and migration, (3) Data analysis workflows, or (4) Automated database queries.
Run a Google Alerts-style keyword coverage tracker. Uses news-search for recent keyword queries, lets the LLM dedupe and classify real features versus junk, stores decisions in SQLite, and alerts only on new real coverage.
Detect and fix SQL injection vulnerabilities in any framework. Covers Laravel (DB::raw, whereRaw), Node.js (template literals in queries), Python (f-strings in SQL), and Cloudflare D1. Enforces parameterized bindings everywhere. Use when writing database queries, reviewing code for injection, or fixing SQL injection findings.
Databricks SQL query optimizer: analyzes a slow SQL query, rewrites it for speed using SQL-level optimizations only, validates byte-for-byte result equivalence, and benchmarks both versions with statistical significance testing. Use this skill whenever the user wants to optimize, speed up, tune, or benchmark a SQL query on Databricks. Trigger on: "/databricks-sql-autotuner", "optimize this SQL", "make this query faster", "tune my Databricks query", "benchmark SQL on Databricks", "speed up this spark SQL", "SQL performance on Databricks", "EXPLAIN this query", "why is my query slow on Databricks", "SQL query optimization Databricks", or whenever a user pastes a SQL query and mentions performance, slowness, or runtime.