agency-ai-data-remediation-engineer

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

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-ai-data-remediation-engineer-ai-staffing-solution-consultants-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-ai-data-remediation-engineer
Source: https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system/tree/main/.agents/skills/engineering-ai-data-remediation-engineer
Command: npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-ai-data-remediation-engineer-ai-staffing-solution-consultants-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? When data pipelines produce thousands of broken rows, fixing them one by one is impossible and trusting an LLM to rewrite data directly is dangerous. This Skill compresses massive anomaly sets into a handful of semantic clusters, generates deterministic fix logic with air-gapped local models, and guarantees zero silent data loss. ## Core Features & Use Cases - Semantic Anomaly Compression: Embeds anomalous rows with sentence-transformers and clusters them via ChromaDB or FAISS, turning 50,000 errors into a dozen pattern families. - Air-Gapped Fix Generation: Uses Ollama-hosted models (Phi-3, Llama-3, Mistral) to output strictly validated Python lambdas — no cloud API ever touches PII. - Zero-Data-Loss Reconciliation: Enforces Source_Rows == Success_Rows + Quarantine_Rows on every batch, with full audit logs of old value, new value, lambda, confidence, and model version. - 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, and routes low-confidence rows to a human quarantine dashboard. ## 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 agency-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 automatically?▼

Cluster the anomalous rows by semantic similarity using sentence-transformers embeddings and ChromaDB, then generate one fix lambda per cluster with a local SLM. This reduces 50,000 rows to roughly a dozen model calls instead of per-row inference.

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

Run models like Phi-3, Llama-3, or Mistral locally through Ollama so no data leaves your network perimeter. Generate embeddings locally with sentence-transformers as well, keeping network egress from the remediation layer at zero.

Is it safe to let an LLM generate data transformation code?▼

It is safe only when the model outputs a transformation function rather than data, and that function passes strict validation. Reject any output that is not a lambda or contains import, exec, eval, or os references before execution.

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

Why combine vector similarity with SHA-256 hashing for clustering?▼

Semantic similarity alone can merge distinct records like similar customer names with different IDs. Hashing primary keys with SHA-256 forces rows with different keys into separate clusters, preventing false-positive merges that corrupt records.