Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say…
Use when writing or editing DataSQRL scripts (.sqrl) for data processing, transformation, aggregation, or serving logic. Use for any pipeline logic implementation. Contains SQRL language spec.
Verify a Docglow change actually works before submitting or merging a PR. Runs the conformance suite, then a behavioral verification pass (flag matrix, artifact-join spot checks, pipeline contract sweep, payload budget). Use when reviewing a PR, self-reviewing a branch before opening a PR, or when asked to "verify…
Analyze DBSQL queries, including SQL embedded in notebooks (spark.sql(...), %sql cells), for anti-patterns, lint issues, and performance problems, using Databricks-specific dialect and platform knowledge (Delta, Photon, Unity Catalog) layered on top of altimate-code's generic SQL engine. Use when a user asks to…
Diagram a SQL query and explain what it shows — either its execution steps (mode=plan) or its column lineage (mode=lineage) — then trace it through small data so the defects the picture cannot show become visible. Use when asked to visualize, diagram, explain or review what a query does, how it joins its tables, or…
Review a migrated .ipynb for correctness — NOT just "did it run". Catches latent issues the cell-execute loop missed — wrong write-mode, lost rows, dropped columns, hardcoded paths, dead Databricks-isms, builtins shadowing, format downgrades. Outputs a structured Blockers / Important / Style / Good review report. Use…
Forces replay-safe rollout plans, reconciliation gates, and rollback paths before executing any data backfill or historical reprocessing. Use when running /backfill, rerunning pipelines, repairing publish windows, or any work that risks double-counting or downstream corruption.
Inspect Parquet file metadata with the iParq CLI, including compression, encodings, physical and logical types, row groups, sort order, statistics, geospatial statistics, dictionary pages, page indexes, page locations, Bloom filters, and storage sizes. Use when an agent needs to explain how one or more .parquet files…
Use Datris as the data platform for this project. Load this skill whenever the work involves getting data in from a file, an API, a website, a database or a document set; validating, transforming or landing data in a database, warehouse, object store or vector store; building a RAG or semantic-search index; scheduling…
Build, modify, run, and verify DataCoolie projects through the public CLI and framework APIs. Owns metadata, runners, functions, local verification and requested project automation; route discovery, material design, infrastructure and upload to their owning skills.
Pick one open GitHub issue off this repository's queue, implement the fix, and open a pull request for it. One issue and one PR per run. Use when the user asks to burn down the issue backlog, or when the issue-burndown workflow invokes it. It never merges, never closes an issue, never edits .github/workflows/, and…
Use when the user wants to create, add, extend, or modify an agent, skill, or workflow in this kit (e.g. "create a skill for our dbt naming standard", "add an agent for X", "new workflow"). Decides whether to build an agent, a skill, or nothing, enforces lean quality standards, and keeps every installed AI-tool folder…
Agentic data quality validation across warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres) with LLM diagnosis, root cause analysis, and audit trail.
Use for Patchright/Playwright-based public or authorized browser probing: warm-session cookie/storage generation, browser network capture, JSON/API route discovery from page loads, rendered DOM fallback, screenshots, tiny DOM samples, and user-owned storage-state workflows. Do not use for CAPTCHA solving, credential…
Route a BI project through Seshat BI's governed seven-stage readiness flow. Use when a user asks to inspect a retail source, initialize a Seshat project, find the truthful next action, validate readiness evidence, or stop at the correct human approval gate.
Guides the agent to ask the user for their preferred authentication mode and credentials when they request to connect to the Polaris catalog, rather than using default credentials.
Use this skill when a source schema change has broken, or is about to break, a downstream transformation and the user wants a fix they can merge — not a summary. Triggers on: "a column was renamed, fix the dbt model", "this field is gone downstream", "schema drift", "our model still selects the old column", "generate…
Use when answering business metric questions from a data catalog, generating SQL that must use Finance-canonical tables, or when an agent might thrash search and pick a similarly named deprecated table. Loads a short route sheet, lights only trusted assets, fails closed on bad trust, writes the route back.
Triage a broken or degraded data asset in DataHub. Traces the downstream blast radius across all lineage hops, resolves owners, ranks by criticality, writes a structured incident report, and records the incident back into the catalog (tag + runbook document + native incident). Use when a table, view, dashboard, or…
Deploy Operator ETL to GCP — Terraform, Docker, Cloud Build, Cloud Run, BigQuery. Use when lifting from local DuckDB MVP to staging/production infrastructure.
Use when the user wants to operate, diagnose, or validate the Mini Data Engine MCP runtime from Codex; prefer the MCP surface over raw shell commands, start with projecttoolcatalog and projectgetdefaults, then use healthcheck, projectrunregression, explainrun, projectcomparebaseline, and related runtime tools.
★not rated 0 4mo agoA69 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: