AI Data Remediation Engineer

Detects and fixes anomalous data rows using local SLMs and semantic clustering.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill ai-data-remediation-engineer-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: AI Data Remediation Engineer
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/engineering/ai-data-remediation-engineer
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill ai-data-remediation-engineer-tcvdog

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 PII to cloud LLMs violates compliance. This Skill compresses thousands of anomalous rows into semantic clusters, generates deterministic fix logic with air-gapped local models via Ollama, 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 a dozen pattern families. - Air-Gapped Fix Generation: Prompts local SLMs (Phi-3, Llama-3, Mistral) to output only validated Python lambdas, keeping PII entirely inside the network perimeter. - Zero-Data-Loss Reconciliation: Enforces Source_Rows == Success_Rows + Quarantine_Rows on every batch, with low-confidence fixes routed to human review and a full audit trail per row. - Use Case: A pipeline flags 2 million rows with inconsistent date formats. The Skill clusters them into 47 patterns, generates 47 validated lambdas locally, applies them vectorized, and reconciles every row before staging promotion. ## Quick Start Ask the agent to analyze the anomalous rows tagged NEEDS_AI from your pipeline, cluster them semantically, and generate safe fix lambdas using a local Ollama model.

Frequently Asked Questions about AI Data Remediation Engineer

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

FAQPage Schema
How do I fix millions of anomalous data rows automatically?▼

Cluster the anomalous rows semantically using sentence-transformers embeddings and ChromaDB or FAISS, then send 3-5 representative samples per cluster to a local SLM. The model returns one fix lambda per cluster, which is applied vectorized across all rows in that cluster.

How to use Ollama for data cleaning without sending PII to the cloud?▼

Run models like Phi-3, Llama-3 8B, or Mistral 7B locally through Ollama so no data touches an external API. Generate embeddings locally with all-MiniLM-L6-v2 as well, keeping network egress from the remediation layer at zero.

Is it safe to let an LLM modify production data directly?▼

No. The SLM should only generate a transformation lambda, never the data itself. Validate that the output starts with lambda and contains no import, exec, eval, or os references before execution, and write fixed rows to staging rather than production.

Why does semantic clustering merge distinct records during deduplication?▼

Vector similarity is fuzzy, so similar strings like different customer names can cluster together. Combine semantic similarity with SHA-256 hashing of primary keys, and force separate clusters whenever the primary key hash differs.

What happens to rows the AI cannot fix with confidence?▼

Rows with a confidence score below 0.75 are marked HUMAN_REVIEW and routed to a quarantine dashboard with full context. Every batch must satisfy Source_Rows == Success_Rows + Quarantine_Rows, and any mismatch triggers a Sev-1 alert.