What it does
The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows.
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category 自动化与智能体
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/vidispine-hull)相似的 Skill
同类工作,排序与 Skill 列表相同
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
安装
Is it safe?
- Who made it
GitHub account vidispine (organization), 9 years old
- Use and upkeep
★ 295 stars, few users so far · code last changed 2026年11月2日
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit eb6dc02 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (417). Use "Let the AI install it" instead
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /hull,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自己放入文件夹
把 hull 文件夹放到 ~/.agents/skills/hull
~ 是你的主文件夹($HOME)
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 hull
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
在 Cursor 的 Agent 聊天中输入 / 并选择 hull
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
5,484 个字符 · 在 GitHub 打开完整文件
---
name: hull
description: Write, convert, check and fix Helm charts built with the HULL library (vidispine/hull), whose Kubernetes objects are defined as values under hull.objects instead of templates. Use when a chart depends on hull, when values contain hull.objects or _HT transformations, when a HULL rendering error ("HULL failed with error [CODE]") needs fixing, or when converting an existing Helm chart or Kubernetes manifests to HULL.
---
# Working with HULL charts
A HULL chart has a single template, `templates/hull.yaml`, and defines every Kubernetes object as data in `values.yaml` under `hull.objects.<type>.<key>`. The values are validated by the JSON schema of the chart's HULL dependency. Do not write Go templates for objects.
The rules below describe HULL 1.35.5, 1.36.2, 1.37.1 and later. Older versions lack some features, for example image digests and explicit selectors; `hull_docs` with the chart's directory as `chart_dir` returns the documentation of the chart's own HULL version.
## Workflow
Use the `hull` MCP tools when they are available:
1. Before writing values, read the rules once: `hull_docs` with topic `guide`. For common tasks start from a tested recipe: `hull_docs` with topic `cookbook`.
2. Look up what is allowed instead of guessing: `hull_schema` with a values path such as `hull.objects.deployment.web.pod.containers.main`, an object type or a definition name.
3. After every change run `hull_validate` on the chart and fix every reported problem. Each problem is one line: `HULL failed with error [CODE] (@Values.<path>) <message> Fix: <hint>`. For details about a code use `hull_docs` with the code as topic.
4. Inspect the result with `hull_render`, using `kind` and `name` to select objects.
5. To convert an existing chart, render it with `helm template <release> <chart> --namespace <ns>` and pass the output to `hull_import` with the same release name and namespace. It writes a HULL chart and verifies that it renders the same objects. Then refactor the verified values into idiomatic HULL in small steps and compare the rendering after each step.
Without the MCP tools, the same is available as scripts in the HULL chart, in `files/scripts` of the dependency (unpack it with `tar -xzf charts/hull-*.tgz -C /tmp`): `python3 hull_validate.py <chart>`, `python3 hull_import.py --chart <dir> --verify <manifests>`, and the documentation in `files/doc`, starting with `agents.md` and `cookbook.md`.
## Rules that differ from Kubernetes YAML
- The instance key is the name: `hull.objects.deployment.web` renders `<release>-<chart>-web`. `staticName: true` or `hull.config.general.noObjectNamePrefixes: true` keep the key unchanged.
- Write the fields of `spec` directly below the instance key, without `spec:`. Pod based objects take the pod spec in `pod`, CronJobs in `job.pod`. Pod labels and annotations go to `pod.labels` and `pod.annotations`.
- Named arrays are dictionaries keyed by name: `containers`, `initContainers`, `volumes`, `env`, `ports`. Never add `name:` to them. `volumeMounts`, `envFrom`, Ingress `rules`, `paths`, `tls` and `webhooks` are dictionaries with free keys. Elements render in key order, use an integer `order` property where order matters.
- Images: `image: {registry, repository, tag, digest}`; a non-empty digest replaces the tag. Quote tags like `"1.10"`.
- Selectors are generated from chart, release and key. A Service without `selector` selects the pods of the workload with the same key. An explicit `selector` keeps an existing selector; the pod labels must then match it.
- References to chart objects use the key and get the name prefix: configMap/secret/PVC volumes, env and envFrom refs, Ingress backends and TLS secrets, HPA targets. Add `staticName: true` next to a name that refers to an object outside the chart. `serviceAccountName`, `imagePullSecrets` and RoleBinding names are rendered as written; use `_HT^<key>` for the full name of a chart object.
- ConfigMap and Secret data: `data.<key>.inline` or `data.<key>.path`. Secret values are plain text, HULL encodes them. Add `noTemplating: true` to content containing `{{`.
- Defaults: `_HULL_OBJECT_TYPE_DEFAULT_` instances or elements, and named `sources`.
- The `default` ServiceAccount, Role and RoleBinding: since HULL 1.37 they only exist with `hull.config.general.createDefaultRbacTriplet: true`. Up to 1.36 they are rendered for every release and pods without `serviceAccountName` get the `default` ServiceAccount; set `enabled: false` on them to leave them out.
- Kinds without a HULL object type are `generic` objects with `apiVersion`, `kind` and their fields.
## Transformations
Strings starting with these prefixes are computed:
| Prefix | Result |
| ------ | ------ |
| `_HT*hull.config.specific.x` | the value at the path below `.Values` |
| `_HT**Release.Name` | the same from the root context |
| `_HT!{{ ... }}` | a Go template result; `(index . "$")` is the root context |
| `_HT?<condition>` | a boolean, for `enabled` |
| `_HT^<key>` | the full name of a chart object |
| `_HT&<key>` | the generated selector labels of a key |
Keep shared values in `hull.config.specific` and reference them with `_HT*`. Write lists and dictionaries returned by `_HT!` in flow style, with embedded references inside `{{ }}`: `_HT![ {{ _HT*hull.config.specific.host }} ]`. Transformations are not applied to single list elements: a transformation as first element replaces the whole list, later elements stay literal.
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 295
- 开发者
- vidispine
- 许可证
- Apache-2.0
- 最近代码更新
- 2026年11月2日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1
- 主题
- ai, dry, helm, helm-chart, helm-charts, helm-deployment, helm-interface, helm-plugin, helm-plugins, helm-wrapper, helm3, json-schema
- Repo
- vidispine/hull