CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightdash-release-review

Review shipped Lightdash features and updates over a date range, on demand or on a schedule.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lightdash-release-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an unusually lean, prescriptive workflow with concrete output templates, explicit validation checkpoints, and genuine error-recovery paths. Its one real defect is structural: the sole bundle reference points to a file that does not exist, which both weakens progressive disclosure and leaves retrieval mechanics unspecified.

Suggestions

Add the missing resources/github-retrieval.md to the bundle (containing the access, pagination, tag-comparison, and recovery procedures), or inline the essential retrieval commands into the Research section, so the body's only reference resolves.

Use the conventional references/ directory name (or verify the packaged path) so the link target matches the bundle layout that ships with the skill.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no definition of Lightdash, GitHub, or releases) and every sentence is an operative rule, e.g. "A merged PR or tag alone does not prove shipping" and "Omit empty sections". Not 4: I could not identify a sentence that could be trimmed without losing a distinct rule; there is no padding and no time-sensitive dates.

5 / 5

Actionability

Highly concrete guidance: the repo URL, "filtering by `published_at` and excluding drafts and prereleases", "Inspect diffs or files at the release tag", an exact title template, "200–350 words", "at most six per feature/update section", "roughly 15–25 words", and a verbatim closing sentence. Not 5: the retrieval mechanics ("access, pagination, comparisons, and recovery") are delegated to ./resources/github-retrieval.md, which is not present in the bundle, leaving that half of execution unspecified. Not 3: what is written is direct and executable, not pseudocode-level.

4 / 5

Workflow Clarity

A clear sequence (Review period → numbered Research steps → Select highlights → Write the review → Delivery) with explicit validation ("Resolve the exact period and timezone before retrieval", "Tie every included change to a published release in the period", docs "checking that it applies to the reviewed version") and error-recovery paths (the **Partial review** labeling with retrieval-gap explanation, and the no-changes case). Not 4: checkpoints and failure loops are explicit rather than implicit, satisfying the anchor-5 pattern.

5 / 5

Progressive Disclosure

The body is well-sectioned and its single reference is clearly signaled ("Read [GitHub retrieval](./resources/github-retrieval.md) for access, pagination, comparisons, and recovery"), but no resources/, references/, scripts/, or assets/ directory exists in the bundle — the one referenced file is missing, so the disclosure chain is broken and the detail it promises is unreachable. Not 4: a dangling reference is more than a minor organization gap; not 2: the SKILL.md itself is well structured, not an inlined wall of reference material.

3 / 5

Total

17

/

20

Passed

Description

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

The description is distinctive and reasonably concrete thanks to the named product and invocation modes, but it omits explicit trigger guidance and only partially enumerates the skill's actions. Adding a "Use when..." clause with natural trigger phrases would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what's new in Lightdash, wants release notes or a changelog for a date range, or requests a recurring Lightdash features-and-updates digest."

Name the deliverable and one more concrete action, e.g. "Compile a customer-facing digest of new features, updates, and breaking changes from published Lightdash releases, linked to their supporting PRs."

Include common synonyms such as "release notes", "changelog", or "what's new" so the description matches the phrasings users actually say.

DimensionReasoningScore

Specificity

"Review shipped Lightdash features and updates" names the domain and one concrete action, with modes "over a date range" and "on demand or on a schedule", matching the anchor for 1-2 concrete actions without comprehensive coverage. Not 4: it lists a single action verb rather than several specific actions (no mention of the digest deliverable, linking PRs, or classifying changes).

3 / 5

Completeness

The what is clear ("Review shipped Lightdash features and updates") but there is no "Use when..." clause or equivalent trigger guidance; "on demand or on a schedule" describes invocation modes rather than when Claude should reach for the skill, so completeness is capped at 3 per the guidelines. Not 4: anchor 4 expects an explicit when-clause, which is absent.

3 / 5

Trigger Term Quality

Natural terms include "Lightdash", "features", "updates", "date range", and "on a schedule", giving good keyword coverage a user would plausibly say. Not 5: common variations such as "release notes", "changelog", or "what's new" are absent; not 3: coverage goes well beyond a bare domain mention.

4 / 5

Distinctiveness Conflict Risk

"Lightdash" is a unique product name establishing a clear niche with distinct triggers and minimal conflict risk with other skills. Not 4: the product name alone disambiguates it from virtually any other skill, so there is no meaningful overlap risk to deduct for.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

lightdash/lightdash

Path

skills/lightdash-release-review/SKILL.md

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.