toolkit — Claude Code skill: project docs site and installation
The toolkit Claude Code skill builds a project documentation site from the repository. It covers architecture, data lineage, code calls, quality checks, and runs.
MIT ★ 106 updated 2026-11-06
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
/plugin install data-engineering@data-with-baraaWhat toolkit does
The skill reads the repository and writes a script that builds an engineering documentation site. Its overview lists sources, layers, and recent runs; separate pages cover architecture, data lineage, the call graph, the data model, and check results.
The catalog describes tables and columns with samples, masking personal data in those samples. The output is a set of HTML files: index.html is the hub, with one page for each project tool. Pages make no network requests and gain no added libraries.
The builder can regenerate the site after every release, so pages are changed through the source or builder rather than by hand. For a large project, the skill asks how many agents can run, assigns one to each page, and has them check their work against the repository.
What it helps with
- build a documentation site from a repository
- map lineage between tables and columns
- show which code calls which functions
- summarize data quality check results
- document runs, durations, and outcomes
Example prompts for the agent
- Build a documentation site for this project from the whole repository.
- Rebuild the documentation site after the release and tell me where to open it.
- Add pages for table lineage, the call graph, and data quality results.
How to install toolkit
1Plugin marketplace
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills/plugin install data-engineering@data-with-baraaThis installs the whole data-engineering plugin with all its skills
2Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill toolkit -a claude-code3Manually: put the files in place
~/.claude/skills/toolkit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/toolkit/
1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill toolkit -a codex2Manually: put the files in place
.agents/skills/toolkit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill toolkit -a cursor2Manually: put the files in place
.cursor/skills/toolkit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install DataWithBaraa/claude-code-data-engineering-skills skills/toolkit2Manually: put the files in place
.github/skills/toolkit/SKILL.md1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill toolkit -a gemini-cli2Platform CLI
gemini skills install https://github.com/DataWithBaraa/claude-code-data-engineering-skills --path skills/toolkitManually: put the files in place
.devin/skills/toolkit/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about toolkit
How do I install toolkit in Claude Code?
Add the marketplace with /plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills, then install the skill with /plugin install data-engineering@data-with-baraa.
What does toolkit do?
It reads a project repository, creates a site builder, and generates HTML documentation covering areas such as architecture, data models, catalogs, and run results.
What does the generated site contain?
It has an index.html hub and a page for each project tool. Its sections cover architecture, lineage, call relationships, data quality, runs, and the data catalog.
Source text
SKILL.md · MIT
--- name: toolkit description: Use 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 1. Write a site builder: one script that reads the repo and writes the pages, so the site can be built again after every release. 2. Overview: the sources, the layers and the latest runs. 3. Architecture: drawn from what runs, not by hand. The high-level picture first, the detail below it. 4. Data lineage: every table, clickable, upstream and downstream. 5. Call graph: who calls what in the code, clickable. 6. Data model: the entities and their relationships, then the star schema with the keys. 7. Data quality: the checks and their results, day by day. 8. Runs: what ran, how long it took, and the result. 9. Data catalog: every table and column, with a sample and a description. Personal data is masked in the samples. 10. 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. 11. Build the site and say where to open it. ## Output One folder of HTML files, like [references/](references/): [index.html](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.
© Data With Baraa · MIT · DataWithBaraa/claude-code-data-engineering-skills