CtrlK
BlogDocsLog inGet started
Tessl Logo

update-lambda

Trigger a new lambda release, update build.rs with the new artifact URL and SHA256, and open a PR

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/update-lambda/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A tight, highly actionable runbook that executes a lambda release end-to-end with strong validation and feedback loops. The only mild gap is a few over-explanatory lines and the lack of any external reference structure, which is appropriate for a linear procedure.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with only brief, purposeful rationale lines like "This ensures the lambda tag points to the latest code."; a few such narrations (e.g. "This triggers the Release Lambda binary GitHub Actions workflow") could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Every step gives copy-paste-ready, fully executable commands ("gh run list --repo quickwit-oss/quickwit --workflow=publish_lambda.yaml ...", "git rev-parse --short HEAD") and Step 9 names the exact two Rust constants to update, covering the common case end-to-end.

5 / 5

Workflow Clarity

Twelve steps are explicitly sequenced with validation checkpoints: Step 4 checks the tag exists, Step 6 branches on status/conclusion with a wait-and-retry feedback loop, and Steps 6/7 abort with the failure URL or on missing assets before the irreversible draft-publish in Step 8.

5 / 5

Progressive Disclosure

A single self-contained file is well-organized into 12 numbered sections with no nested references and no content that needs splitting; at ~140 lines it exceeds the under-50-line simple-skill exception, so it lands at 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

62%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 specific, distinct description that clearly states what the skill does, but it omits any explicit trigger guidance for when Claude should activate it. Adding a "Use when..." clause would raise both completeness and trigger-term quality.

Suggestions

Append a "Use when..." trigger clause, e.g. "Use when updating the Quickwit lambda artifact, bumping the lambda client build.rs URL/SHA256, or cutting a new lambda release."

Add natural synonyms users might say, such as "lambda artifact", "lambda binary", or "bump lambda client", to broaden trigger coverage.

Specify the trigger mechanism briefly ("by pushing a lambda-<commit> tag to run the Release Lambda binary workflow") to lift specificity from 4 to 5.

DimensionReasoningScore

Specificity

It lists several concrete actions on named targets ("update build.rs with the new artifact URL and SHA256, and open a PR"), but "Trigger a new lambda release" stays slightly abstract about the mechanism (pushing a tag to run a GitHub Actions workflow), leaving a minor gap versus a 5.

4 / 5

Completeness

The "what" is clear and concrete, but there is no explicit "when should Claude use it" clause; per the rubric guidance, a missing "Use when..." clause caps completeness at 3.

3 / 5

Trigger Term Quality

Domain terms a user would actually say are present ("lambda release", "build.rs", "SHA256", "open a PR"), but there are no common variations/synonyms and no natural "Use when..." trigger phrase wrapping them.

3 / 5

Distinctiveness Conflict Risk

The combination of "lambda release", "build.rs", "artifact URL and SHA256", and "open a PR" carves out a very specific niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

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.