pipeline-design-doc SKILL.md skillA
pipeline-design-doc from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/pipeline-design-doc@git:20260303.8412b01Pins git:20260303.8412b01 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/data-engineer/pipeline-design-doc/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.8412b01, committed Mar 3, 2026
- Size
- 5,418 bytes
- Repository stars
- 21
- License
- MIT
Write a data pipeline design document. Use when the user says "pipeline design doc", "document this pipeline", "pipeline architecture doc", "data flow document", "how does this pipeline work", "design doc for ETL", "pipeline spec", or needs to capture the architecture, data flow, and operational details of a data pipeline - even if they don't explicitly say "design doc".
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
## Overview Based on **Fundamentals of Data Engineering** (Reis & Housley) and **Designing Data-Intensive Applications** (Kleppmann). A pipeline design doc is the architectural contract for a data flow: what data moves, from where to where, how it transforms, and what guarantees it provides. Kleppmann's standard: document the data system's reliability, scalability, and maintainability properties - not just the happy path. The test: can a new engineer understand what this pipeline does, debug it when it breaks, and extend it safely - without asking anyone? ## Workflow ### Step 1: Write the pipeline overview ``` Pipeline: [name] Owner: [team or person] Purpose: [1-2 sentences on why this pipeline exists and what decision it enables] Source systems: [list of upstream data sources] Destination: [where data lands - warehouse, lake, API, etc.] Schedule: [batch frequency or streaming latency SLA] Data volume: [approx rows/day or GB/day] SLA: [when downstream consumers need data available by] ``` ### Step 2: Document the data flow Draw or describe each stage linearly: ``` [Source] → [Ingest] → [Raw/Landing Zone] → [Transform] → [Serving Layer] → [Consumer] ``` …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/pipeline-design-doc@sha256:4a182f90aeaf740dThe line at the top of this page pins the label git:20260303.8412b01, 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_yk77dfaqmpi4fpjp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 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 (5418 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
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yk77dfaqmpi4fpjp GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/pipeline-design-doc GET https://markdownregistry.com/api/v1/blob/4a182f90aeaf740dc27ecfd9213d6292201d378a8d85be05f431cd4b0e2548b2
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.