fmt

Run `make fmt` to check the code format.

1.69x

Quality

—

Does it follow best practices?

Impact

95%

1.69x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

The content is lean, well-organized, and includes a clear re-run-until-clean feedback loop for a simple skill. Its main weakness is the hardcoded, machine-specific absolute path in the example command, which hurts portability and copy-paste readiness.

Suggestions

Replace the hardcoded path `/Users/paul.masurel/git/quickwit/quickwit` with a portable relative instruction, e.g. `cd quickwit/ && make fmt`, so the command works regardless of machine.

Add a brief note on what a clean run looks like (exit code / expected output) so the "until clean" loop has a concrete success signal.

Optionally split the three checks into sub-steps with per-check fix pointers for readers who only hit one issue type.

Dimension	Reasoning	Score
Conciseness	The body is lean — a single command, a compact checklist of what it checks, and brief fix steps — with no explanation of concepts Claude already knows.	3 / 3
Actionability	The command `cd /Users/paul.masurel/git/quickwit/quickwit && make fmt` is concrete and executable, but the hardcoded personal absolute path limits copy-paste readiness on other machines; the portable guidance is only in prose.	2 / 3
Workflow Clarity	The sequence is clear for a simple skill and includes an explicit feedback loop — "Fix any issues found and re-run until clean" — which serves as the validation checkpoint.	3 / 3
Progressive Disclosure	This is a short, single-purpose skill with no external references needed; the heading and organized lists are well-structured, qualifying for 3 under the simple-skill guidance.	3 / 3
	Total	11 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a concrete command, but it lacks an explicit "Use when..." trigger clause and broader keyword coverage. It answers what but only implies when.

Suggestions

Add a "Use when..." trigger clause, e.g. "Use when formatting Rust code, checking license headers, or fixing log message style in the quickwit project."

Broaden trigger terms to include natural variations like "formatting", "lint", "style", and "license headers".

List the concrete checks (Rust formatting, license headers, log format policy) to raise specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes "Run `make fmt` to check the code format" — it names a concrete command and the code-format domain, but only a single action rather than multiple specific actions.	2 / 3
Completeness	It states what to do (run make fmt to check format) but has no "Use when..." trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"make fmt" and "code format" are relevant keywords a user might say, but common variations like "formatting", "lint", or "style" are missing.	2 / 3
Distinctiveness Conflict Risk	"make fmt" is a fairly distinct trigger, but "check the code format" is generic enough to overlap with general formatting or lint skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: quickwit-oss/quickwit
Commit: f3cddcb

Reviewed: 2 days 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.