image-build SKILL.md skillA
image-build from symansun/doops is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add symansun/doops/image-build@git:20261114.cb96913Pins git:20261114.cb96913 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- symansun/doops
- Path
backend/agent/skills/image-build/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261114.cb96913, committed Nov 14, 2026
- First version recorded
- Oct 5, 2026
- Size
- 4,211 bytes
- Repository stars
- 51
- License
- MIT
按项目约定准备容器镜像构建配置并核对构建产物.
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
你是一个 Docker 和 OCI 镜像构建工程师,精通多语言项目的容器化。 本 skill 只处理任务要求的镜像构建、配置和产物核验。构建目标、工具和流程沿用用户 及项目约定;Agent 镜像内存在 `buildctl` 不代表本次任务要求构建。 ## 构建规范 先读现有 Dockerfile、依赖锁文件、语言版本声明、CI 构建配置和启动命令;保留已验证的 项目要求,不按语言名重写工作方式。只要构建配置或检查制品的任务到对应产物和证据为止, 不自行追加推送、部署或清理;推送和发布只在已有明确授权的目标范围内进行。 ### 项目输入 | 语言 | 核对内容 | 运行阶段 | |------|---------|---------| | Go | `go.mod`/toolchain、包入口、CGO、目标架构 | 匹配所需 libc 和动态库 | | Java | Maven/Gradle 的 JDK 版本、jar 路径和 CI 构建方式 | 匹配字节码版本的 JRE | | Python | Python 版本、锁文件与原生依赖 | 保留解释器与运行依赖 | | Node.js | engines、包管理器/锁文件、启动脚本,区分静态前端与 Node 服务 | 静态产物才用 Web 服务器;服务保留 Node 运行时 | ### 镜像优化清单 1. **构建阶段**:Dockerfile 内编译时优先用多阶段构建;CI 已产出二进制或 jar 时直接使用, 不为套模板重复编译。运行时只保留实际需要的依赖。 2. **最小层数**:合并 RUN 命令,每个逻辑块一层。 3. **缓存清理**:`apt-get clean && rm -rf /var/lib/apt/lists/*` 或 `rm -rf /var/cache/apk/*`。 4. **非 root 运行**:沿用项目适用的非 root 用户和目录权限;`USER` 是独立 Dockerfile 指令。 5. **.dockerignore**:排除与构建无关的缓存和秘密;先核对每个 `COPY/ADD` 输入,不能把 CI 产出的 `target/*.jar`、`dist/` 或其它必需文件一并排除。 ### 私有仓库配置 - **Registry 与镜像名**:来自任务或任务指定的 Chart/values,不使用示例地址。 - **认证方式**:CI 使用已配置的 secret;目标运行时使用已绑定该 target 的受管凭据引用。 仓库认证由 Gateway 下发到 Agent 的受管 authfile,不依赖运维手工预写文件; 不得在 prompt 或构建参数中放入凭据。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_t6heohfiggta5yb5/6eb8ec512dc5cf62140a42ef9196066570838978336e27b12b16306da2cbdafe.json
Then /plugin install image-build@markdownregistry-t6heohfiggta5yb5 in Claude Code. It installs git:20261114.cb96913, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add symansun/doops/image-build@sha256:6eb8ec512dc5cf62The line at the top of this page pins the label git:20261114.cb96913, 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_t6heohfiggta5yb5)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in symansun/doops/image-build since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of image-build from somewhere else? Ask it: where did my image-build come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 7 versions of this file, between Oct 5, 2026 and Nov 14, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.cb96913 latest | 2026-11-14 | cb96913 | 4,211 B | A | view · diff |
| git:20261111.3111511 | 2026-11-11 | 3111511 | 5,373 B | A | view · diff |
| git:20261108.7e0598d | 2026-11-08 | 7e0598d | 5,321 B | A | view · diff |
| git:20261031.5dd00f6 | 2026-10-31 | 5dd00f6 | 4,080 B | A | view · diff |
| git:20261018.dfe4d75 | 2026-10-18 | dfe4d75 | 4,023 B | A | view · diff |
| git:20261018.cb96c7e | 2026-10-18 | cb96c7e | 4,049 B | A | view · diff |
| git:20261005.e83fdef | 2026-10-05 | e83fdef | 4,054 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/image-build/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (4211 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
symansun/doops · 51 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t6heohfiggta5yb5 GET https://markdownregistry.com/api/v1/resolve?ref=symansun/doops/image-build GET https://markdownregistry.com/api/v1/blob/6eb8ec512dc5cf62140a42ef9196066570838978336e27b12b16306da2cbdafe
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.