data-provenance-mapping SKILL.md skillA
data-provenance-mapping from annatchijova/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add annatchijova/skills/data-provenance-mapping@git:20260825.0cef3f6Pins git:20260825.0cef3f6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- annatchijova/skills
- Path
data-provenance-mapping/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260825.0cef3f6, committed Aug 25, 2026
- Size
- 7,709 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
You cannot protect, delete, or report on data whose flow you have not mapped — a "delete my data" request, a breach-scope estimate, or a "we don't store PII" claim is only as true as your knowledge of where the data actually went, and it always went further than the schema says: into backups, logs, caches, analytics, data warehouses, search indexes, third-party processors, exports, and derived features. Use whenever the question is where sensitive data lives or goes…
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
# Data-Provenance Mapping Every strong statement about sensitive data — "we deleted it," "we don't retain that," "the breach was limited to these records," "it's anonymized" — is a claim about *where the data is*, and it is true only to the depth of your map. The recurring, expensive error is that data always travels further than the schema admits. The row you deleted was copied into last night's backup, logged in full by a debug statement, cached at the edge, shipped to an analytics vendor, indexed for search, and distilled into a model's training set. **The PII you forgot is the breach; the copy you did not delete is the failed DSAR.** Two failure modes, both from mapping intent instead of reality: - **Mapping the intended flow.** The architecture diagram shows the data going where you designed it to go. The actual flow includes the debug log that captured the whole request body, the one-off CSV a analyst exported to their laptop, the queue that retains messages for seven days, and the processor you integrated in 2021 and forgot. The diagram is a hypothesis; the flow is discovered. - **Treating a delete as an erasure.** "We deleted the row" reads as "the data is gone" …
Read the whole file at its exact version.
How to install
mdr add annatchijova/skills/data-provenance-mapping@sha256:a4d74a11b9b95644The line at the top of this page pins the label git:20260825.0cef3f6, 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_wq3n45nzf5iwd2gk)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 25, 2026.
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 (7709 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
annatchijova/skills · 9 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wq3n45nzf5iwd2gk GET https://markdownregistry.com/api/v1/resolve?ref=annatchijova/skills/data-provenance-mapping GET https://markdownregistry.com/api/v1/blob/a4d74a11b9b956444e659207292d5d089e8decddc95d386d78cce91b8c50f72e
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.