engineering-engineering-ai-data-remediation-engineer

Detects, clusters, and fixes anomalous data rows using local SLMs and semantic embeddings.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill engineering-engineering-ai-data-remediation-engineer-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-engineering-ai-data-remediation-engineer
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/engineering-engineering-ai-data-remediation-engineer
Command: npx skills add https://github.com/30eggis/walwal-harness --skill engineering-engineering-ai-data-remediation-engineer-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sentence-transformers, chromadb, ollama, pandas.

What problem does it solve? Broken data at scale cannot be fixed row-by-row, and sending sensitive records to cloud LLMs violates PII compliance. This Skill compresses thousands of anomalous rows into a handful of semantic clusters, generates deterministic fix logic with air-gapped local models, and enforces a mathematical zero-data-loss guarantee on every batch. ## Core Features & Use Cases - Semantic Anomaly Compression: Embeds suspect rows with sentence-transformers and clusters them in ChromaDB or FAISS, turning 50,000 errors into roughly a dozen actionable pattern families. - Air-Gapped Fix Generation: Uses Ollama-hosted models (Phi-3, Llama-3, Mistral) to output strictly validated Python lambdas, with forbidden-term rejection and confidence thresholds routing low-certainty clusters to human quarantine. - Zero-Data-Loss Reconciliation: Enforces Source_Rows == Success_Rows + Quarantine_Rows on every batch, triggering a Sev-1 alert on any mismatch, plus a full audit log of every transformation. - Use Case: A pipeline flags 50,000 rows with inconsistent date formats. The Skill clusters them into 12 patterns, generates 12 validated lambdas locally, applies them vectorized via pandas, and reconciles every row before staging promotion. ## Quick Start Assign this worker a mission to remediate the anomalous rows tagged NEEDS_AI in the staging table and produce a full audit log with reconciliation results.

Frequently Asked Questions about engineering-engineering-ai-data-remediation-engineer

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

FAQPage Schema
How do I fix thousands of anomalous data rows without calling an LLM per row?▼

Embed the anomalous rows locally with sentence-transformers, cluster them in ChromaDB or FAISS, and send only 3-5 representative samples per cluster to the model. This compresses 50,000 errors into roughly a dozen SLM calls, then applies each fix vectorized across the whole cluster.

How to generate data fix logic with Ollama local models?▼

Prompt a local model like Phi-3 with a strict system prompt requiring JSON output containing a Python lambda, confidence score, and pattern type. Validate the output starts with 'lambda' and contains no import, exec, eval, or os references before executing it on data.

Can I use LLMs on data containing PII or medical records?▼

Yes, but only with air-gapped local models via Ollama so no data leaves the network perimeter. Embeddings are also generated locally, keeping network egress from the remediation layer at zero for compliance.

Why does semantic clustering merge distinct records incorrectly?▼

Vector similarity is fuzzy, so similar-looking rows like 'John Doe ID:101' and 'Jon Doe ID:102' may cluster together. Combine embeddings with SHA-256 hashing of primary keys and force separate clusters when PK hashes differ to prevent false-positive merges.

What happens to rows the AI cannot fix confidently?▼

Rows with a confidence score below 0.75 are routed to a Human Quarantine Dashboard with full context instead of being auto-fixed. Every batch must satisfy Source_Rows == Success_Rows + Quarantine_Rows, and any mismatch triggers a Sev-1 data loss alert.