icedq-api-testingDesigns iceDQ rules for testing a REST API — validating its own response (required fields, valid values, formats, status codes) or reconciling API data against a backend/database. Use when the customer wants to test, validate, or reconcile a REST API, e.g. "test our orders API", "validate the fields
icedq-author-rulesCreates iceDQ rules via the MCP server — the single creation path all iceDQ skills funnel through. Direct mode (user-facing): use when the customer already KNOWS the checks they want — they name COLUMNS or CHECK TYPES, not just a table and a goal — e.g. "check my customer table for nulls and duplica
icedq-compare-datasetsIntent playbook for comparing two datasets in iceDQ — one-time data-migration testing AND ongoing reconciliation; asks which when unclear. Migration framing: "I am moving data from SQL Server to Snowflake", "validate my data migration", "test the cutover before go-live". Reconciliation framing: "rec
icedq-etl-code-rulesUses ETL/transformation code provided by the user (SQL stored procedures, dbt, PySpark, Spark Scala, SSIS, Informatica, Airflow, and similar) to identify and design iceDQ rules — Validation, Duplicate, Checksum, Recon, Pushdown. Use whenever the user SHARES pipeline code and wants checks derived fro
icedq-mapping-doc-rulesUses a mapping document provided by the user (Excel, CSV, or Word source-to-target specification) to identify and design iceDQ rules — Validation, Duplicate, Checksum, Recon, Pushdown. Use whenever the user uploads or points to a mapping doc or ETL mapping sheet and wants checks derived from it, e.g
icedq-run-and-reportRuns existing iceDQ rules, workflows, or schedules through the iceDQ MCP server, waits for them to finish, and reports the results — including exception (failure) details — in plain language. Use whenever a customer wants to EXECUTE checks or SEE results, e.g. "run my customer validation rule", "run
icedq-schedule-and-monitorSets up, changes, and reviews recurring iceDQ schedules and run history through the iceDQ MCP server. Use whenever a customer wants to AUTOMATE checks or REVIEW past runs, e.g. "run my validation rules every morning at 6", "schedule the daily reconciliation", "set up a weekly data quality workflow",
icedq-suggest-checksGuided front door for data testing with iceDQ — advises customers who want to know WHAT to test or WHERE to start, then takes them from requirements to created rules. Use for: "I want to test my data", "what checks would you recommend for this table", "help me set up data quality checks for our ware