Menu
HR & operations rules: SCD current-record filtering, issue resolution metrics.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Load when working with Xata Postgres branches: forking a branch, building or testing dbt models on a branch, wiring dbt to a branch's credentials, diffing two branches, or the pre-merge impact report. Covers create_xata_branch, delete_xata_branch, get_dbt_profile, xata_branch_diff, schema_diff_branches, and pgroll migrations.
Load at Step 1 before exploring the project. Covers output shape inference, incremental model handling, and what to trust in YML.
Use this skill before writing any SQL query. Covers: output shape inference (cardinality clues from the question), efficient schema exploration, iterative CTE-based query building, structured verification loop (row count, NULL audit, fan-out check, sample inspection), error recovery protocol, saving output to result.sql and result.csv, turn budget management, and common benchmark traps.
Populate the knowledge base from dbt project research. Proposes entries across all 6 categories at org, project, and connection scopes.
Load FIRST before any dbt project work. Covers the full 8-step dbt workflow: project scanning, skill loading, validation, macro discovery, research, technical spec, SQL writing, and verification. Also covers output shape inference, incremental model handling, and what to trust in YML.
Loaded at Step 2 for the full workflow. Covers column naming, type preservation, JOIN defaults, lookup joins, sibling models, materialization, packages, and filtering rules.
| name | domain-hr |
| description | HR & operations rules: SCD current-record filtering, issue resolution metrics. |
When aggregating workforce or issue metrics, drive FROM the fact/event table (issues, tickets, time_entries), not the dimension table (employees, teams, projects). Employees with zero activity MUST NOT appear in activity reports - they have no data to aggregate.
Exception: if a parent/entity table exists whose primary key matches the GROUP BY key AND some parent rows have no matching children in the detail table, drive FROM the parent and LEFT JOIN the detail. Parent rows with zero children must appear with count=0, not be silently dropped.
Tables with _fivetran_start/_fivetran_end or valid_from/valid_to columns track historical state. You MUST filter to the current record before aggregating.
Current record: _fivetran_end = '9999-12-31' OR _fivetran_end IS NULL - verify the sentinel value by querying 3-5 rows before assuming.
For _fivetran_active columns, always use WHERE COALESCE(_fivetran_active, true) - never WHERE _fivetran_active = true because NULL values (meaning "active") would be filtered out.
NEVER aggregate across all historical rows without filtering to current records first - doing so double-counts entities that changed state.
Include ONLY closed issues in resolution time calculations - open issues have no close timestamp.
NEVER substitute current_date for a missing close timestamp - this produces artificially inflated resolution times that corrupt the metric.
