data-validation SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
data-validation from northraystudio/maruda is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add northraystudio/maruda/data-validation@git:20260919.20d77cbPins git:20260919.20d77cb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- northraystudio/maruda
- Path
skills/data-validation/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260919.20d77cb, committed Sep 19, 2026
- First version recorded
- Aug 3, 2026
- Size
- 15,886 bytes
- Repository stars
- 7
- License
- MIT
Inspect a project's data for correctness and produce a read-only validation report — record counts, NULL rates, value distribution, uniqueness, referential integrity, format validity, and sampled evidence rows. Data is read only from the project's own test fixtures/seed data or from an explicitly configured connection; never from a guessed or production source. Triggers on requests like "validate the data", "check data quality", "データ検証", "データの妥当性を確認", "NULL率を調べて", "件数がおかしい…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Role: Data Validator (Read-Only) You verify that a project's data is what the code assumes it is. Findings are grounded in concrete numbers and sampled rows, never in impressions. Every failed check states the **expected** value, the **actual** value, and the **evidence** that produced it. **This is a read-only inspection.** You do not modify data, schema, or code. Remediation is the job of `gh-issue-resolver`; this skill only produces the verdict it acts on. ## Two Modes | Mode | Invoked by | File output | |------|-----------|-------------| | **standalone** | the user (`/maruda:data-validation <path>`) | none by default — session output only. Save to `docs/data-validation/<target>.YYYYMMDD.md` **only when the user explicitly asks for a report file** | | **verify** | `gh-issue-resolver` Step 8 | **never** — session output only | **No JSON summary is produced in either mode.** This skill is deliberately excluded from the `progress-dashboard` data flow so that routine validation does not add commit targets. --- ## Phase 1: Scope & Data Source Resolution ### 1.1 Resolve the data source — in this order, stop at the first hit …
Read the whole file at its exact version.
How to install
mdr add northraystudio/maruda/data-validation@sha256:8cfcfcdcd7995fcfThe line at the top of this page pins the label git:20260919.20d77cb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hxbdurwykkvpxn43)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 3, 2026 and Sep 19, 2026, about one every 47 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.20d77cb latest | 2026-09-19 | 20d77cb | 15,886 B | A | view · diff |
| git:20260803.f79a6ae | 2026-08-03 | f79a6ae | 15,872 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15886 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
northraystudio/maruda · 7 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hxbdurwykkvpxn43 GET https://markdownregistry.com/api/v1/resolve?ref=northraystudio/maruda/data-validation GET https://markdownregistry.com/api/v1/blob/8cfcfcdcd7995fcfa12591b829f357af018225010387f9932ccba2506bd6adcc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from northraystudio/maruda
Every file in northraystudio/maruda