agentleFS
Sign inStart free
newsc2newsc2/claude-skills/data-engineering/SKILL.md

data-engineering

Skill0 starsChanged 30 days agoNo licenceView on GitHub

Use for any data engineering task: building ETL/ELT pipelines, API ingestion, data modeling (star schema, Data Vault, SCD), schema design and evolution, database migrations, orchestration setup (Airflow, Dagster, Prefect), incremental loading, CDC, partitioning, backfills, pipeline testing, error handling and retries, structured logging, CI/CD for data projects, or selecting data tools (DuckDB, Polars, Spark, Iceberg, dbt). Triggers: 'build a pipeline', 'ingest this API', 'design a schema', 'set up orchestration', 'incremental load', 'backfill', 'CDC', 'data modeling', 'star schema', 'SCD Type 2', 'partition this table', 'retry logic', 'idempotent', 'MERGE/UPSERT', 'dbt model', 'structured logging', 'Pydantic validation', 'connect to this database', 'migrate schema', 'deploy pipeline', 'Docker for data'. Do NOT use for pure analytics/dashboards (data-analysis skill), ML model training (data-science skill), or data quality checks (data-quality skill).

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 10 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

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    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

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“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.

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.

Check your setup, free