data-quality-auditor

Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "data-quality-auditor" with this command: npx skills add AlexYedi/skillsmp-alexyedi-alexyedi-data-quality-auditor

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Security

data-engineering-lifecycle-and-principles

Apply Reis & Housley's Data Engineering Lifecycle (Generation → Storage → Ingestion → Transformation → Serving) plus the six undercurrents (Security, Data Management, DataOps, Data Architecture, Orchestration, Software Engineering) and the nine architecture principles (common components, plan for failure, scalability, leadership, always architecting, loose coupling, reversibility, security, FinOps). Use when scoping a new data platform, diagnosing why a data system is failing, deciding what role / team structure a company needs, or evaluating maturity. Triggers: "build a data platform", "are we doing data engineering right", "what's the data engineering lifecycle", "data team structure", "data maturity", "data engineering principles", "data engineer vs data scientist".

Repository SourceNeeds Review

-1AlexYedi

Security

waterfall-blueprint

Design provider sequences, throttling logic, and credit policies for enrichment waterfalls across 150+ B2B data sources. Use when building or tuning waterfall sequences, selecting provider stacks per enrichment type, or auditing credit consumption.

Repository SourceNeeds Review

-1AlexYedi

General

database-designer

Use when the user asks to design database schemas, plan data migrations, optimize queries, choose between SQL and NoSQL, or model data relationships.

Repository SourceNeeds Review

-1AlexYedi

Web3

mdm-and-federated-data-governance

Apply Master Data Management (MDM) styles (Consolidation, Registry, Centralized, Coexistence), federated governance via data contracts and policy automation, data catalog + metalake architecture, knowledge graphs for metadata, semantic layers, and access control models (ACL, RBAC, ABAC + PEP/PDP/PIP/PAP). Use when scoping MDM, choosing an MDM style, designing a data catalog, building governance automation, defining data contracts, or implementing fine-grained access control on data products. Triggers: "MDM strategy", "consolidation vs registry vs centralized vs coexistence", "data contract", "data catalog", "knowledge graph for metadata", "ABAC for data", "semantic layer for governance", "metalake". Produces a chosen MDM style + governance architecture with policy automation.

Repository SourceNeeds Review

-1AlexYedi