CtrlK
BlogDocsLog inGet started
Tessl Logo

best-of-n

Generate a small set of independent candidate solutions in worktrees, judge them against one explicit rubric, and apply the winner only after PASS verification.

68

Quality

83%

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

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 body is a tight, actionable orchestration playbook with concrete config examples, an explicit four-phase workflow, and strong PASS-gated validation feedback loops, all well organized with no unnecessary padding or broken references.

DimensionReasoningScore

Conciseness

The body is lean and instruction-dense — it never explains what a worktree or agent worker is, and lines like 'Never run parallel writers in the parent checkout' earn their tokens; it avoids the padded conceptual preamble penalized at score 1 and the over-explanation of score 2.

3 / 3

Actionability

Provides a copy-paste-ready JSON agent contract plus concrete settings ('type: implementer', 'worktree: true', 'write_authority: worktree_write', bounded 'write_roots'), matching the score-3 'fully executable; copy-paste ready' anchor rather than the pseudocode of score 2.

3 / 3

Workflow Clarity

The four-phase sequence (Set The Tournament → Generate Independently → Judge Once → Integrate Only After PASS) has explicit validation checkpoints — 'VERDICT: PASS|FAIL', 'apply/merge the winner only after the judge reports PASS with real checks', 'Re-run the repository's checks in the parent after apply' — meeting the score-3 anchor with feedback loops, well above the implicit-checkpoint score 2.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is a self-contained process with well-organized sections and no nested or dangling references, so per the scoring notes a no-reference, well-structured skill scores 3 rather than the monolithic-wall or unsplit-inline cases at lower levels.

3 / 3

Total

12

/

12

Passed

Description

67%

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 concretely names the skill's three core actions and occupies a distinctive niche, but it omits an explicit 'Use when...' trigger clause and leans on technical jargon over natural user keywords, capping completeness and trigger quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a high-stakes task has several plausible approaches and comparison is worth the extra work; do not use for tiny changes or pre-chosen approaches.'

Surface natural user keywords such as 'compare options', 'best of N', or 'pick the best approach' alongside the technical terms to improve trigger-term quality.

Mirror the body's gating language in the description so the 'when' is as explicit as the 'what'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate a small set of independent candidate solutions in worktrees', 'judge them against one explicit rubric', 'apply the winner only after PASS verification' — matching the score-3 anchor of several specific concrete actions rather than the single-domain score-2 example.

3 / 3

Completeness

The 'what' is explicit, but there is no 'Use when...' clause or equivalent trigger guidance for 'when' to use the skill; per the judging guidelines a missing trigger clause caps completeness at 2, and it is not score 1 because the capability is clearly stated.

2 / 3

Trigger Term Quality

Domain terms like 'candidate solutions', 'judge', and 'rubric' are relevant, but the phrasing leans technical ('worktrees', 'PASS verification') and omits natural user variations such as 'compare options' or 'best of N', fitting the score-2 'some relevant keywords but missing common variations' rather than the broad natural-term coverage of score 3.

2 / 3

Distinctiveness Conflict Risk

The ensemble/best-of-N niche with worktree isolation, rubric judging, and PASS verification is distinctive and unlikely to trigger for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor; it is above score 2 because the described behavior is specific rather than broadly overlapping.

3 / 3

Total

10

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
Hmbown/CodeWhale
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.