This skill gives Claude direct access to your Tilt development environment through the CLI. It knows to check errors first (using jq to surface the actual buildHistory error, not just status flags), query resource status with uiresources, tail logs, and manage deployments. The best part is it follows the zmx session pattern for running tilt up in a detached terminal and explicitly knows not to restart Tilt for code changes since live reload is the whole point. Useful when debugging why a service won't start or checking if your local Kubernetes stack is actually healthy. It handles non-default ports and includes the full status model so Claude doesn't confuse updateStatus with runtimeStatus.
- skills.sh installs
- 196
- GitHub stars
- 48
- last updated
- Jun 3, 2026
Install
$ npx -y skills add 0xbigboss/claude-code --skill tilt --agent claude-codeInstalls into .claude/skills of the current project.
Files
Tilt
First Action: Check for Errors
Before investigating issues or verifying deployments, check resource health. Run errors first, separately from pending/in-progress — otherwise real failures get buried in 20+ pending lines:
# 1. Errors only — surface the buildHistory[0].error so you see WHY, not just THAT
tilt get uiresources -o json | jq -r '.items[] | select(.status.runtimeStatus == "error" or .status.updateStatus == "error") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)\n reason: \((.status.buildHistory[0].error // "(no buildHistory error; check tilt logs)") | gsub("\n"; " ") | .[0:240])"'
# 2. In-progress and pending — informational; an in-progress build may flip to error any moment
tilt get uiresources -o json | jq -r '.items[] | select(.status.updateStatus == "in_progress" or .status.updateStatus == "pending" or .status.runtimeStatus == "pending") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)"'
Sponsors
Details
- Repository
- github.com/0xbigboss/claude-code
- First seen
- Jun 3, 2026
More from 0xbigboss/claude-code
All 22- Orbstack Best Practices180
- Canton Network Repos157
- Ios Device Screenshot155
- Atlas Best Practices154
- Git Best Practices149
- Git Rebase Sync146
- Testing Best Practices135
- E2e126
- Extract Transcripts122
- React Best Practices3K
- Typescript Best Practices2.9K
- Python Best Practices1.8K
- Web Fetch929
- Zig Best Practices388
- Nix Best Practices359
- Tamagui Best Practices290
- Openai Image Gen288
- Go Best Practices272
- Playwright Best Practices266
- Axe Ios Simulator239
- Electrobun Best Practices209
