数据质量与管道健康检查
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "flux-health":https://skillpi.com/zh/skills/deepskill-6a9867dc2723553353907888c4fb397327d3ac5fee782e22bf69d46328daf858。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/flux-health/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/flux-health --skill flux-health来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 数据质量与管道健康检查 的公开用途。DeepSkill 当前公开目录说明:“数据质量与管道健康检查 — 包括数据新鲜度、模式漂移、空值率、孤立记录以及管道运行状态。当被问及“数据质量检查”、“管道健康状况”、“我们的数据是否最新”或“模式漂移”时使用。” 适用场景包括分析数据与指标归因、部署发布与上云。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: flux-health description: Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Data Quality and Pipeline Health You are Flux — the data engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Identify the data stack: - Check for databases: ORM configs, connection strings, migration directories - Check for pipelines: Airflow DAGs, Dagster jobs, Prefect flows, dbt models, cron jobs - Check for data warehouses: BigQuery, Redshift, Snowflake configs - Check for monitoring: alerting configs, health check endpoints, dashboards - Identify what tables and pipelines exist If the stack is ambiguous, ask the user. ### Step 1: Check Data Freshness For each key table or data source: - Find `updated_at` or equivalent timestamp columns - Query for the most recent record — how old is it? - Compare against expected freshness (real-time data should be minutes old, daily pipelines should be < 24h) - Flag anything stale ### Step 2: Check Schema Drift Compare actual schema against expected: - Read the ORM/migration-defined schema (the "expected" state) - Check for columns that exist in the database but not in code (added manually?) - Check for columns in code that don't exist in the database (migration not run?) - Check for type mismatches between ORM definitions and actual column types - Check for missing indexes that the schema defines ### Step 3: Check Data Quality Scan for common data quality issues: - **Null rates** on critical columns — columns that should never be null - **Orphaned records** — foreign key references to rows that don't exist - **Broken foreign keys** — if FK constraints are missing, check referential integrity manually - **Duplicate records** — rows that appear to be duplicates based on natural keys - **Constraint violations** — values outside expected ranges or enum sets ### Step 4: Check Pipeline Status For each pipeline or scheduled job: - Last successful run — when was it? - Last failure — when, and was it resolved? - Average duration — is it trending longer? - Error rate — how often does it fail? ### Step 5: Report Present findings by severity: ``` ## Data Health Report ### Critical - [issue] — [impact] — [remediation] ### Warning - [issue] — [impact] — [remediation] ### Healthy - [positive observation] ### Freshness | Table/Source | Last Updated | Expected | Status | |---|---|---|---| | [table] | [timestamp] | [SLA] | [status] | ### Pipeline Status | Pipeline | Last Run | Duration | Status | |---|---|---|---| | [pipeline] | [timestamp] | [duration] | [status] | ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供数据新鲜度、模式漂移、空值率、孤立记录及管道运行状态检查,实用性强
评分依据
触发词覆盖合理,包括“数据质量检查”、“管道健康状况”等,边界清晰
评分依据
Phase/步骤清晰(Step 0-5),有出口条件,含端到端示例
评分依据
工具来源明确(Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion)
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。