Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
tradermonty avatar

Data Quality Checker

  • 924 installs
  • 2.6k repo stars
  • Updated August 4, 2026
  • tradermonty/claude-trading-skills

data-quality-checker is an AI agent skill that automatically scans market analysis reports and financial blog posts for data inconsistencies before publishing for developers and analysts writing finance content.

About

data-quality-checker is a tradermonty/claude-trading-skills validation workflow for market analysis documents and blog articles before publication. It checks five categories: price scale consistency between ETFs and futures, instrument notation errors, date and day-of-week mismatches, allocation total errors, and unit mismatches. Findings run in advisory mode as warnings for human review rather than hard blockers. The skill supports English and Japanese content. Developers and financial writers reach for data-quality-checker when drafting macro or markets posts where a wrong ticker scale or weekday typo undermines credibility. Activate when validating drafts that mix futures, ETFs, allocation tables, and dated price references.

  • Validates five categories: price scale consistency, instrument notation, date/weekday accuracy, allocation totals, and u
  • Advisory mode that flags issues as warnings for human review rather than blocking publication
  • Supports both English and Japanese market analysis content
  • Works with documents combining data from FRED, FMP, and FINVIZ
  • Zero third-party dependencies, runs with only Python standard library

Data Quality Checker by the numbers

  • 924 all-time installs (skills.sh)
  • +84 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #149 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tradermonty/claude-trading-skills --skill data-quality-checker

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs924
repo stars2.6k
Last updatedAugust 4, 2026
Repositorytradermonty/claude-trading-skills

How do you catch data errors in market analysis posts?

Automatically scan market analysis reports and financial blog posts for data inconsistencies before publishing.

Who is it for?

Financial bloggers and analysts publishing English or Japanese market commentary who need automated consistency checks on figures and dates.

Skip if: Live trading execution, portfolio optimization, or code-centric unit test generation unrelated to published market writeups.

When should I use this skill?

The user validates a market analysis or financial blog draft for price scale, ticker notation, date, allocation, or unit errors.

What you get

Advisory warning report covering price scales, instrument notation, dates, allocation totals, and unit mismatches.

  • Advisory data quality warning report

By the numbers

  • Validates 5 data quality categories before publication

Files

SKILL.mdMarkdownGitHub ↗

Overview

Detect common data quality issues in market analysis documents before publication. The checker validates five categories: price scale consistency, instrument notation, date/weekday accuracy, allocation totals, and unit usage. All findings are advisory -- they flag potential issues for human review rather than blocking publication.

When to Use

  • Before publishing a weekly strategy blog or market analysis report
  • After generating automated market summaries
  • When reviewing translated documents (English/Japanese) for data accuracy
  • When combining data from multiple sources (FRED, FMP, FINVIZ) into one report
  • As a pre-flight check for any document containing financial data

Prerequisites

  • Python 3.9+
  • No external API keys required
  • No third-party Python packages required (uses only standard library)

Workflow

Step 1: Receive Input Document

Accept the target markdown file path and optional parameters:

  • --file: Path to the markdown document to validate (required)
  • --checks: Comma-separated list of checks to run (optional; default: all)
  • --as-of: Reference date for year inference in YYYY-MM-DD format (optional)
  • --output-dir: Directory for report output (optional; default: reports/)

Step 2: Execute Validation Script

Run the data quality checker script:

python3 skills/data-quality-checker/scripts/check_data_quality.py \
  --file path/to/document.md \
  --output-dir reports/

To run specific checks only:

python3 skills/data-quality-checker/scripts/check_data_quality.py \
  --file path/to/document.md \
  --checks price_scale,dates,allocations

To provide a reference date for year inference (useful for documents without explicit year in dates):

python3 skills/data-quality-checker/scripts/check_data_quality.py \
  --file path/to/document.md \
  --as-of 2026-02-28

Step 3: Load Reference Standards

Read the relevant reference documents to contextualize findings:

  • references/instrument_notation_standard.md -- Standard ticker notation,

digit-count hints, and naming conventions for each instrument class

  • references/common_data_errors.md -- Catalog of frequently observed errors

including FRED data delays, ETF/futures scale confusion, holiday oversights, allocation total pitfalls, and unit confusion patterns

Use these references to explain findings and suggest corrections.

Step 4: Review Findings

Examine each finding in the output:

  • ERROR -- High confidence issues (e.g., date-weekday mismatches verified

by calendar computation). Strongly recommend correction.

  • WARNING -- Likely issues that need human judgment (e.g., price scale

anomalies, notation inconsistencies, allocation sums off by more than 0.5%).

  • INFO -- Informational notes (e.g., mixed bp/% usage that may be

intentional).

Step 5: Generate Quality Report

The script produces two output files:

1. JSON report (data_quality_YYYY-MM-DD_HHMMSS.json): Machine-readable list of findings with severity, category, message, line number, and context. 2. Markdown report (data_quality_YYYY-MM-DD_HHMMSS.md): Human-readable report grouped by severity level.

Present the findings to the user with explanations referencing the knowledge base. Suggest specific corrections for each issue.

Output Format

JSON Finding Structure

{
  "severity": "WARNING",
  "category": "price_scale",
  "message": "GLD: $2,800 has 4 digits (expected 2-3 digits)",
  "line_number": 5,
  "context": "GLD: $2,800"
}

Markdown Report Structure

# Data Quality Report
**Source:** path/to/document.md
**Generated:** 2026-02-28 14:30:00
**Total findings:** 3

## ERROR (1)
- **[dates]** (line 12): Date-weekday mismatch: January 1, 2026 (Monday) -- actual weekday is Thursday

## WARNING (2)
- **[price_scale]** (line 5): GLD: $2,800 has 4 digits (expected 2-3 digits)
  > `GLD: $2,800`
- **[allocations]**: Allocation total: 110.0% (expected ~100%)

Resources

  • scripts/check_data_quality.py -- Main validation script
  • references/instrument_notation_standard.md -- Notation and price scale reference
  • references/common_data_errors.md -- Common error patterns and prevention

Key Principles

1. Advisory mode: All findings are warnings for human review. The script always exits with code 0 on successful execution, even when findings are present. Exit code 1 is reserved for script failures (file not found, parse errors).

2. Section-aware allocation checking: Only percentages within allocation sections (identified by headings like "配分", "Allocation", or table columns like "ウェイト", "目安比率") are checked. Random percentages in body text (probability, RSI, YoY growth) are ignored.

3. Bilingual support: Handles both English and Japanese date formats, weekday names, and section headings. Full-width characters (%, 〜, en-dash) are normalized before processing.

4. Year inference: For dates without an explicit year, the checker infers the year using (in priority order): the --as-of option, a YYYY pattern found in the document title/metadata, or the current year with a 6-month cross-year heuristic.

5. Digit-count heuristic: Price scale validation uses digit counts (number of digits before the decimal point) rather than absolute price ranges. This approach is resilient to price changes over time while still catching ETF/futures confusion errors.

Related skills

FAQ

What does data-quality-checker validate in market documents?

data-quality-checker validates five categories in tradermonty/claude-trading-skills: price scale consistency, instrument notation, date/weekday accuracy, allocation totals, and unit usage. All findings are advisory warnings for human review.

Does data-quality-checker support Japanese financial content?

data-quality-checker supports both English and Japanese market analysis documents and blog articles. The skill readme specifies bilingual validation before publication in advisory mode.

Code Review & Qualityautomationresearch

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.