Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook and the guides match the code.
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
# Docs
The job: the runbook and the how-to guides, matching the code every time. It writes the docs, never the code. The standards and the source pages are checked by the knowledge-refresh skill, and the incident log gets its entries from the incident skill.
Input: none, or the change to document.
## Steps
1. List what changed since the docs were last written: the diff, the new files, the renamed things.
2. The runbook: every command, in order, as it runs today. Check that each command exists and that its flags parse, with --help or a dry run. Never run a command that writes data or starts a job.
3. The how-to guides: one per repeated task of the project, the steps as a new colleague would follow them.
4. Check every guide against the code: every path exists, every name is the name in the code.
5. Link the facts instead of copying them. A source, a business term or a rule links to its page in the knowledge, and a repeated passage becomes a link.
6. Report what was out of date and what is now written.
## Output
The runbook and the how-to guides as Markdown files in the docs folder, every command and every path checked against the code.
## Reads
…
The line at the top of this page pins the label git:20261029.2e2b6c2, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_ffexxki3f5vsticg
GET https://markdownregistry.com/api/v1/resolve?ref=datawithbaraa/claude-code-data-engineering-skills/docs
GET https://markdownregistry.com/api/v1/blob/bb8f0436cc9487f0747a742e8cc5b2e24ec2355e3c50f2e94e8d739d6edec06d
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.
datawithbaraa/claude-code-data-engineering-skills · skills/big-review/SKILL.md · Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs…
datawithbaraa/claude-code-data-engineering-skills · skills/contract/SKILL.md · Use when a new source is connected or a source changes how it delivers, to write the data contract with the source…
datawithbaraa/claude-code-data-engineering-skills · skills/cost-review/SKILL.md · Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline…
datawithbaraa/claude-code-data-engineering-skills · skills/data-product/SKILL.md · Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product…
datawithbaraa/claude-code-data-engineering-skills · skills/impact/SKILL.md · Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it…
datawithbaraa/claude-code-data-engineering-skills · skills/incident/SKILL.md · Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two…
datawithbaraa/claude-code-data-engineering-skills · skills/knowledge-refresh/SKILL.md · Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the…
datawithbaraa/claude-code-data-engineering-skills · skills/metadata/SKILL.md · Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types…
datawithbaraa/claude-code-data-engineering-skills · skills/migration/SKILL.md · Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the…
datawithbaraa/claude-code-data-engineering-skills · skills/pr-review/SKILL.md · Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass…
datawithbaraa/claude-code-data-engineering-skills · skills/profile/SKILL.md · Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the…
tanstack/ai · .claude/skills/docs/SKILL.md · Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning…
tanstack/ai · .grok/skills/docs/SKILL.md · Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning…
tanstack/ai · .agents/skills/docs/SKILL.md · Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning…
sidiora-labs/hyperfide · plugins/docs/skills/docs/SKILL.md · Read, edit, or save documents in HYPERFIDE Docs vaults, including documents supplied through Docs mentions.
sidiora-labs/codify · plugins/docs/skills/docs/SKILL.md · Read, edit, or save documents in HYPERFIDE Docs vaults, including documents supplied through Docs mentions.
aiskillstore/marketplace · skills/0xsero/docs/SKILL.md · Research documentation, find examples, explain APIs and libraries - Use when you need to look up official…
jstanden/cerb · features/cerberusweb.core/assets/agent_filesystems/cerb-agents/skills/docs/SKILL.md · The mounted Cerb documentation -- what lives where, how to find a page without reading it, and when the docs are the…
