tiltup
Start Tilt dev environment in tmux, monitor bootstrap to healthy state, fix Tiltfile bugs without hard-coding or fallbacks. Use when starting tilt, debugging Tiltfile errors, or bootstrapping a dev environment.
96
96%
Does it follow best practices?
Impact
92%
1.33xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely covers specific capabilities, includes natural trigger terms, and provides explicit 'Use when' guidance. It uses proper third-person voice and targets a clear, distinct niche around Tilt dev environment management. The description is well-structured and would allow Claude to confidently select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Start Tilt dev environment in tmux', 'monitor bootstrap to healthy state', 'fix Tiltfile bugs without hard-coding or fallbacks'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (start Tilt in tmux, monitor bootstrap, fix Tiltfile bugs) and 'when' with an explicit 'Use when...' clause covering starting tilt, debugging Tiltfile errors, and bootstrapping a dev environment. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'tilt', 'Tiltfile', 'tmux', 'dev environment', 'bootstrap', 'debugging', 'Tiltfile errors'. These cover the main terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Tilt/Tiltfile and tmux-based dev environments. The specific tooling references (Tilt, Tiltfile, tmux) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable guidance for starting and monitoring a Tilt dev environment. The principles section establishes strong guardrails against common anti-patterns, and the workflow is well-sequenced with proper validation and error recovery loops. The only minor weakness is that the inline principles section is somewhat lengthy, though it remains relevant and well-organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. Every section serves a purpose—principles are stated as actionable rules without explaining what Tilt is, the workflow steps are concrete without padding, and there's no unnecessary exposition about concepts Claude would already know. | 3 / 3 |
Actionability | Provides fully executable bash commands for every step: checking tmux sessions, starting tilt, polling resource status with jq, reading logs. The code blocks are copy-paste ready with proper variable handling and conditional logic. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation checkpoints: Step 3 monitors convergence with specific polling criteria, Step 4 includes a feedback loop (fix → live-reload → re-poll), and there's a clear escalation path after 3 failed fix iterations. The success/failure criteria are explicit. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and references the tmux skill for patterns, but the Principles section is fairly lengthy inline content. For a skill of this size (~100 lines), the organization is reasonable but the principles could potentially be separated or the reference to the tmux skill could be more clearly signaled. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.