agentleFS
SwastikPandey1024SwastikPandey1024/agentic-engineering-os/.agents/skills/data-engineering/SKILL.md

data-engineering

Skill1 starsChanged 3 months agoMITView on GitHub

Data cleaning, schema enforcement, time-series transformations, Daylight Saving Time (DST) handling, rolling features, and leak-free feature pipelines.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use qa-testing, infrastructure-as-code and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • miketrombaSkill

    qa-testing

    Autonomously QA and verify the application using browser automation. Use when verifying code changes, testing features, validating bug fixes, or confirming any work done on the application. Triggers on requests to "test this", "verify this works", "QA this change", "make sure it works", or after implementing features that need validation.

    Also in 3 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 3 projects that use this

  • onejaejaeSkill

    api-documentation

    API 문서화 스킬. Notion과 Postman에 API 명세를 추가합니다. Use when documenting APIs, updating Notion database, or adding Postman requests.

    Also in 3 projects that use this

  • AnthropicSkill

    system-design

    Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

    Also in 4 projects that use this

  • VercelSkill

    technical-writing

    Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 10

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Engineering Skill

1. When Should I Use This?

Use this skill when:

  • Cleaning, transforming, or validating tabular, time-series, or batch datasets.
  • Handling timestamp discontinuities, Daylight Saving Time (DST) duplicate hours, structural gaps, or missing values.
  • Engineering temporal, cyclical (sine/cosine), lag, and rolling-window statistical features.
  • Building reproducible, versioned data pipelines using Pandas, Polars, or NumPy.

2. What Should I Inspect First?

  1. Schema & Data Types: Inspect column types, null percentages, date formats (ISO8601, UNIX timestamps, naive vs UTC timezones).
  2. Temporal Integrity (For Time Series):
    • Are there duplicate timestamps? (Common in fall DST clock fallbacks).
    • Are there missing intervals? (Common in spring DST clock skips).
    • Is the data strictly sorted chronologically?
  3. Target Variable Stability: Inspect target distribution, outliers, and extreme spikes.

3. What Workflow Should I Follow?

Load Raw Invariant Dataset
            ↓
Data Quality Audit (Nulls, Duplicates, Types, Extreme Outliers)
            ↓
Temporal Resolution & DST Handling (Mean aggregate duplicate hours / resample)
            ↓
Feature Engineering (Calendar, Sine/Cosine Cyclical, Lags, Rolling Windows)
            ↓
Strict Chronological / Group-Aware Train-Val-Test Split
            ↓
Validate Feature Order & Export Processed Parquet / CSV Datasets

Time-Series DST & Temporal Feature Engineering Pipeline

# data_engineering/pipeline.py
import numpy as np
import pandas as pd

def process_energy_time_series(df: pd.DataFrame, datetime_col: str, target_col: str) -> pd.DataFrame:
    # 1. Parse timestamps and sort chronologically
    df[datetime_col] = pd.to_datetime(df[datetime_col])
    df = df.sort_values(datetime_col).reset_index(drop=True)

    # 2. DST Duplicate Timestamp Resolution: Mean aggregate duplicate hours
    df = df.groupby(datetime_col, as_index=False)[target_col].mean()

    # 3. Calendar & Cyclical Features
    dt = df[datetime_col].dt
    df['hour'] = dt.hour
    df['dayofweek'] = dt.dayofweek
    df['month'] = dt.month
    df['is_weekend'] = (df['dayofweek'] >= 5).astype(int)

    # Cyclical hour encoding (smooth 24-hour periodic boundary)
    df['hour_sin'] = np.sin(2 * np.pi * df['hour'] / 24.0)
    df['hour_cos'] = np.cos(2 * np.pi * df['hour'] / 24.0)

    # 4. Lag Features (Historical lookbacks)
    df['lag_1h'] = df[target_col].shift(1)
    df['lag_24h'] = df[target_col].shift(24)
    df['lag_168h'] = df[target_col].shift(168) # 1-week seasonal lag

    # 5. Rolling Window Statistics (Strictly backward-looking)
    df['rolling_mean_24h'] = df[target_col].shift(1).rolling(window=24).mean()
    df['rolling_std_24h'] = df[target_col].shift(1).rolling(window=24).std()
    df['rolling_mean_168h'] = df[target_col].shift(1).rolling(window=168).mean()

    # 6. Drop warm-up NaN rows created by the 168h lookback
    df = df.dropna().reset_index(drop=True)
    return df

def split_chronological(df: pd.DataFrame, train_ratio=0.70, val_ratio=0.15):
    n = len(df)
    train_end = int(n * train_ratio)
    val_end = int(n * (train_ratio + val_ratio))

    train_df = df.iloc[:train_end].copy()
    val_df = df.iloc[train_end:val_end].copy()
    test_df = df.iloc[val_end:].copy()

    print(f"Train: {len(train_df)} | Val: {len(val_df)} | Test: {len(test_df)}")
    return train_df, val_df, test_df

4. What Decisions Should I Make?

ChallengeEngineering Rule
Rolling Stats LeakageAlways apply .shift(1) before computing .rolling() when forecasting current target $y_t$. Otherwise, $y_t$ leaks into the rolling mean of time $t$.
File Storage FormatUse Parquet with Snappy compression for intermediate processed datasets. It preserves exact column types, handles nulls natively, and is 5-10x faster to load than CSV.
Missing ValuesImpute time-series gaps using forward-fill (ffill) or linear interpolation only for small gaps (<= 3 hours). Never use future lookahead backfill (bfill).

5. What Should I Avoid?

  • NEVER shuffle time-series rows: Preserving temporal ordering is non-negotiable.
  • NEVER overwrite raw source datasets: Raw data must remain immutable in datasets/raw/. Always write transformed outputs to datasets/processed/.
  • NEVER use current timestamp features that are unavailable at inference time: Only use historical lag features.

6. How Should I Verify Success?

# 1. Run data engineering pipeline
python data_engineering/pipeline.py

# 2. Check for missing values and temporal continuity
python -c "
import pandas as pd
df = pd.read_parquet('datasets/processed/cleaned_features.parquet')
assert df.isna().sum().sum() == 0, 'Null values remain in processed data!'
print('Data engineering validation clean. Total rows:', len(df))
"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.