data-quality-checker
Validate data quality in market analysis documents and blog articles before publication
Install / Use
npx skills add tradermonty/claude-trading-skills --skill data-quality-checkerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of data-quality-checker
data-quality-checker scores 87/100 on our quality scale, 640th of 1,155 Content & Media skills we index.
Its SKILL.md is 5.8 KB long, well organised into 17 sections with 5 code examples: a solid amount of guidance for an agent.
With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so data-quality-checker is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
data-quality-checker compared with similar skills
All 4 of these similar skills score higher than data-quality-checker; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| data-quality-checker (this skill)by tradermonty | 87 | 2.9k | 53d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install data-quality-checker?
- Run
npx skills add tradermonty/claude-trading-skills --skill data-quality-checker. The install tabs above show the steps for each supported agent. - Which AI agents does data-quality-checker work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is data-quality-checker safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is data-quality-checker still maintained?
- The repository was last updated about 2 months ago, so data-quality-checker is actively maintained.
Skill content
View source on GitHubname: data-quality-checker description: Validate data quality in market analysis documents and blog articles before publication. Use when checking for price scale inconsistencies (ETF vs futures), instrument notation errors, date/day-of-week mismatches, allocation total errors, and unit mismatches. Supports English and Japanese content. Advisory mode -- flags issues as warnings for human review, not as blockers.
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 classreferences/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:
- JSON report (
data_quality_YYYY-MM-DD_HHMMSS.json): Machine-readable list of findings with severity, category, message, line number, and context. - 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 scriptreferences/instrument_notation_standard.md-- Notation and price scale referencereferences/common_data_errors.md-- Common error patterns and prevention
Key Principles
-
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).
-
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.
-
Bilingual support: Handles both English and Japanese date formats, weekday names, and section headings. Full-width characters (%, 〜, en-dash) are normalized before processing.
-
Year inference: For dates without an explicit year, the checker infers the year using (in priority order): the
--as-ofoption, a YYYY pattern found in the document title/metadata, or the current year with a 6-month cross-year heuristic. -
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
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
