CtrlK
BlogDocsLog inGet started
Tessl Logo

lading-optimize-review

Reviews optimization patches using a 5-persona peer review system. Requires unanimous approval backed by benchmarks.

60

Quality

71%

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/lading-optimize-review/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.

The content is a well-structured, highly actionable review workflow with strong validation checkpoints and clean progressive disclosure to template assets, held back only by minor redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tables, checklists, and concrete commands, but repeats the 'does NOT record results' note and duplicates the Outcomes/Decision table, leaving minor trimmable padding.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (cargo criterion, hyperfine, ci/kani, ci/validate) with explicit numeric thresholds (5%/10%/20%) and named template files, covering the common cases.

5 / 5

Workflow Clarity

Phases 1-5 are clearly sequenced with explicit validation checkpoints (missing-argument/baseline REJECT gates, statistical thresholds), feedback loops (REJECT with documented reasons), and per-persona checklists for a complex process.

5 / 5

Progressive Disclosure

Good structure with one-level-deep, clearly signaled references to the approved/rejected template assets in a verdict-to-template table; the core workflow is appropriately inline, with only minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

53%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 conveys a clear, distinctive purpose with concrete benchmark-backed review mechanics, but it lacks a 'Use when...' trigger clause and relies on somewhat technical jargon over natural user phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when reviewing an optimization patch in lading before merging, or when the caller requests benchmark-backed approval').

Soften jargon like '5-persona peer review system' and 'unanimous approval' with more natural phrasing users would actually say, such as 'peer review by five reviewers' and 'all reviewers must approve'.

List 1-2 more concrete actions (e.g. 'runs micro- and macro-benchmarks, checks for duplicate optimizations') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('optimization patches') and a couple concrete actions ('5-persona peer review system', 'unanimous approval backed by benchmarks'), but the actions are somewhat abstract rather than a comprehensive list of specific operations.

3 / 5

Completeness

Clearly states what the skill does but omits any 'Use when...' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('optimization patches', 'peer review', 'benchmarks') but leans on niche jargon ('5-persona peer review system', 'unanimous approval') and misses common variations or synonyms a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

The 5-persona optimization-review niche is fairly distinct with low conflict risk, though the missing explicit trigger clause leaves minor overlap risk with related lading optimization skills.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
DataDog/lading
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.