CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

98

1.33x
Quality

Does it follow best practices?

Impact

92%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, concise, and highly actionable with executable commands and a clear, validated workflow including error-recovery feedback loops. It appropriately keeps everything in one organized file with no need for bundled references.

DimensionReasoningScore

Conciseness

The body is lean and directive — bullets assume Claude knows tmux/Tilt/k8s and avoid concept over-explanation; tokens earn their place despite minor redundancy of resource_deps() across principle subsections.

3 / 3

Actionability

Provides fully executable, copy-paste-ready bash throughout — real tmux session/window commands, a real 'tilt get uiresources -o json | jq' polling query, and 'tilt logs' — matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear five-step sequence has explicit validation checkpoints (convergence polling in Step 3) and a feedback loop in Step 4 (fix -> re-poll to verify) plus escalation after three stalled fix iterations.

3 / 3

Progressive Disclosure

No bundle files exist; the self-contained content is organized into well-signaled Principles and Workflow sections with only one-level cross-references (the tmux skill), avoiding nested or monolithic structure.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong description that concretely states capabilities, provides natural trigger terms, and explicitly marks when to use it. It is concise, third-person, and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Start Tilt dev environment in tmux, monitor bootstrap to healthy state, fix Tiltfile bugs without hard-coding or fallbacks' — with explicit constraints, matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what (start, monitor, fix bugs) and when via an explicit 'Use when...' clause, exactly matching the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasings are present — 'starting tilt', 'debugging Tiltfile errors', 'bootstrapping a dev environment' — terms a user would actually say, giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The Tilt/Tiltfile/tmux-bootstrap niche is sharply scoped with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.