CtrlK
BlogDocsLog inGet started
Tessl Logo

depot-container-builds

Configures and runs Depot remote container builds using `depot build` and `depot bake`. Use when building Docker images, creating Dockerfiles with Depot, pushing images to registries, building multi-platform/multi-arch images (linux/amd64, linux/arm64), debugging container build failures, optimizing Dockerfile layer caching, using docker-bake.hcl or docker-compose builds, or migrating from `docker build` / `docker buildx build` to Depot. Also use when the user mentions depot build, depot bake, container builds, image builds, or asks about Depot's build cache, build parallelism, or ephemeral registry.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient Depot build reference with excellent command coverage and tight organization. Its only gap is workflow clarity: multi-target/batch bake operations lack an explicit validation-checkpoint sequence.

Suggestions

Add a short numbered 'Build and verify' workflow for bake/multi-target builds with an explicit validate step (e.g., depot bake --print to confirm resolved targets before building, then verify pushed images) to lift workflow_clarity.

For destructive/batch paths like 'depot cache reset' and registry pushes, include an explicit confirmation or verification checkpoint in the sequence.

Consider moving the long flags table and builder-size table into a reference file to keep SKILL.md as a leaner overview, improving progressive_disclosure headroom.

DimensionReasoningScore

Conciseness

Lean, reference-style content with no explaining of concepts Claude already knows; nearly every line is an executable command, flag, or table entry that earns its place.

3 / 3

Actionability

Copy-paste-ready commands, complete HCL/YAML bake and compose examples, a full flag table, and concrete migration one-liners provide fully executable guidance.

3 / 3

Workflow Clarity

Steps are present and error-recovery is captured in the Common Mistakes table, but there is no explicit numbered validate->fix->retry checkpoint sequence, and bake/destructive batch operations lack explicit validation steps (capping this at 2).

2 / 3

Progressive Disclosure

A single-purpose reference skill with no external bundle files, but content is well-organized into clearly signaled sections, satisfying the simple-skill allowance for progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: specific actions, natural trigger terms, explicit what-and-when guidance, and a distinctive Depot niche. It earns full marks across all four dimensions with no padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (building Docker images, pushing to registries, multi-platform builds, debugging failures, optimizing layer caching, migrating from docker build/buildx) rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Configures and runs Depot remote container builds using depot build and depot bake') and when ('Use when... Also use when the user mentions...') with explicit trigger clauses.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say: 'depot build', 'depot bake', 'container builds', 'image builds', 'docker-bake.hcl', 'docker-compose', plus cache/parallelism/ephemeral registry.

3 / 3

Distinctiveness Conflict Risk

Clear Depot-specific niche anchored by 'depot' and docker-to-Depot migration triggers; the few generic terms ('container builds') are dominated by Depot-distinctive ones, making conflict unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.