tilt
Before investigating issues or verifying deployments, check resource health:
Works with
0
total installs
0
this week
43
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
43
stars
Installation Guide
How to use tilt on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
tilt
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches tilt from 0xbigboss/claude-code and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tilt. Access via /tilt in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Tilt
First Action: Check for Errors
Before investigating issues or verifying deployments, check resource health:
# Find errors and pending resources (primary health check)
tilt get uiresources -o json | jq -r '.items[] | select(.status.runtimeStatus == "error" or .status.updateStatus == "error" or .status.updateStatus == "pending") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)"'
# Quick status overview
tilt get uiresources -o json | jq '[.items[].status.updateStatus] | group_by(.) | map({status: .[0], count: length})'
Non-Default Ports
When Tilt runs on a non-default port, add --port:
tilt get uiresources --port 37035
tilt logs <resource> --port 37035
Resource Status
# All resources with status
tilt get uiresources -o json | jq '.items[] | {name: .metadata.name, runtime: .status.runtimeStatus, update: .status.updateStatus}'
# Single resource detail
tilt get uiresource/<name> -o json
# Wait for ready
tilt wait --for=condition=Ready uiresource/<name> --timeout=120s
Status values:
- RuntimeStatus:
ok,error,pending,none,not_applicable - UpdateStatus:
ok,error,pending,in_progress,none,not_applicable
Logs
tilt logs <resource>
tilt logs <resource> --since 5m
tilt logs <resource> --tail 100
tilt logs --json # JSON Lines output
Trigger and Lifecycle
tilt trigger <resource> # Force update
tilt up # Start
tilt down # Stop and clean up
Running tilt up
Follow zmx skill patterns — check for existing sessions, derive name from git root, use zmx run (not attach):
PROJECT=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" || basename "$PWD")
SESSION="${PROJECT}-tilt"
if zmx list --short 2>/dev/null | grep -q "^${SESSION}$"; then
echo "Tilt session already exists: $SESSION"
else
zmx run "$SESSION" 'tilt up'
echo "Started tilt in zmx session: $SESSION"
fi
Critical: Never Restart for Code Changes
Tilt live-reloads automatically. Never suggest restarting tilt up for:
- Tiltfile edits
- Source code changes
- Kubernetes manifest updates
Restart only for: Tilt version upgrades, port/host changes, crashes, cluster context switches.
References
- TILTFILE_API.md - Tiltfile authoring
- CLI_REFERENCE.md - Complete CLI with JSON patterns
- https://docs.tilt.dev/
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
359mattpocock/skills
premortem
196parcadei/continuous-claude-v3
deslop
113cursor/plugins
framer-motion
96pproenca/dot-skills
write-a-prd
88mattpocock/skills
travel-planner
85ailabs-393/ai-labs-claude-skills
Reviews
- CChaitanya Patil★★★★★Dec 28, 2024
tilt reduced setup friction for our internal harness; good balance of opinion and flexibility.
- MMaya Liu★★★★★Dec 24, 2024
Keeps context tight: tilt is the kind of skill you can hand to a new teammate without a long onboarding doc.
- OOlivia Nasser★★★★★Dec 16, 2024
tilt has been reliable in day-to-day use. Documentation quality is above average for community skills.
- OOlivia Haddad★★★★★Dec 8, 2024
We added tilt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- MMia Gonzalez★★★★★Nov 27, 2024
Solid pick for teams standardizing on skills: tilt is focused, and the summary matches what you get after install.
- PPiyush G★★★★★Nov 15, 2024
I recommend tilt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- OOlivia Ndlovu★★★★★Nov 7, 2024
tilt fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- VValentina Park★★★★★Oct 26, 2024
We added tilt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- MMia Martinez★★★★★Oct 18, 2024
tilt has been reliable in day-to-day use. Documentation quality is above average for community skills.
- SShikha Mishra★★★★★Oct 6, 2024
Useful defaults in tilt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 36
Discussion
Comments — not star reviews- No comments yet — start the thread.