CtrlK
BlogDocsLog inGet started
Tessl Logo

bump-tantivy

Bump tantivy to the latest commit on main branch, fix compilation issues, and open a PR

94

4.71x
Quality

Does it follow best practices?

Impact

99%

4.71x

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 content is a tight, fully actionable 10-step workflow with concrete commands and an explicit cargo-check validation loop. It respects the token budget, contains no unnecessary concept explanations, and is well organized for a simple single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — each step is a direct command with a one-line rationale and no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor (3).

3 / 3

Actionability

Every step provides concrete, copy-paste-ready commands (e.g. `gh api repos/quickwit-oss/tantivy/commits/main --jq '.sha'`, `cargo check`, `make fmt`, `gh pr create ...`), matching the fully-executable anchor (3) rather than pseudocode or vague direction (2).

3 / 3

Workflow Clarity

A clear 10-step numbered sequence with explicit validation checkpoints — Step 1 aborts if not on main, and Step 5 has a feedback loop ('Repeat until cargo check passes') for the risky build operation — matching the anchor for clear sequence with explicit validation (3).

3 / 3

Progressive Disclosure

This is a single-purpose skill under 50 lines with no need for external references, organized into clearly labeled sections; per the simple-skills scoring note, that organization earns a 3 without separate files.

3 / 3

Total

12

/

12

Passed

Description

82%

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 specific, actionable, and distinct, listing three concrete operations for bumping tantivy. Its main weakness is the absence of an explicit 'Use when' trigger clause, which leaves the invocation context implied and caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when bumping the tantivy dependency, after a new commit lands on its main branch, or when asked to update quickwit's tantivy rev.'

Consider adding the natural term 'quickwit' so the trigger matches how users refer to the target repository.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Bump tantivy to the latest commit on main branch', 'fix compilation issues', and 'open a PR' — matching the anchor for multiple specific concrete actions rather than a single domain+action (2).

3 / 3

Completeness

It clearly states what the skill does but provides no explicit 'Use when...' trigger clause, so the 'when' is only implied; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural phrasing a user would actually say — 'bump tantivy', 'latest commit on main branch', 'fix compilation issues', 'open a PR' — giving good coverage of natural trigger terms rather than only technical jargon (2).

3 / 3

Distinctiveness Conflict Risk

Highly specific to bumping the tantivy dependency, giving it a clear niche with distinct triggers unlikely to conflict with other skills, matching the anchor for a clear niche (3) rather than a generic description (2).

3 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
quickwit-oss/quickwit
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.