Docker Jfr Benchmark Loop
eclipse-rdf4j/rdf4j
Run a repeatable RDF4J performance loop against one JMH benchmark in Docker with Linux Java 26 and JFR CPU-time profiling.
A skill your agent uses when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime…
Install 706 Technologies Containers Docker
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 706-technologies-containers-docker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/706-technologies-containers-docker .claude/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .claude/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-dockerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 706-technologies-containers-docker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/706-technologies-containers-docker .agents/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .agents/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 706-technologies-containers-docker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/706-technologies-containers-docker .cursor/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .cursor/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/706-technologies-containers-docker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 706-technologies-containers-docker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/706-technologies-containers-docker .gemini/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .gemini/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 706-technologies-containers-dockerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/706-technologies-containers-docker .github/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .github/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 706-technologies-containers-docker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/706-technologies-containers-docker .opencode/skills/706-technologies-containers-docker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "706-technologies-containers-docker" agent skill from https://github.com/jabrena/plinth/tree/main/skills/706-technologies-containers-docker into .opencode/skills/706-technologies-containers-docker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "706-technologies-containers-docker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
706-technologies-containers-docker- GitHub stars
- 447
- Token cost
- ~1.4k tokens
- SKILL.md length
- 573 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime…
- You need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Calls mvn
- Multi-stage Maven builds
What it does
706 Technologies Containers Docker is an agent skill from jabrena/plinth. Use when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime distributions such as Alpaquita, JVM container ergonomics, non-root execution, image metadata, .dockerignore, reproducible builds, vulnerability scanning, SBOM awareness, and production-safe container defaults. This should trigger for requests such as Review Java Dockerfile; Improve Docker image security; Add jlink runtime to a Java…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/706-technologies-containers-docker.md`).
It sits in DevOps & Cloud, covering Containers. It works with Docker and Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- You need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design
- Multi-stage Maven builds
- Jlink custom runtimes
- Micro runtime distributions such as Alpaquita
Example prompts
- “/706-technologies-containers-docker”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
706 Technologies Containers Docker loads about 1.4k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 573 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 573 words, ~1,396 tokens.
Download SKILL.mdSave it as
.claude/skills/706-technologies-containers-docker/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 706-technologies-containers-docker
- description
- Use when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime distributions such as Alpaquita, JVM container ergonomics, non-root execution, image metadata, .dockerignore, reproducible builds, vulnerability scanning, SBOM awareness, and production-safe container defaults. This should trigger for requests such as Review Java Dockerfile; Improve Docker image security; Add jlink runtime to a Java container; Add containerization to a Java project; Optimize Java container image size; Review Docker build reproducibility. Part of Plinth Toolkit
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
Java container image best practices with Docker
Help teams build secure, reproducible, and maintainable Docker container images for Java applications without coupling the guidance to Spring Boot, Quarkus, or Micronaut.
What is covered in this Skill?
- Dockerfile structure for Java applications: multi-stage builds, Maven dependency caching, deterministic artifact copies,
jlinkcustom runtimes, and.dockerignore - Runtime image selection: micro distributions such as Alpaquita, minimal JRE images, pinned versions or digests where appropriate, image labels, and explicit entrypoints
- JVM container ergonomics: memory percentage flags, startup behavior, graceful shutdown signals, time zones, and predictable runtime options
- Security defaults: non-root users, least privilege, no secrets in layers, reduced package managers, vulnerability scanning, SBOM awareness, and avoiding privileged containers
- Operational readiness: health checks when suitable, stdout/stderr logging, port declaration, image size control, build reproducibility, and CI verification
Scope: Framework-agnostic Docker and container-image quality for Java projects. For framework runtime wiring, defer to the matching Spring Boot, Quarkus, or Micronaut skill. For Testcontainers-based tests, defer to the relevant testing skill.
Constraints
Keep recommendations at the Dockerfile, image-build, and runtime-container layer unless the user explicitly asks for framework-specific configuration. After editing this repository's XML sources, regenerate skills and verify the build.
- MANDATORY: Run
./mvnw compileormvn compilebefore proposing Java or Maven changes in the same change set - SECRETS: Never bake credentials, tokens, private keys, Maven settings with secrets, or environment-specific secrets into image layers, labels, arguments, or logs
- SECURITY: Prefer non-root execution, least-privilege filesystem permissions, micro runtime images, and explicit container capabilities over privileged defaults
- JLINK: Prefer
jlinkcustom runtimes for production images when the module graph is known, validated at runtime, and compatible with the application's dependencies - REPRODUCIBILITY: Pin base image versions intentionally, document digest trade-offs, keep build inputs explicit, and avoid network-dependent runtime startup steps
- JVM: Account for container memory and CPU limits with JVM flags, graceful shutdown behavior, and observable startup failures before claiming production readiness
- BOUNDARIES: Defer Spring Boot runtime behavior to
@301-frameworks-spring-boot-core, Quarkus runtime behavior to@401-frameworks-quarkus-core, Micronaut runtime behavior to@501-frameworks-micronaut-core, and Testcontainers setup to the matching testing skill - VERIFY: Run
./mvnw clean verifyormvn clean verifybefore promoting changes - EDGE CASE: If the target Java version, build tool, deployment platform, base-image policy, registry policy, or security scanner is missing and affects the recommendation, ask a clarifying question before editing container artifacts
- EDGE CASE: If requested changes conflict with security policy, image provenance, air-gapped builds, or runtime platform constraints, explain the trade-off and ask for confirmation
Show full SKILL.md (165 more words)Show less
When to use this skill
- Review Java Dockerfile
- Improve Docker image security
- Add jlink runtime to a Java container
- Add containerization to a Java project
- Optimize Java container image size
- Review Docker build reproducibility
Workflow
- Read reference and assess container context
Read references/706-technologies-containers-docker.md and inspect current Dockerfiles, .dockerignore, Maven build inputs, image build scripts, CI jobs, registry policy, and deployment constraints before proposing changes.
- Identify runtime and supply-chain constraints
Confirm Java version, build tool, jlink module requirements, micro distro compatibility, target platform, base-image policy, registry requirements, vulnerability scanner, SBOM expectations, memory limits, exposed ports, and operational readiness needs.
- Apply container-aligned changes
Implement or refactor Docker and container build artifacts following the reference patterns and project conventions, keeping framework-specific runtime behavior out of scope unless explicitly requested.
- Run verification and report results
Execute appropriate build, image build, scan, smoke-test, and generator checks; summarize what changed, what was verified, and any remaining container risks.
Reference
For detailed guidance, examples, and constraints, see references/706-technologies-containers-docker.md.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/706-technologies-containers-docker of jabrena/plinth.
- SKILL.md
- references/706-technologies-containers-docker.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
706 Technologies Containers Docker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 706 Technologies Containers Docker this skilljabrena/plinth | 447 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Docker Jfr Benchmark Loopeclipse-rdf4j/rdf4j | 420 | — | ~945 | Automated safety check: Pass | BSD-3-Clause | |
| Opik Local Dev Environmentcomet-ml/opik | 22k | — | ~734 | Automated safety check: Pass | Apache-2.0 | |
| Oci Functions Deployoracle/skills | 877 | — | ~4.6k | Automated safety check: Pass | UPL-1.0 | |
| EelJetBrains/intellij-community | 21k | — | ~504 | Automated safety check: Pass | Custom licence | |
| Writing Dockerfilesancoleman/ai-design-components | 525 | — | ~3.2k | Automated safety check: Notes | MIT |
Similar skills
Opik Local Dev Environment
comet-ml/opik
Starts, rebuilds, and troubleshoots the Opik local dev stack, including an optional Comet Platform integration mode for the Opik team.
- Official
Oci Functions Deploy
oracle/skills
Build, configure, scaffold, and deploy OCI Functions from a local machine using a dependency-first, Fn-context-guided flow with argv-safe mutation execution, nonce-scoped confirmations, and a…
- Official
Eel
JetBrains/intellij-community
Use IntelliJ EEL APIs for process execution, paths, WSL, or Docker.
Writing Dockerfiles
ancoleman/ai-design-components
Writing optimized, secure, multi-stage Dockerfiles with language-specific patterns (Python, Node.js, Go, Rust), BuildKit features, and distroless images.
Containerization Assistant
ArabelaTso/Skills-4-SE
Generate Dockerfiles, Docker Compose configurations, and Kubernetes manifests for containerizing applications.
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Categories
Questions about 706 Technologies Containers Docker
What does 706 Technologies Containers Docker do?
A skill your agent uses when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime…. 706 Technologies Containers Docker is an agent skill from jabrena/plinth.dockerignore, reproducible builds, vulnerability scanning, SBOM awareness, and production-safe container defaults.
When should I use 706 Technologies Containers Docker?
706 Technologies Containers Docker fits situations like: you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design; multi-stage Maven builds; jlink custom runtimes; micro runtime distributions such as Alpaquita.
How do I install 706 Technologies Containers Docker in Claude Code?
Run `npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a claude-code`. Or copy the skill folder (skills/706-technologies-containers-docker in jabrena/plinth) into .claude/skills/706-technologies-containers-docker in your project. Claude Code loads it when a task matches its description.
How do I install 706 Technologies Containers Docker in Codex?
Run `npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a codex`. Or copy the skill folder (skills/706-technologies-containers-docker in jabrena/plinth) into .agents/skills/706-technologies-containers-docker in your project. Codex loads it when a task matches its description.
Can I use 706 Technologies Containers Docker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 706-technologies-containers-docker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/706-technologies-containers-docker, .gemini/skills/706-technologies-containers-docker, .github/skills/706-technologies-containers-docker and .opencode/skills/706-technologies-containers-docker in your project.
What does 706 Technologies Containers Docker need to run?
Going by SKILL.md and its folder, 706 Technologies Containers Docker needs the command-line tools its instructions call (mvn). Our summary lists: Docker.
Does 706 Technologies Containers Docker access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 706 Technologies Containers Docker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 706 Technologies Containers Docker use?
706 Technologies Containers Docker is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 706 Technologies Containers Docker use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to 706 Technologies Containers Docker?
Skills that share tags, products or a category with 706 Technologies Containers Docker: Docker Jfr Benchmark Loop (eclipse-rdf4j/rdf4j, 420 stars), Opik Local Dev Environment (comet-ml/opik, 22k stars), Oci Functions Deploy (oracle/skills, 877 stars) and Eel (JetBrains/intellij-community, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 706 Technologies Containers Docker?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.