ericrisco/rsc-harness / skills/docker
docker
VerifiedUse when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is `deployment`), NOT k8s autoscaling (that is `scaling`), NOT app-level injection or secrets-in-code (that is `security-audit`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| evals/README.md | markdown | 788 B |
| evals/cases.yaml | config | 2.4 KB |
| references/base-images-and-stages.md | markdown | 3.9 KB |
| references/compose-recipes.md | markdown | 3.3 KB |
| scripts/verify.shexecutable | script | 5.2 KB |
evals/README.md
View on GitHub# Evals — docker
`cases.yaml` has two kinds of checks. `should_trigger` / `should_not_trigger` are routing cases:
they validate that this skill's `description` fires on real container/image/Compose phrasings
(including the size-symptom and Catalan/Spanish ones) and stays quiet for CI-deploy, k8s,
app-security, and PaaS-host prompts, each routing to a named sibling. The `capability` case is a
rubric-graded scenario: feed the naive single-stage root Dockerfile to the skill and grade the
output against `must_include` (multi-stage, cache mount, non-root, pinned base, `.dockerignore`,
exec-form CMD, healthcheck, compose watch, no ARG/ENV secrets, hadolint/trivy). Run these through
the repo's eval harness; routing cases are mechanical, the capability case is manual or LLM-graded.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |