一键导入
ref-setup
Download AI reference materials (external source code for AI assistant reference). Offers individual or all references.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Download AI reference materials (external source code for AI assistant reference). Offers individual or all references.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reference and coding guide for DataHub integration in backend development. Use when implementing or debugging code that touches DataHub — entities (datasets, dashboards, charts), aspects (ownership, tags, domains, glossary terms, structured properties), lineage, assertions, URNs, ingestion/emission, GraphQL, REST, or the acryl-datahub Python SDK. Also answers data-modeling questions and helps choose native DataHub features vs custom extensions. Trigger this skill whenever a task involves DataHub metadata, lineage, ingestion, or any DataHub API surface, even without explicit mention of "API".
Drive the helm-charts/bin/ install/uninstall/build/health scripts for both dev and prod profiles — configure, install, reinstall, uninstall, health-check, and rebuild-the-API / rebuild-the-frontend. The dev profile installs umbrella chart + peripherals (nginx-ingress, DataHub, Langfuse, dummy data, dev-lock) and auto-seeds peripheral connection config via the admin API. The prod profile installs the umbrella chart only; operator wires peripherals via /api/v1/admin/peripherals/*.
Walk a single api-wired UC scenario through the browser UI manually: for each step in the source test file, print the UI gesture (page + action), ask you to perform it and report what you observed, then independently probe the backend (REST read-back, DB rows, DataHub aspects, k8s secrets) to confirm the side effect fired. The human-driven sibling of the automated `tests/e2e/` use-case group — same scenarios, with a human at the browser. Optional argument `scope` selects the case (free-form: "UC1", "UC1 Case 2", "passive kafka", filename fragment, etc.).
Bidirectional sync between DataSpoke specs and implementation. Accepts a preset scope (prauto, ai-scaffold, k8s-deploy, helm-charts, api, ref, backend, frontend, all) or a free-form description of an area (e.g., "recently developed backend ingestion secret resolution"). Audits the scope, reports the gaps, asks the user which direction to resolve each gap (spec→impl, impl→spec, or leave-as-flagged), then applies the chosen edits. Trigger when specs and code may have drifted apart and the user wants them reconciled.
Author timeless specification documents under spec/ (top-level or spec/feature/<FEATURE>.md) following the project hierarchy, naming conventions, and templates. Use when the user asks to write, design, or document a DataSpoke feature, component, or architectural decision as a reference spec. Do NOT use for implementation plans — those live in GitHub issues/PRs and are produced by native Plan mode or PRauto.
Connect this plugin to a deployed DataSpoke and verify access. Use to point Claude at a DataSpoke deployment (API base URL + dsk_ API token), mint a token from email/password, or check who you are and what role you hold. Prerequisite for every other dataspoke-* skill — run this first, or when calls start returning 401.
| name | ref-setup |
| description | Download AI reference materials (external source code for AI assistant reference). Offers individual or all references. |
| allowed-tools | Bash(bash ref/*), Bash(ls *), Bash(test *), Bash(tail *), Bash(sleep *), Read, AskUserQuestion |
Use AskUserQuestion with the following options:
| Option | Label | Description |
|---|---|---|
| 1 | all | Download all reference materials (default) |
| 2 | datahub | Download only DataHub source code |
| 3 | clean | Remove all downloaded content |
Map the selected option to a ref/setup.sh argument:
bash ref/setup.sh (no argument)bash ref/setup.sh datahubbash ref/setup.sh --cleanExecute the setup script in the background: bash ref/setup.sh <selected-option>
While the script runs, check the background task output every ~20 seconds:
tail -30 <output-file>) to report progress messages (cloning, cleanup steps, etc.).Continue until the background script exits with exit code 0.
When the script exits successfully:
ref/github/datahub/ref/github/datahub/):
metadata-models/ — Entity schemas (PDL/Avro)metadata-service/ — GMS backend (Java/Spring)datahub-web-react/ — Frontend (TypeScript/React)metadata-ingestion/ — Python SDK and ingestion frameworkdatahub-graphql-core/ — GraphQL API schemas