tilt

Queries Tilt resource status, logs, and manages dev environments. Use when checking deployment health, investigating errors, reading logs, or working with Tiltfiles.

1.29x

Quality

86%

Does it follow best practices?

Impact

100%

1.29x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

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

The body is concise, executable, and action-oriented with a clear first-action checkpoint and useful guardrails. The main weakness is progressive disclosure: two referenced markdown files are cited but not present in the bundle.

Suggestions

Create the referenced TILTFILE_API.md and CLI_REFERENCE.md files in the bundle, or remove the broken references from the body.

Add a brief validation/verification step (e.g., checking resource health again after a trigger) to make the workflow feedback loop explicit.

Consider moving the longer tmux 'tilt up' script into a bundled script file to keep the overview leaner.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding explaining what Tilt is; every command earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste ready commands covering common cases including non-default ports and JSON status queries.	5 / 5
Workflow Clarity	A clear 'First Action: Check for Errors' establishes an explicit primary checkpoint before investigation, with guardrails like 'Never Restart for Code Changes'; minor validation gaps keep it just below the top anchor.	4 / 5
Progressive Disclosure	Sections are well organized, but the referenced files (TILTFILE_API.md, CLI_REFERENCE.md) do not exist in the bundle, so the signaled references point to missing material.	3 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, well-structured description that concretely names capabilities and provides explicit use-when triggers tied to a distinct Tilt niche. Minor gains possible by adding synonyms or file extensions to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Names the Tilt domain and three concrete actions ('Queries Tilt resource status, logs, and manages dev environments'), with only minor coverage gaps, matching the 'several specific actions' anchor.	4 / 5
Completeness	Explicitly states both what it does and when to use it via a concrete 'Use when...' clause with multiple trigger scenarios, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases ('checking deployment health, investigating errors, reading logs, or working with Tiltfiles') but lacks synonyms or file extensions, sitting just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Tilt-specific niche with distinct triggers ('Tiltfiles', 'Tilt resource status') that minimize overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/tilt/SKILL.md
Commit: 2f57aec

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.