DataWithBaraa/claude-code-data-engineering-skills / skills/toolkit
toolkit
UnverifiedUse to build or rebuild the documentation site of the project from the repo, the architecture, the data lineage, the call graph, the data model, the data quality, the runs and the data catalog.
Toolkit
The job: the engineering toolkit of the project as a website, built from the repo, one page per tool. Rebuilt after every release.
Input: none, it reads the whole repo.
Steps
- Write a site builder: one script that reads the repo and writes the pages, so the site can be built again after every release.
- Overview: the sources, the layers and the latest runs.
- Architecture: drawn from what runs, not by hand. The high-level picture first, the detail below it.
- Data lineage: every table, clickable, upstream and downstream.
- Call graph: who calls what in the code, clickable.
- Data model: the entities and their relationships, then the star schema with the keys.
- Data quality: the checks and their results, day by day.
- Runs: what ran, how long it took, and the result.
- Data catalog: every table and column, with a sample and a description. Personal data is masked in the samples.
- When the project is big, ask how many agents may run, give one agent per page, and let every agent check its page against the repo.
- Build the site and say where to open it.
Output
One folder of HTML files, like references/: index.html as the hub and one page per tool, nothing fetched from the network. Read them for the layout before you write the builder.
Reads
- the metadata, the pipeline code, the run records, the check results, the knowledge
Writes
- the site builder, and the pages it writes
Never
- Never edits a page by hand: fix the input or the builder, and build again.
- Never adds a library or a fetch from the network to a page.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 195k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |