CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-quality-checker

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable commands, clear five-step sequencing, and properly signaled one-level-deep references to real bundle files. The main improvements are trimming repeated advisory-mode statements and changelog-style phrasing, and moving the weekday-check edge-case detail into a reference file.

Suggestions

Move the 'Supported weekday checks' edge-case detail (range/parenthesis/year-inference rules) into references/common_data_errors.md or a dedicated reference, keeping only a one-line summary in SKILL.md.

State the advisory-mode and exit-code-0 behavior once (e.g., in Key Principles only) instead of three times across Overview, Key Principles, and the weekday section.

Add a brief error-recovery note for exit code 1 (e.g., verify the file path and re-run) to close the workflow's validation loop.

Delete changelog references to past behavior such as 'that previously produced WARNING' — they add tokens without helping a fresh reader.

DimensionReasoningScore

Conciseness

The body is largely efficient — no explanations of concepts Claude already knows, and commands/outputs are shown rather than described. Minor trimmable instances remain: the advisory-mode/exit-code-0 point is repeated in the Overview, Key Principles, and again at the end of the weekday section, and the phrase 'including Japanese forms that previously produced WARNING' is changelog-style padding irrelevant to a fresh reader. Not the 3 anchor because the redundancy is minor relative to the whole.

4 / 5

Actionability

Guidance is fully executable: three copy-paste-ready CLI invocations with flags documented ('--file', '--checks price_scale,dates,allocations', '--as-of 2026-02-28'), concrete JSON and markdown output examples, and severity-level handling instructions. This matches the 'copy-paste ready commands covering common cases' top anchor.

5 / 5

Workflow Clarity

The 5-step workflow (receive input → run script → load references → review findings → generate report) is clearly sequenced, and exit-code semantics (0 for advisory findings, 1 for script failures) are documented. It falls short of the 5 anchor because there is no explicit error-recovery loop for exit-code-1 failures (e.g., what to check and retry), though the read-only advisory nature of the skill makes this a minor gap rather than the missing-validation case the rubric caps at 3.

4 / 5

Progressive Disclosure

Bundle structure is sound: SKILL.md points one level deep to two real reference files, each introduced in Step 3 with a purpose description and re-listed under Resources, plus the script and its tests. The gap against the 5 anchor is the 'Supported weekday checks' section, which inlines ~17 lines of dense edge-case matching rules (tight ranges, mixed-width parentheses, year-inference precedence) that would fit better in a reference file than in the overview.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability list, explicit 'Use when...' trigger guidance with specific check categories, and a clearly differentiated niche. The only weakness is modest keyword coverage — a few natural synonyms a user might say (fact-check, financial report) are absent.

Suggestions

Add one or two natural user phrasings such as 'fact-check financial data' or 'pre-publication review of market reports' to broaden trigger term coverage.

Mention the document types explicitly handled (e.g., markdown reports, weekly strategy blogs) so trigger matching on file context is more reliable.

DimensionReasoningScore

Specificity

The description enumerates five concrete check categories — 'price scale inconsistencies (ETF vs futures), instrument notation errors, date/day-of-week mismatches, allocation total errors, and unit mismatches' — which is comprehensive, specific coverage of the skill's capabilities within its niche, matching the top anchor.

5 / 5

Completeness

It explicitly answers both 'what' ('Validate data quality in market analysis documents and blog articles before publication') and 'when' with a concrete trigger clause ('Use when checking for price scale inconsistencies (ETF vs futures), instrument notation errors, date/day-of-week mismatches...'), matching the top anchor's pattern of what + explicit 'Use when' with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms like 'market analysis documents', 'blog articles', 'ETF vs futures', 'allocation total', and 'before publication' give good keyword coverage, but a few natural user phrases are missing (e.g., 'fact-check', 'financial report', 'proofread', or specific file types). Not the comprehensive-with-synonyms level of the 5 anchor, but clearly above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — pre-publication data QA for financial market analysis with bilingual (English/Japanese) support and advisory mode — and the triggers (ETF vs futures scale confusion, allocation totals, weekday mismatches) are distinct enough that it would rarely fire for an unrelated skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/data-quality-checker/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.