with one click
sql-reporting
// Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.
// Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.
Adopt and maintain the apache-steward framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo — every other skill is a symlink the adopt sub-action wires up. Sub-actions: `/setup-steward` — first-time adoption (default; main-checkout only) `/setup-steward upgrade` — refresh the gitignored snapshot per the committed lock (main-checkout only) `/setup-steward worktree-init` — symlink a worktree's snapshot to the main's `/setup-steward verify` — health check + drift detection `/setup-steward override <skill>` — open or scaffold an agentic override in `.apache-steward-overrides/` `/setup-steward unadopt` — reverse the adoption (snapshot, locks, symlinks, hook, doc sections); preserves
Add or update translations for the Apache Airflow UI. Guides through setting up locales, scaffolding translation files, translating with locale-specific guidelines, and validating results. Use when working with i18n tasks in airflow-core/src/airflow/ui/public/i18n/locales/.
Replace the manual commit-by-commit classification step in `breeze release-management prepare-provider-documentation` with AI-driven classification. For each provider with pending changes, analyze every PR (using sub-agents per PR), pay special attention to potentially breaking changes by inspecting the actual diff, scope multi-provider PRs to the current provider's slice, ask the release manager when uncertain, and apply version bumps + changelog entries. Use during the regular provider release cycle as an alternative to the interactive breeze prompts.
Generate verified recipe playbooks from AIPs with PR implementations (post mode), or speculative user stories from AIPs without implementations (pre mode). Use when the user provides an AIP URL or AIP content, optionally with PR URLs and file paths.
| name | sql-reporting |
| description | Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics. |
| license | Apache-2.0 |
Apply this skill before writing or running any analytics SQL so reports stay consistent and safe.
Use this skill when the task involves:
SELECT explicit column names, never SELECT *.order_count, not count(*)).LIMIT unless an aggregate already collapses
the result set.COUNT(DISTINCT ...) over a sub-query when de-duplicating.SELECT *.Return the final SQL in a fenced ```sql block, then one sentence describing what the query returns.