technicalpickles/colima
plugins/dev-tools/skills/colima/SKILL.md
Use when Docker commands fail with "Cannot connect to Docker daemon", when starting/stopping container environments on macOS, when managing Docker contexts or profiles, or when running incus (system containers / VMs with nested virtualization) on macOS - provides Colima lifecycle management, profile handling, SSH commands, and troubleshooting
$ install --global
skillsauthnpx skillsauth add technicalpickles/pickled-claude-plugins colimaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 28, 2026, 4:28 AM35.6s13 files scanned
SKILL.md
- name:
- colima
- description:
- Use when Docker commands fail with "Cannot connect to Docker daemon", when starting/stopping container environments on macOS, when managing Docker contexts or profiles, or when running incus (system containers / VMs with nested virtualization) on macOS - provides Colima lifecycle management, profile handling, SSH commands, and troubleshooting
Colima
Overview
Colima provides container and VM runtimes (Docker, Containerd, Incus) on macOS with minimal setup. It runs a Linux VM and exposes the chosen runtime to the host.
Use this skill when:
- Docker commands fail ("Cannot connect to Docker daemon")
- Starting/stopping container runtime on macOS
- Managing multiple Docker profiles/contexts
- Troubleshooting container environment issues
- Need SSH agent forwarding for Docker builds
- Running incus on macOS (system containers or VMs with nested virtualization)
Not for: Docker Compose or Kubernetes clusters.
Quick Reference
| Operation | Command |
|-----------|---------|
| Start | colima start or colima start <profile> |
| Start with SSH agent | colima start <profile> -s |
| Stop | colima stop or colima stop --force |
| Status | colima status -p <profile> |
| List profiles | colima list |
| SSH into VM | colima ssh or colima ssh -- <cmd> |
| SSH with chained commands | colima ssh -- bash -c "cmd1 && cmd2" |
| Get socket path | colima status -p <profile> --json \| jq -r .docker_socket |
Docker Context Basics
Colima creates Docker contexts per profile:
- Profile
default→ contextcolima - Profile
work→ contextcolima-work
# Switch context (global - affects all terminals)
docker context use colima-work
# Override per-session
export DOCKER_CONTEXT=colima-work
# Override per-command
docker --context colima-work ps
For details, see references/docker-contexts.md.
Common Issues
Docker daemon not connecting?
colima status- is it running?docker context list- right context selected?- See
references/troubleshooting.mdfor more
Need more VM resources?
colima stop && colima start --cpu 4 --memory 8
"Broken" status after restart?
colima stop --force && colima start
References
references/ssh-commands.md- SSH command syntax, chaining, escapingreferences/docker-contexts.md- Context switching, DOCKER_HOST, socket pathsreferences/profile-management.md- Creating, configuring, deleting profilesreferences/troubleshooting.md- Common issues and solutionsreferences/common-options.md- Flags, VM types, resource configurationreferences/incus-runtime.md- Running incus (containers + VMs with nested virt) on Apple Silicon
Upstream Documentation
Local copies of official Colima docs (from github.com/abiosoft/colima):
references/colima-upstream/README.md- Official README with features and usagereferences/colima-upstream/FAQ.md- Official FAQ and troubleshootingreferences/colima-upstream/INSTALL.md- Installation options
Related Skills
technicalpickles/plugins/writing-tools/skills/writing-for-scannability
tools
VerifiedTrustedCommunity
--- name: writing-for-scannability description: Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that
10SKILL.mdUpdated Jun 2, 2026
technicalpickles/actually-lsp-ignore
development
VerifiedTrustedCommunity
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp.json`. Persistent across sessions for this project only.
10SKILL.mdUpdated May 28, 2026
technicalpickles/actually-lsp-doctor
tools
VerifiedTrustedCommunity
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
10SKILL.mdUpdated May 28, 2026
technicalpickles/plugins/github-actions/skills/investigating-runs
tools
VerifiedTrustedCommunity
--- name: investigating-runs description: Use whenever the user mentions a GitHub Actions / GHA run, even casually — invoke this skill before reaching for raw `gh` commands, because the bundled `gha-snapshot` helper distills `gh run view --log-failed` (a firehose) into a readable block with per-job status, failed-step log tails, and annotations. Specific triggers (any one is enough): a `github.com/.../actions/runs/...` URL; the phrase "GitHub Actions" or "GHA"; the `gh run` CLI; a failing workfl
10SKILL.mdUpdated May 21, 2026