skills.rest
SignalPilot-Labs
SignalPilot-LabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

domain-hr

Apply HR/ops rules to filter SCD current records and compute closed-issue resolution metrics in analytics pipelines.

475|25|Updated Mar 31, 2026
Search Tags:#analytics#metrics#etl#data-quality#hr#scd
One-click install
npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill domain-hr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-hr
Source: https://github.com/SignalPilot-Labs/SignalPilot/tree/main/benchmark/signalpilot-plugin/skills/domain-hr
Command: npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill domain-hr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HR and operations analytics often suffer from stale history in slowly changing dimensions and miscalculated metrics when all historical rows are counted. This skill provides rules to filter to the current record and ensure reliable issue resolution timing.

Core Features & Use Cases

  • SCD current-record filtering: enforce that queries focus on the current state using sentinel values (e.g., _fivetran_end) and LEFT JOINs to preserve zero-activity rows.
  • Active flag handling: use COALESCE(_fivetran_active, true) to avoid excluding potentially active rows with NULL.
  • Issue resolution metrics: include only closed issues in resolution times to prevent bias from open tickets.
  • Use Case: For HR dashboards, compute time-to-close only on finished issues and compare current vs historical states.

Quick Start

Apply these HR rules to your data pipeline to filter current records and compute resolution metrics for HR issues.

Frequently Asked Questions about domain-hr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter SCD current records in HR analytics pipelines?▼

Filter SCD current records by excluding sentinel values like _fivetran_end and using LEFT JOINs to preserve zero-activity rows. This ensures HR queries focus on the current state without dropping valid historical data.

Why does COALESCE need to be used with _fivetran_active?▼

Use COALESCE(_fivetran_active, true) to handle active flags because NULL values can exclude potentially active rows. This prevents accidentally filtering out current records during SCD data quality checks.

How do I calculate issue resolution time without biasing open tickets?▼

Calculate issue resolution time by including only closed issues in your metrics. This prevents bias from open tickets and ensures accurate time-to-close measurements for HR operations dashboards.

What is the best way to avoid double-counting historical rows in SCD aggregations?▼

Avoid double-counting in historical aggregations by enforcing correct SCD current-record filtering and applying proper handling of _fivetran_active via COALESCE to ensure only current rows are summed.

How do LEFT JOINs improve SCD data quality in metrics pipelines?▼

LEFT JOINs improve SCD data quality by preserving zero-activity rows when filtering current records. This maintains accurate baseline data for HR analytics instead of dropping rows with no recent activity.

Related Skills

Explore More Data & Analytics Skills→
treasure-datatreasure-data
21

aps-doc-golden

Document golden layer tables with SCD types, business rules, and data quality scoring.

Official
Advanced
mehdicmehdic

velocity-tracker

Analyze historical project data to compute velocity, cycle times, and trends.

Community
Advanced
accelerate-dataaccelerate-data

dbt-snapshot-scd2

Automate SCD Type 2 snapshot creation and management in dbt on Microsoft Fabric.

Official
Advanced
MindOpsTeamMindOpsTeam

cfo-analise-estrategica

Compute and compare financial metrics from ERP data across monthly periods.

Official
Advanced