icedq-mapping-doc-rules

icedq-mapping-doc-rules is a skill for Claude Code from icedq-tools/mcp-server. It costs 169 tokens per session (7,226 once invoked), scanned A, original, Apache-2.0.

A mapping-document rule extractor for iceDQ that reads Excel, CSV, Word, dbt schema, JSON Schema, or written specifications. It converts source-to-target mappings and stated constraints into data-quality rules.

In plain words
What is it for?
Use it to generate validation, duplicate, checksum, reconciliation, and pushdown rules from data-mapping documents.
Why use it?
It avoids manually translating mapping sheets and documented requirements into separate validation checks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the icedq-mcp plugin — 5 skills, 1 MCP server shipped together

Good fit Use it to generate validation, duplicate, checksum, reconciliation, and pushdown rules from data-mapping documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/icedq-tools/mcp-server/icedq-mapping-doc-rules
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add icedq-tools/mcp-server --skill icedq-mapping-doc-rules
Clone the repo
git clone --depth 1 https://github.com/icedq-tools/mcp-server

Made for: Claude Code.

Or install icedq-mcp, the plugin that ships this one along with the rest of its 5 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for icedq-mapping-doc-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/icedq-tools/mcp-server/icedq-mapping-doc-rules.svg)](https://agentmods.dev/skills/icedq-tools/mcp-server/icedq-mapping-doc-rules)
Your own site
<a href="https://agentmods.dev/skills/icedq-tools/mcp-server/icedq-mapping-doc-rules"><img src="https://agentmods.dev/badge/skills/icedq-tools/mcp-server/icedq-mapping-doc-rules.svg" alt="Measured on agentmods" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,226 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00169 $0.07226
Opus 5 $0.00084 $0.03613
Sonnet 5 $0.00034 $0.01445
Haiku 4.5 $0.00017 $0.00723

Measured today against content hash 05fee0f3cd38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

icedq-mapping-doc-rules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/icedq-mapping-doc-rules/SKILL.md · 442 lines

How it starts

The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GOAL

Extract ALL quality rules from a column mapping spec. ONE Validation rule per table (all checks combined). Rule types: Validation, Duplicate, Checksum, Recon, Pushdown.


STEP 0 — PARSE DOC

Format detection:

  • Excel/CSV/Word table: find header row; map labels to signal fields below. Ignore decorative title rows.
  • dbt schema.yml: not_null→Mandatory; unique→UniqueKey; accepted_values→ApprovedValues; relationships→FK Pushdown
  • JSON Schema: required→Mandatory; enum→ApprovedValues; maxLength→MaxLen; pattern→Format; $ref→FK Pushdown
  • Prose: scan for "Validations:", "Business Rules:", "Constraints:", "Data Requirements:" headings

Signal field aliases:

Signal Common column names
Source col Source Column, SRC Column, From Column, Source Field
Target col Target Column, TGT Column, DW Column, Destination
Mandatory Mandatory?, Required?, Nullable?, Not Null
Unique key Unique Key?, PK?, Business Key?, Natural Key?
Transform Transformation, Logic, Mapping Rule, ETL Logic
Approved values Approved Values, Domain, Valid Values, Lookup
Format Format, Pattern, Regex, Data Format
Min/Max Length Min Length, Max Length, Length
FK Cross-Table, FK Reference, References, Lookup Table
Business rule Business Rule, Acceptance Criteria, DQ Rule, Notes
Severity Severity, Priority, Criticality, Risk Level

YES synonyms: Y YES TRUE 1 Required NOT NULL Mandatory. NO synonyms: N NO FALSE 0 Optional NULL Nullable blank.

Missing columns — infer:

  • No Mandatory col → check target DDL for NOT NULL; scan Business Rule text for "must not be null"
  • No Unique Key → scan Business Rule for "must be unique"/"primary key"/"no duplicate"
  • No Approved Values → extract from Business Rule or Transform text
  • No Min/Max Length → infer from type: VARCHAR(N)→max=N; CHAR(N)→exact=N
  • No Format → extract regex/format strings from Business Rule text

Table metadata (above column rows): source schema.table + connection; target schema.table + connection; join key. No join key → ask user. If none: Validation + Duplicate + Checksum only (skip Recon).

Read the full file on GitHub · 442 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 442 lines · 169 tokens per session scan A 05fee0f3cd38

Subscribe to this mod's changes

icedq-mapping-doc-rules is a skill published in the GitHub repository icedq-tools/mcp-server (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 169 tokens to every session and 7,226 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.

Related

Other skills, from other repositories

spreadsheet-direct-verification

Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

HKUDS/OpenSpace · 36 tokens

spreadsheet-create-verify-gate

Create or edit Excel workbooks with openpyxl-specific pitfall handling, anchored preflight audit, and deterministic post-write proof that every criterion is satisfied.

HKUDS/OpenSpace · 38 tokens

spreadsheet-proof-gate-merged-fedf41-merged

The derived skill is complete and provides a meaningful enhancement.

HKUDS/OpenSpace · 12 tokens

define-data

Standalone Phase 4 of SAP UI testing. Authors one tests/ /test-cases/TC-XXX.data.md requirement spec per case marked dataRequired: yes — choosing the narrowest correct source (sql/static/generated/seeded), and generating upload fixtures in the EXACT file format the program parses (xlsx vs csv). Validates that every…

marcellourbani/vscode_abap_remote_fs · 0 tokens

xz-cases

A generator for acceptance-test checklists covering the core feature changes between specified software versions. It writes the checklist to an XLSX spreadsheet, a format used by Microsoft Excel and similar programs.

Xuzan9396/plugin_claude · 66 tokens

postman-test-implementation

Converts an approved company-format testcase workbook (from api-test-design + company-testcase-format) into one Postman collection and one Postman environment, using conventions learned from real company artifacts and this project's src/postman builders. Does not execute anything and does not decide what to test.

mdkulkarni2005/osmos-marketing-mcp · 63 tokens