tiltup

Start Tilt sessions and diagnose Tiltfile and resource bootstrap failures.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill tiltup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tiltup
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/tiltup
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill tiltup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, principled workflow to start Tilt, monitor bootstrap progress, and fix Tiltfile or manifest errors so local Kubernetes development converges to a healthy state without hidden workarounds.

Core Features & Use Cases

  • Automated session management: Start Tilt in a named zmx session (or use silo up for silo projects) and avoid duplicate sessions.
  • Bootstrap monitoring and convergence: Poll Tilt UI resources for runtime and update states, detect pending/error conditions, and determine when resources are healthy.
  • Config-first debugging: Inspect Tiltfile, manifests, and logs to root-cause config issues and apply fixes without adding brittle fallbacks or sleep loops.

Quick Start

Start a tilt session in zmx, monitor resource convergence, and iteratively fix any Tiltfile or manifest errors until all resources report runtime=ok and update=ok.

Frequently Asked Questions about tiltup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Tiltfile that fails to bootstrap my local Kubernetes development environment?

Debug Tiltfile bootstrap failures by inspecting Tilt UI resource states and logs to root-cause config issues, then iteratively applying manifest fixes until all resources report runtime=ok and update=ok.

How do I start a Tilt session for local Kubernetes development without creating duplicate sessions?

Start a Tilt session using named zmx sessions or silo up for silo-managed projects to enable automated session management and avoid duplicate processes during local Kubernetes bootstrapping.

What is the best way to monitor Tilt resource convergence during a local cluster bootstrap?

Monitor Tilt resource convergence by periodically polling the Tilt UI to detect pending or error conditions, verifying when runtime and update states achieve a healthy converged state.

Why do my Kubernetes resources stay pending when bootstrapping Tilt, and how do I fix config errors?

Kubernetes resources stay pending due to Tiltfile or manifest errors; fix config errors by inspecting logs and applying iterative config fixes without introducing brittle fallbacks or sleep loops.

Can I use Tilt with silo-managed projects for automated bootstrapping and debugging?

Yes, use silo up for silo-managed projects to start automated Tilt sessions, monitor resource convergence, and diagnose bootstrap failures within your local Kubernetes development workflow.