skills/github-docker-action/SKILL.md
Create Docker container actions for GitHub Actions with Dockerfile, action.yml metadata, and entrypoint scripts. Use when building custom GitHub Actions with Docker, scaffolding container-based actions, or debugging Docker action workflows.
npx skillsauth add kjanat/skills github-docker-actionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build, package, and test custom GitHub Actions using Docker containers.
Not what you need? For running sidecar services (Redis, PostgreSQL, etc.) in CI workflows, see the
github-service-containersskill.
Security: Always treat workflow inputs as untrusted. Avoid script injection via
${{ }}inrun:blocks.
my-action/
├── Dockerfile
├── action.yml
├── entrypoint.sh
└── README.md
See dockerfile-patterns.md
Minimal:
FROM alpine:3.21
COPY entrypoint.sh /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]
See action-metadata.md
Declare inputs, outputs, and Docker configuration in action.yml.
See entrypoint-scripts.md
Script receives inputs as positional args. Write outputs to $GITHUB_OUTPUT.
git add entrypoint.sh
git update-index --chmod=+x entrypoint.sh
Verify: git ls-files --stage entrypoint.sh should show 100755.
git add action.yml entrypoint.sh Dockerfile README.md
git commit -m "Initial action release"
git tag -a -m "v1 release" v1
git push --follow-tags
See workflow-testing.md
| Component | Purpose |
| --------------- | ----------------------------------------- |
| Dockerfile | Container image definition |
| action.yml | Action metadata (inputs, outputs, runner) |
| entrypoint.sh | Code executed when container starts |
| README.md | Usage docs for action consumers |
| Variable | Description |
| ------------------- | ------------------------------------------------------------ |
| $GITHUB_OUTPUT | File to write output key=value pairs |
| $GITHUB_WORKSPACE | Repo checkout dir (maps to /github/workspace in container) |
| $GITHUB_ENV | File to set env vars for later steps |
The runner maps GITHUB_WORKSPACE to /github/workspace in the container.
Files written there are available to subsequent workflow steps.
| Task | Files to Read | | ------------------------ | ---------------------------------------------- | | Scaffold new action | SKILL.md (this file) | | Dockerfile questions | dockerfile-patterns.md | | Configure inputs/outputs | action-metadata.md | | Write entrypoint logic | entrypoint-scripts.md | | Test in workflow | workflow-testing.md | | Debug container issues | dockerfile-patterns.md + entrypoint-scripts.md |
| File | Purpose | | ----------------------------------------------------------- | -------------------------------- | | dockerfile-patterns.md | Dockerfile templates and gotchas | | action-metadata.md | action.yml spec and examples | | entrypoint-scripts.md | Entrypoint, outputs, permissions | | workflow-testing.md | Workflow YAML for public/private |
development
Use this skill whenever the user is designing, building, scaffolding, reviewing, or debugging Go-based reverse proxy or HTTP edge infrastructure, especially when they mention statute, config-as-code proxies, building an nginx replacement in Go, networking topology, TLS termination, load balancing, HTTP/2, HTTP/3, QUIC, ACME, upstream pools, middleware chains, or graceful shutdown. Trigger this skill even when the user does not explicitly name statute but is clearly working on a Go HTTP server, edge proxy, or networking infrastructure problem where the resulting artefact will be a compiled binary rather than a runtime-configured server. Also trigger when the user asks for explanations of networking protocols (HTTP/1.1, HTTP/2, HTTP/3, WebSockets, gRPC, TLS) in the context of building or operating a proxy, or when they ask about Go net/http pitfalls, transport tuning, or production-grade server defaults.
development
Routes Threlte questions to exact, commit-pinned docs paths and practical workflows. Use when helping with setup, debugging, or architecture across @threlte/core, @threlte/extras, @threlte/gltf, @threlte/rapier, @threlte/theatre, @threlte/xr, @threlte/flex, and @threlte/studio.
testing
Comprehensive lightning physics knowledge base derived from Rakov & Uman (2003) "Lightning: Physics and Effects". Covers discharge types, current parameters, leader/return-stroke physics, cloud electrification, protection, detection systems, atmospheric effects, and quantitative reference data. Use when answering questions about lightning physics, electromagnetic fields, thunderstorm electricity, lightning protection, or atmospheric electrical phenomena.
development
Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.